Trigger, guard, execute, log.
Deeds flow through trigger resolution, queue lanes, execution guards, capability tokens, mutation logging, and final status.
Deeds
Workflows as deterministic assets.
A Deed is a JSON-defined action sequence for resource mutations, notifications, provider calls, AI generation, confirmations, and scheduled work.
Control flow is explicit.
Sequential, parallel, switch, if/else, for-each, try/catch, delay, and confirmation steps are represented in the Deed definition.
Same write rule.
Deeds do not bypass the platform. Workspace writes still go through the Command Bus with a source.
Tool substrate.
Registered Deeds are the current substrate for Poly tools and provider capability wrappers.