Decisions
What was decided, by whom, and in which round or session it was settled.
Resume with the decisions, context, and responsibilities intact.
Corvair Memory supports the Knowledge Substrate by preserving the chronology of a project, what was said, decided, changed, assigned, and produced, then building the working context each person or agent needs. A project can pause, move to another channel, bring in a specialist, and resume without treating every session as day one.
Messages remain part of the chronology, but Memory is designed to recover the state of the work, not merely replay a transcript.
What was decided, by whom, and in which round or session it was settled.
Owners, current status, and whether the work was ever closed out.
What changed, and which earlier direction the change superseded.
The boundaries a project has deliberately set, so they are not quietly re-crossed.
What the work produced, and the events that led to the artefact.
The Knowledge snapshot and premises used when an answer shaped the work.
The chronological record stays canonical. Working context is derived from it and can be rebuilt, which is what keeps continuity explainable.
Each meaningful interaction becomes a typed, chronological event with its speaker and time.
Conversation state and a project digest are derived from that record.
The next session receives recent context, decisions, open actions, exclusions, and project state.
New work extends the same record. It does not overwrite the past.
The project digest and recent context were restored.
The recorded policy snapshot supplied the premises for this round.
Proceed with the revised control design after compliance review.
The risk lead will confirm the evidence owner before Friday.
The control rationale was written up and saved to the project.
An illustrative project. The record on the left is what actually happened, in order. The digest on the right is derived from it, which means it can always be rebuilt and explained.
A project rarely stays with one person, in one session, in one place. Memory is designed so that moving the work does not mean losing it.
The people and agents taking part in the project are recorded, not assumed.
Composition modes and capabilities describe which agents are working and what each one may do.
A participant can be given only the context their part of the work requires.
Session markers record where the work stopped, so the next round knows where to pick it up.
The same project digest can follow a case across chat, voice, email, and other channels that an application connects.
Corvair supports continuity across those channels. The application that integrates them still owns the channel itself.
Memory and Knowledge have different units, different access patterns, and different lifecycles. Keeping them apart is what lets a project move quickly without weakening the governance promise.
Two controlled crossings, in plain language. Knowledge can seed Memory when a project resumes, and the snapshot it used is recorded. Selected decisions or artefacts can be proposed for Knowledge, where they face the same admission rules as any other source.
Lifecycle and audience controls sit on the data path. They shape what can be retained, viewed, exported, erased, or used to ground later work.
Different audiences receive purpose-specific views, from an owner's full record to shared and audit-oriented exports.
Erasure is previewed before it is applied and leaves an audit record. Linked Knowledge content is retracted through the cross-boundary workflow.
Protected records can be tokenised and kept under elevated access while a hold is in force.
Histories, summaries, actions, and interaction records can be exported through policy-aware paths, and artefacts can be revoked.
Identity and access are resolved from the platform principal and the project binding, not supplied by the calling client.
Usage reporting is designed to carry no customer identity, personal data, or content.
Humans working in the browser workbench, and in future the mobile applications, resume from the same project record that agents reach through the governed API and MCP. Memory does not create a privileged agent-only view of the work.
Resume, decide, curate, and verify.
Resume, reason, act, and hand off.
Equivalent authority produces equivalent access to decisions, actions, grounding references, and evidence. The interface differs. The governed record does not. The Knowledge Substrate remains the authority both sides are grounded in.
Advisory, case, and research work restarts with the current decisions and open actions intact, rather than with a summary of a summary.
Specialist agents receive the perspective their part of the work needs, without sharing every internal detail of the project.
An application can carry a single project digest across the chat, voice, email, and messaging channels it has connected.
Record which Knowledge snapshot supplied the premises that shaped the context behind a decision, and reopen it later.
Corvair Memory lets people and agents continue the same governed body of work across time. It supports the Knowledge Substrate by preserving context, while Vault contributes personal knowledge under the user's control.