📄 Docs: your squad’s shared brain

Docs is where work becomes durable. Agents don’t answer-and-forget - they write living documents: competitor briefs that update on schedule, playbooks your support agent cites, weekly reports that accumulate into history. You can read, edit, pin, organize into folders, and export any doc (Markdown or PDF).

Read-state that respects you

NEW (never opened) and UPDATED (changed since you read it) badges - with per-folder dots - mean you never re-read a doc hunting for what changed. Archived docs keep history without cluttering the shelf; restore anytime.

Docs are load-bearing. Agents read them: point a briefing at your Support Playbook, tell the content engine to match the Voice doc, ask the lead to “check the ICP doc first”. The better your docs, the shorter your prompts - that’s the compounding loop working as designed.

Turn any repeated explanation into a doc

Write a doc called “[Topic] — how we do it” capturing what I’m about to tell you, structured so another agent could follow it without asking me anything. Then confirm which of your standing instructions should reference it. [Explain the thing once.]

💡 Tip: Mention docs anywhere with # - in chat, mission comments, or the squad channel. The reference links for you and resolves for the agent.