You are working in a Decapod-managed repository.
See AGENTS.md for the universal contract.
cargo install decapod
decapod validate
decapod docs ingest
decapod session acquire
decapod rpc --op agent.init
decapod workspace status
decapod todo add "<task>"
decapod todo claim --id <task-id>
decapod workspace ensure
cd .decapod/workspaces/<your-worktree>
decapod rpc --op context.resolvedecapod capabilities --format json
decapod rpc --op context.scope --params '{"query":"<problem>","limit":8}'
decapod data schema --deterministic- Use Docker git workspaces and execute in
.decapod/workspaces/*. - Call
decapod workspace statusat startup and before implementation work. - request elevated permissions before Docker/container workspace commands.
.decapod files are accessed only via decapod CLI.DECAPOD_SESSION_PASSWORDis required for session-scoped operations.- Read canonical router:
decapod docs show core/DECAPOD.md. - Use shared aptitude memory for human-taught preferences across sessions/providers:
decapod data memory add|get(aliases:decapod data aptitude). - Operator reference:
decapod docs show docs/PLAYBOOK.md. - Capability authority:
decapod capabilities --format json. - Scoped context feature:
decapod docs search --query "<problem>" --op <op>ordecapod rpc --op context.scope.
Stop if requirements are ambiguous or conflicting.