ag-dir

A durable agent project directory organizes core architectural docs at the repository root while isolating runtime artifacts in a dedicated .agents directory. This structure separates durable documents like design.md from high-churn runtime data, ensuring stable ownership and repeatable workflows.

An AGD structure defines a stable repository root housing durable files like design.md, memory.md, config.md, progress.md, and a specs/ directory. It isolates per-spec runtime data and history under a dedicated .agents directory, keeping churn separate from durable architectural documentation.

Maintain a specs-driven workflow by creating specs/*.md files for design definitions and routing per-spec progress and history to an isolated .agents/runs/ directory. This keeps durable architectural docs stable at the root while runtime execution data churns safely in the .agents directory.

Yes, you can audit and update existing architectural docs by applying the durable agent directory structure. It enforces clear ownership rules and repeatable workflows around core files like design.md, config.md, and progress.md, ensuring project documentation remains organized and current.

The best way to separate durable docs from runtime artifacts is implementing a root-level agent directory for design.md and specs, alongside a dedicated .agents directory for runtime data. This physical separation prevents runtime churn from corrupting stable architectural documentation.

You need a dedicated .agents directory specifically for runtime artifacts and per-spec run history, not for durable memory or config files. Durable documents like memory.md and config.md belong at the repository root to maintain stable ownership and separation from runtime churn.