Story Documents

Story documents preserve context across AI sessions. They are suitable for requirements, evidence, implementation plans, release procedures, decisions, and final results.

Create documents with descriptive titles in the Story's Documents area. Content is stored on the owner node and rendered by Control Plane. Documents can be opened, renamed, and deleted.

When an AI session updates a document, identify the document, desired outcome, and allowed scope explicitly. Review generated facts, commands, and risk conclusions. Avoid parallel sessions writing the same document.

Use titles such as Authentication acceptance criteria or Production release procedure, rather than generic names. Keep chronological status inside the document instead of repeatedly renaming it.

Document deletion and Story deletion are irreversible. Keep important deliverables in the project repository or approved storage.