Concepts
A task defines what should run: target package, module/function or PTB template, parameters, trigger condition, fee policy, privacy refs, cooldowns, and owner controls.
Keepers
Section titled “Keepers”Keepers are permissionless operators. They stake SUI, discover eligible tasks, evaluate triggers, execute PTBs or Nautilus-backed logic, and submit claims for rewards.
Epoch Committees
Section titled “Epoch Committees”DeHeart can group staked keepers into epoch-based committees for coordination and quality control. The MVP can start simpler, then graduate into stronger epoch mechanics.
Reputation
Section titled “Reputation”Reputation is objective protocol telemetry: success rate, total executions, uptime heartbeats, and disputes won/lost. It helps route work but does not replace proof validity.
Verifiability
Section titled “Verifiability”Simple tasks verify through Sui state checks and events. Private or complex tasks use Nautilus attestations and signed result hashes.
Privacy
Section titled “Privacy”Seal policies protect encrypted parameters, private strategies, and result data. Access can be limited to task owners, selected keepers, successful keepers, or delayed reveal policies.