Docmancer separates three things that should not be confused:
- Agent evidence is what coding agents already wrote. It remains source-attributed and read-only.
- Curated memory is Markdown that a person or authorised agent deliberately chose to keep.
- Shared Memory is the canonical Markdown tree that carries durable knowledge between agents.
Machine-wide files live under profile/, principles/, projects/, and shared/. Project files live under decisions/, constraints/, workflows/, and lessons/.
Write deliberate memory
docmancer write $'# Deployment\n\nProduction deploys run on Railway.' \
--path decisions/deployment.md \
--scope project \
--source issue:123
The result includes a stable address, content hash, revision, and canonical path.
Read and change safely
docmancer read docmancer://memory/<id> --json
docmancer edit docmancer://memory/<id> - --expected-hash <hash>
docmancer move docmancer://memory/<id> decisions/production.md --expected-hash <hash>
Every existing-file change is hash guarded. Stable addresses and citations survive moves.
write, read, and edit default to the project tree at ./.docmancer/tree. Add --global to target the machine-wide tree at ~/.docmancer/tree instead:
docmancer read --global about.md
Machine-wide files have a generated zone that combination rewrites. Editing that zone is refused rather than silently overwritten; keep your own notes in the pinned zone with docmancer memory canonical pin.
Import notes
docmancer import ./agent-notes
Import copies Markdown into the inbox without rewriting the source. Review the complete file before assigning a durable destination. Docmancer does not create a queue that asks people to approve hundreds of fragments individually.
Inspect change history
Use docmancer timeline for readable curated-memory changes. Normal deletion is recoverable through trash and restore. Compatibility-generated artifacts remain outside canonical Shared Memory and can be rebuilt from their sources.