Glossary

Terms as this project uses them. Every entry links to a working implementation; if it cannot, it is a dictionary definition and we do not publish those.

• Closet: the compressed summary that recall actually reads

  A closet compresses a room's drawers into a summary with a declared token cost, and keeps the drawer ids so the original is always one step away.

• Drawer: verbatim content that is never summarised

  A drawer holds original content exactly as written, with a content hash. Summarisation happens in closets, so the source is always recoverable.

• Hall: a typed relationship between two rooms

  A hall connects two rooms in the same wing with a typed relation and a weight, so recall can follow a topic to what it depends on.

• Room: topic-specific storage inside a wing

  A room narrows a wing to one topic. It is the unit recall actually queries, and the node that relationships between topics are drawn between.

• Tunnel: the deliberate exception that crosses wings

  A tunnel links rooms in different wings. It carries a reason rather than a relation type, because crossing a partition should be justified.

• Wing: the top-level grouping in agent memory

  A wing is the outermost partition of an agent's memory — scoped to a project, a persona, or scratch work, and optionally bound to one repository.

• Critical path: the floor on how fast a plan can finish

  The longest chain of dependencies through a task graph. It sets the minimum completion time even with unlimited agents, and only shortening it helps.

• Wave plan: parallel batches separated by a barrier

  Tasks grouped into waves that run in parallel, where nothing in wave N+1 starts until every task in wave N finishes. The barrier is the point.

• Dispatch queue: the row that guarantees delivery

  A Postgres table holding work committed for a specific machine. In DevPilot it is the delivery guarantee itself, not a cache in front of one.

• Orchestrator: the agent runner on your own machine

  The local process that claims dispatched work and runs a coding agent against your checkout. It holds the credentials; the hosted plane never does.

• Shared session: an encrypted transcript we cannot read

  An ordered, end-to-end encrypted conversation between people and their agents. The key lives in the link fragment, so the server only ever stores its hash.