Personal knowledge that supplements the institutional substrate.
The Knowledge Substrate manages the institution's licensed expertise, content, and files. Corvair Vault supports it by giving each person a private place for their own notes, research, reference files, and working artefacts. Personal knowledge can be checked, organised, used in authorised work, and deliberately admitted to the substrate without silently becoming institutional record.
These two sources work together without being confused for one another. Institutional content and files are managed in the Knowledge Substrate. Personal Vault material is private by default and supplements that base only under explicit authority.
The governed authority for what the institution knows and uses across its people and its agents. It manages the institution's content and files, and holds them to governed premises, citations, provenance, freshness, and warrants.
A person's own notes, research, reference files, and working artefacts.
Vault governs the boundary. The Knowledge Substrate still applies its own parsing, classification, extraction, veracity, provenance, and admission controls to anything that crosses it.
Large files are designed to stream in resumable chunks, with size and checksum verified before the file is sealed.
New content is unavailable to people, agents, and Knowledge while its checks are incomplete.
Malware, active content, scanner availability, and personal-data gates produce a stable verdict.
Clean files are placed into system or custom folders. A manual placement always wins.
A ready file can support authorised work, or be sent through the Knowledge admission path, pinned to its version.
An illustration of the states a personal file moves through. The archive is held because the scanner could not be reached, which is the fail-closed path rather than an error to be waved through.
Checks and quarantine are enforced before raw content can be served or sent to Knowledge. A clean technical check is not the same as factual trust. It is the first gate on the way to governed use.
Every new upload starts unavailable, while its integrity and content checks run.
Malware, active content, scanner availability, and policy-defined personal-data handling.
A scanner outage, error, timeout, or indeterminate result leaves the file quarantined.
Raw reads and Knowledge ingestion stay blocked while a file is quarantined or incomplete.
A steward may request release only with a reason, and the file must pass a fresh scan before quarantine clears.
Outcomes are stable enough for an application to show a person a meaningful next step.
The personal file path is designed for real working conditions, where a network drops, a file is revised, and every successful operation needs a durable and replayable outcome.
An interrupted transfer is designed to continue from an offset that was only acknowledged once it was durably committed.
The declared size and checksum must match before a file is sealed.
An application does not need to hold an entire large object in memory to work with it.
An authorised application can retrieve only the part of a clean object it actually needs.
System categories alongside custom folders, with rename and controlled movement.
A changed file becomes a distinct ingestion input, while replaying the same version stays idempotent.
After a clean verdict, Vault can place files using file type and provenance signals. You can rename and move them. Once a person chooses a location, later scans may suggest another folder but do not overwrite the manual placement.
File type, extension, and provenance metadata decide the initial category. Documents remain the safe default. Nothing here claims to understand what the file means.
A later check can make a suggestion, but it never quietly relocates a file that someone has already put where they want it.
When a user or a policy deliberately admits a ready personal file, Vault records which project, file, and version entered the ingestion queue. The Knowledge Substrate then performs its governed work: parse, classify, extract, score, attribute, and write.
Repeating the same request does not duplicate the source. Changing the file creates a new version for a new ingestion.
Knowledge can point back to the project file and version that supplied the material.
The clean file remains available for a controlled retry, rather than being lost or half-admitted.
You see what a deletion would affect before it commits, and it does not bypass governance.
Corvair pairs each external project with one Knowledge base, one Memory instance, and one Vault. Access to personal Vault material resolves through the paired Knowledge base and the caller's project permissions. The Vault remains a supporting source, not the institutional system of record.
The Vault view in the Corvair workbench: personal knowledge, current status, and governed actions in one place.
Vault lets each person supplement the core Knowledge Substrate with material of their own. Memory preserves continuity, while the substrate remains the governed authority for the institutional knowledge that people and agents rely on.