Create and structure docs
Docs is the long-form wiki for workspace context. Use this guide to create pages that people and AI can find, cite, and maintain.
Create a doc
- Check the project picker.
- Use
All Projectsfor organisation-wide context. - Use a project scope for project-specific docs.
- Use
- Open Docs.
- Select the Create doc button in the docs sidebar.
- Enter a clear title.
- Start writing in the body editor.
- Wait for the saved indicator after meaningful edits.
Use direct titles such as Enterprise onboarding checklist or Billing architecture constraints. Avoid vague titles such as Notes.
Create a child page
- Open the parent page.
- Use the doc tree context menu or the editor's child-page insertion flow.
- Create the child page.
- Give it a specific title.
- Add a short summary at the top.
- Return to the parent and confirm the child page appears in the expected place.
Use child pages for research, implementation notes, customer context, follow-up plans, and supporting material under a stable parent.
Structure a page
- Start with a one-paragraph summary.
- Use headings for major sections.
- Use bullets for constraints, decisions, risks, and next steps.
- Add references to related tickets, decisions, risks, memory, snapshots, or docs.
- Split the page when separate topics begin competing for attention.
Good docs are readable to a teammate who did not attend the meeting or write the plan.
Add references
- Copy the visible display ID of the related record.
- Paste it into the doc body where the dependency matters.
- Use the reference in a sentence, not only as a loose link.
- Save the doc.
- Open details or backlinks later to verify the relationship.
Example:
This rollout depends on DEC-18 and resolves the customer risk tracked in RISK-7.
Implementation work is tracked in APP-42.
Organize the docs tree
- Use top-level pages for stable areas such as product, customers, engineering, operations, or policies.
- Nest child pages under the page that owns the context.
- Drag pages in the tree to reorder or reparent them.
- Create an index page when a section has many child pages.
- Search before creating another similar page.
If a doc seems missing, switch between All Projects and the relevant project before assuming it was deleted.
Duplicate a doc
- Open the doc.
- Open the doc actions menu.
- Select Duplicate.
- Rename the duplicate.
- Edit content that should not carry over.
- Confirm references still point to the right records.
Duplicate only when the old structure is a useful template. Do not duplicate stale facts into new pages without reviewing them.
Extract memory from a doc
- Finish and review the source doc.
- Open the doc actions menu.
- Select Extract memory.
- Wait for Agent running to finish.
- Open Inbox or Memory Diffs.
- Review each proposed fact.
- Accept only facts that are accurate, durable, scoped correctly, and useful.
- Reject speculative, stale, or overly broad facts.
Extract memory creates proposals. It does not automatically turn the whole doc into trusted memory.
Restore an earlier revision
- Open the doc.
- Open the details or revision panel.
- Review the available revisions.
- Choose the revision to restore.
- Confirm the restored body is correct.
- Extract memory again only if the restored content contains durable facts that should change active memory.
Archive a stale doc
- Open the doc.
- Review backlinks and related memory.
- Open the doc actions menu.
- Select Archive.
- Confirm active search and docs lists no longer treat the page as current.
Archive is the default retirement path. It preserves history while reducing stale guidance.
Delete a doc
- Open the doc.
- Review child docs, backlinks, and related memory.
- Open the doc actions menu.
- Select Delete.
- Choose whether nested child docs should be deleted or kept.
- Choose whether memory extracted from the deleted docs should be archived.
- Confirm deletion.
Use delete only when the page should be removed from docs, revisions, backlinks, and search.
Related concepts: Docs wiki, Memory diffs, Search and references.