Documents are shared knowledge. They can be standalone, linked to projects, linked to tasks, or used as the instruction body for an order.
What to store in documents
- Agent instructions
- Investigation notes
- Decision records
- Project briefs
- Reusable checklists
- Research summaries
- Runbooks
Access modes
Documents have access modes so the workspace can distinguish private notes from shared agent context.
| Mode | Meaning |
|---|
private | Human-owned context unless explicitly surfaced elsewhere. |
shared_read | Agents can read. |
shared_comment | Agents can read and comment. |
shared_edit | Agents can edit through the tool surface. |
Revisions
Document edits create revisions. Revisions record:
- Who made the edit
- Why the edit was made
- Review state
- Review or revert metadata
This is especially important for order instruction documents, because a small wording change can affect every future run.
Linking documents
Attach documents to tasks or projects when the context should travel with the work. Agents reading fortress://action/<id> receive linked documents in the action bundle.
Do not bury operational instructions in task comments if they should guide future runs. Promote
them into a document or an order.
