Can I drive plans, decisions, and procedures programmatically?

Yes; the planning surfaces are daemon tools, not UI-only features.

• ExecPlans and the live work board. Plans, milestones, and work-item state changes are all tool calls, so an agent can create a plan, advance milestones, and mark blockers, with each transition receipted. The console kanban is a view over the same data.
• Decision records. First-class records for why a choice was made, linked into the trail, so a future session (or auditor) gets rationale rather than archaeology.
• Engrams. Compiled procedures with provenance hashes: a repeatable way of doing something, carrying proof of where it came from. Fleets use engrams to share working procedures without copy-paste drift.
• C2PA output attestation is available behind a default-off flag for teams that need standards-aligned attestation on generated outputs.

The pattern throughout: coordination state lives in the daemon under the same receipt discipline as memory, so orchestration is auditable by construction.