Purpose: make AFS itself get used in an AFS-first way.
Startup Contract
- Start with
./scripts/afs session bootstrap --jsonor the MCP promptafs.session.bootstrap. - If bootstrap is unavailable, call
context.status, thencontext.query; usecontext.read/context.listfor scratchpad follow-up. - Read scratchpad state and deferred notes before major edits.
- Use
context.querybefore asking for context that may already be in memory, knowledge, or scratchpad. - Prefer scratchpad/task/hivemind updates for handoff instead of ad hoc summaries.
Working Rules
- Clarify goals, constraints, and done criteria before major edits.
- Prefer the smallest working change over architecture churn.
- Touch only task-related files.
- Keep hygiene high: no dead code or commented-out leftovers.
- Run the fastest relevant verification command before finishing.
- If checks cannot run, report exactly why and residual risk.
- Ask before destructive actions (
rm, force-push, history rewrite).
Delivery Contract
- Report what changed.
- Report what was verified.
- Report known gaps or follow-ups.
AFS Defaults
- Treat
scratchpadas the default writable working area. - Treat
memoryandknowledgeas deliberate, durable updates. - Use
itemsfor queued work andhivemindfor cross-agent handoffs only when a task spans turns or tools. - Do not start training, embeddings, background agents, or domain MCP tooling unless the task explicitly needs that surface.
Reference Material
- Agent harness upgrade guide:
docs/AGENT_INTEGRATION_UPGRADE.md - Guided setup and approachable CLI guide:
docs/SETUP_GUIDE.md - Detailed agent/runtime docs:
docs/AGENT_SURFACES.md - MCP surface docs:
docs/MCP_SERVER.md - CLI docs:
docs/CLI_REFERENCE.md