artifact-management

Project artifact management enforces consistency by defining agent-specific write permissions for local .AGENTS.md files and global documents, preventing data loss. This ensures all agents follow strict guidelines for reading and updating critical project memory like TASK.md and ARCHITECTURE.md.

Task tracking and project memory are maintained through a dual-state protocol linking internal agent memory with external documentation. Agents must read relevant artifacts before starting work and update TASK.md immediately after completing changes, enforcing version control and data integrity.

Version control for project tasks is handled through a strict archiving protocol mandated for TASK.md. This protocol enforces agent-specific write permissions and requires immediate documentation updates after changes, ensuring data integrity and preventing the loss of development progress.

Yes, local .AGENTS.md files are used to track code documentation and specific changes made by individual agents. The system enforces agent-specific write permissions for these files, ensuring that only the responsible agent updates its local memory after completing a development task.

Yes, agents must read relevant artifacts like ARCHITECTURE.md and TASK.md before starting work to understand project scope. This required reading ensures consistency, prevents conflicting changes, and aligns new development tasks with the established project architecture and memory.

The limitation of dual-state tracking is the strict requirement for immediate manual updates to external documentation after internal agent changes. Failure to adhere to the archiving protocol for TASK.md or agent-specific write permissions can break project memory synchronization and compromise data integrity.