Description
Memory and Context Cabinet commands give agents direct access to the durable observations and curated references that should shape later work. dots memory lists entries, reads full detail, and reinforces a memory when new evidence supports it. the Context Cabinet is an ordinary Dotabase addressed with dots rows list context-cabinet and dots rows get context-cabinet <CTX-N>.
The workflow is designed for operators and coding agents. It uses the same authenticated, company-scoped service contracts as the rest of Dots, so terminal or protocol convenience never creates a second source of truth. Inputs are validated before or at the route boundary, and outputs preserve identifiers and structured details needed for a reliable next step.
Selling Points
- Brings durable organizational memory into headless agent sessions before decisions are made.
- Separates concise discovery lists from full-detail reads to control context volume.
- Lets new evidence reinforce an existing memory instead of creating uncontrolled duplicates.
- Makes curated reference material accessible with stable human identifiers.
- Uses the standard output envelope, so memory can feed both people and scripts.
User Story
A coding agent lists memories related to a module, opens the most relevant entry, checks the corresponding cabinet reference, and reinforces the memory with a fresh observation. It proceeds with context that survives beyond the current session. The result is a concrete, inspectable outcome that another person or automation can continue from without reconstructing hidden state.
Extension Surface
The CLI is automatable: packages/cli/src/commands/memory.ts binds Memory Bank operations, while the generic row commands in packages/cli/src/commands/rows.ts address Context Cabinet records. The knowledge content evolves, but command registration is not external. The rating reflects the most-open supported seam that is true for this capability, not a transitive implementation detail. The cited path is the operational proof: consumers can use the documented seam, while unsupported changes still require a core release.
Capabilities & Limits
- Capability: Bounded memory listing and detailed retrieval.
- Capability: Evidence-backed memory reinforcement.
- Capability: Context Cabinet list and detail retrieval.
- Limit: The CLI retrieves and reinforces stored knowledge; it does not independently judge memory truth, merge duplicates, or run the nightly synthesis cycle.
The limit is intentional product truth rather than missing documentation. Calls also remain subject to authentication, tenant selection, schema validation, and the permissions enforced by the authoritative service.
Implementation Map
packages/cli/src/commands/memory.tspackages/cli/src/commands/rows.tsrows listrows getdocs/cli/module-and-chat-commands.md