1. Carry one memory to every connected agent
This is the outcome the rest of the pipeline exists to produce. Installed skills teach agents when to ask Docmancer for prior decisions. Supported recall hooks can provide a bounded, task-relevant file selection automatically. Managed projections provide another delivery path.
The Shared Memory page shows both canonical trees and lets you inspect the exact bounded projection prepared for each agent, which is how you confirm that the same context really did reach all of them. Delivery status distinguishes installation from automatic recall and recent successful use. Lifecycle capture is installed by confirmed setup for the agents that support it, and it can be added or removed on its own with docmancer agent install <agent> --capture-hooks and docmancer agent remove <agent> --capture-hooks.
2. Discover what agents already wrote
docmancer setup finds supported agent memory, instructions, rules, and eligible session evidence. Docmancer records the contributing agent, project, source, and update time without rewriting the source file.
This corpus is evidence, not automatic truth. Several agents recording the same thing is useful provenance, but it does not become consensus merely because it recurs.
3. Organise durable knowledge
Docmancer creates an opinionated Markdown scaffold instead of asking you to invent a memory taxonomy.
- Machine-wide memory uses
profile/,principles/,projects/, andshared/. - Each project uses
decisions/,constraints/,workflows/, andlessons/.
Every file remains directly readable and editable. Stable docmancer://memory/... addresses survive file moves, and source metadata stays attached.
4. Ask across the evidence
docmancer ask combines relevant Shared Memory files and attributable agent evidence under one token budget. Weak matches stay out, mandatory project policy remains visible, and returned knowledge keeps citations.
Ask reads the latest committed index rather than rescanning your disk, which is why it answers immediately. Combination of changed sources happens during setup, explicit sync, and lifecycle capture; pass --fresh when a question must wait for changed files to be indexed first. When a generation provider is configured, Ask calls it after retrieval to turn that evidence into prose. The provider never decides what enters the bundle.
5. Keep people and agents on different surfaces
docmancer web is the human interface. Its shell appears immediately while memory services load in the background, with independent loading states for the file tree and agent delivery. The CLI, installed skills, hooks, and MCP are stable agent and automation surfaces. All use the same local files and services.
Technical documentation stays in a separate Library corpus. Personal Sync adds encrypted continuity and recovery across the machines you approve, while the complete local workflow remains free. Team Sync is not available yet.