# Glossary | Corvair Knowledge Substrate

Glossary of Corvair Knowledge Substrate terms in plain words: passage, claim, source tier, context, learning, checksum, warrant, seal, ledger and many more.

Canonical: <https://corvair.ai/cks/glossary.html>

## A to C

### Active content

Macros, scripts or hidden instructions inside a file that could run, or mislead an AI that reads it.

### API

The one versioned HTTP API every caller goes through. It resolves the tenant and identity, applies the caller's scopes and shows a preview before any change. See [route groups](https://corvair.ai/cks/api.html).

### Background work

Work that nobody is waiting for, such as batch writing, quick judgements, scheduled crawls and link runs. It runs behind the API, so a reply never waits for it.

### Batch work

Writing that nobody is waiting for, sent in a batch at half price.

### Binding

The tie between the three stores. Each project or account is bound to one knowledge base, one memory and one Vault, and they feed each other.

### Cached

Part of a prompt the AI provider has seen in the call just before. It is charged at a lower rate and read faster.

### Canvas

A workspace that lays an analytical frame over one topic, with each part sourced from the base. A framed topic can be explored, reused or exported as a report. See [Knowledge](https://corvair.ai/cks/product.html#canvas).

### Chain

Each warrant points to the one before it, so none can be removed or altered without the break showing.

### Checksum

A fingerprint of a file's bytes. Any change to the file gives a different checksum.

### Cited answer

An answer that shows the passages it was built from, so anyone can read the source.

### Claim

A single statement of fact in a document, such as "the pump is rated to 40 bar". Claims are pulled out and checked one by one.

### Claim link

A link between claims across documents: one supports, depends on or contradicts another. A scheduled link run finds them, and they are kept beside the document records, not in them.

### Command line (cks)

The program that drives the Knowledge Substrate through its HTTP API. Every change it makes shows a preview first. See [API, MCP and the command line](https://corvair.ai/cks/api.html).

### Commitment

A sealed stand-in for one part of a warrant. It can be checked against that part, but reveals nothing by itself.

### Company library

A shared knowledge base that holds a company's own documents and files. In Corvair Virtual Worker it sits behind the Reference pages.

### Context

What an agent is given to read before it answers: its instructions, what is known about the account, and the conversation so far.

### Contradiction

Two claims that cannot both be true. Answers that use either one say so.

### Conversation

One thread of messages between people and agents, by any channel, kept in order.

### Crawl

A scheduled read of your own website and the competitor, industry and regulator sites a recipe lists. the Knowledge Substrate pays only for what changed.

## D to G

### Decision

Two meanings. A decision the Knowledge Substrate makes on its own, such as settling a contradiction, is listed with its reason and can be undone. A decision made by a person or agent is what a warrant binds to its facts, sources and authority.

### Digest

A short fingerprint of some content. The same content always gives the same digest, and the content cannot be worked out from it.

### Discovery plane

The side of the Knowledge Substrate that reaches the open web. It runs in the cloud, can be pinned to a jurisdiction or switched off, and only instructions cross out to it. See [Security and regions](https://corvair.ai/cks/security.html).

### Drift

A source has changed since the warrant was sealed. It is reported as advice, not as a failure.

### Erased part

A part of a warrant whose content has been erased. It is reported as erased, not as a failure, and the warrant still checks.

### Erasure

Removing a person's or a project's content on request, with a record that it was done.

### Event

One entry in a conversation: a message, decision or hand-over. Each event gets a fixed place and is never rewritten.

### File states

The one set of states a Vault file moves through, enforced on the server: uploading, scanning, checked, ready, and needs attention. A file that is not clean is on hold. See [Vault](https://corvair.ai/cks/vault.html).

### Fixed form

The first sealing step: the warrant record is put in one exact form, so the same record always gives the same digest.

### Gap

A topic where people search often and find little. A heat map marks gaps, and the Knowledge Substrate can fill the ones you pick.

### Gate

The point where the Vault hands a clean, version-pinned file to knowledge. Uploading a file never makes it company knowledge by itself.

### Generated file

A file an agent or service made, such as a quote or a report.

### Governance key

The key Corvair signs warrants with. It is held in a key service and never exported.

## H to M

### Heat map

A count of documents, claims and fresh sources for each topic, with a gap marked where people search often and find little. See [Knowledge](https://corvair.ai/cks/product.html#heat-maps).

### History

Every conversation, kept in order. It can be searched by words, tags or topic.

### Key

A credential for scripts and the command line, with a name, scopes and an end date. Interactive use signs in through the browser instead.

### Kinds of learning

Preference, convention, fact, decision, exclusion, pattern, glossary and goal.

### Knowledge

The searchable base a checked version can be sent to. The Vault decides if a file is safe; knowledge decides if its content is true.

### Knowledge base

One collection of documents and websites for a company, a project or an account, searched as one.

### Knowledge plane

The side of the Knowledge Substrate that holds your content, the store, answers and warrants, in the region you choose. Sensitive content never crosses out of it.

### Learning

A statement drawn from many memories or conversations, such as a team decision or a common question.

### Ledger

A company's own chain of warrants, kept apart from its documents and conversations.

### Long-term memory

A short statement kept after a conversation ends, such as "Tom prefers email after 4 pm".

### MCP tool

An operation offered to AI assistants over MCP. Each tool forwards to its API route, so access rules apply once for every interface.

### Memory

The store that records each conversation in order and builds context from it. It holds memories and learnings per person, project or account. See [Memory](https://corvair.ai/cks/memory.html).

### Memory project

The project or account a memory belongs to. It is bound to one knowledge base, one memory and one Vault.

## N to R

### OKF record

The one record the Knowledge Substrate writes for each document in Open Knowledge Format, and treats as the record of truth. Each load is a new version, and the search tables can be rebuilt from it. See [Open Knowledge Format](https://corvair.ai/cks/okf.html).

### On hold

Kept from use until it passes its checks. A file on hold is never shown, previewed or read into knowledge.

### Open Knowledge Format

An open standard from Google Cloud for keeping knowledge as plain Markdown files. The Knowledge Substrate keeps each document as one record in it, and adds its own fields in a separate block.

### Outcome

What came of a decision: won, lost, granted, refused, reversed or other. It is sealed on the same chain, after the decision.

### Passage

A short piece of a document, usually a paragraph or two, that an answer can point to.

### Personal data flag

A note that a file contains names, numbers or other personal details. The file is not held; the application decides what to do.

### Premise

One fact, passage or file a decision rested on.

### Preview

What a change would do, shown before it happens. Every change, and every destructive operation, shows one first.

### Prompt

Everything an AI model is sent for one reply: the context plus the new message.

### Provenance

Where a generated file came from: the service, the run, the model and the time. It cannot be faked by the file's author.

### Recipe

The list a knowledge base is built from. It names the sites the Knowledge Substrate crawls and sets the rules for what stays.

### Region

Where your knowledge plane holds your content, chosen by you.

### Registered client

An application that has registered itself and its agents with the Knowledge Substrate. The Knowledge Substrate names no caller of its own, and each application seals warrants as the client it is registered as.

## S to W

### Scan

The three checks run on each Vault file: malware, active content and file type. Any doubt keeps the file on hold, with the reason shown. Personal data is found and flagged, not held.

### Scope

A limit on what a key or caller may do. The command line keys carry read, write or admin, and every request is limited to what the person or agent may see.

### Seal

To fix a warrant so it can never be changed unnoticed: it is put in one exact form, signed, timestamped and chained.

### Search tables

The tables of passages, topics, terms, tags and claims that serve search, answers, heat maps and the Canvas. They are built from the OKF records with no model call.

### Source rule

A rule to keep, exclude or purge sources that match it. Each rule shows what it would change before it is applied.

### Source tier

How far a source is trusted, set by where it came from: Tier 1 licensed expertise, Tier 2 your own content, Tier 3 outside sites, Tier 4 generated by an agent.

### Summary

A short account of earlier turns, written in the background so the agent can keep the thread without reading everything.

### Template

A form that turns a framed topic on the Canvas into a structured deliverable with a rubric.

### Tenant

An agency, or one customer organisation, with its own space in the Knowledge Substrate. Its content, memory, files and ledgers stay inside it unless it allows more.

### Thumbnail and preview

Small images and readable copies made for each version, so a file can be seen without downloading it.

### Timestamp

Proof from an independent time service that the warrant existed at that moment.

### Topic

A subject the base is organised by, such as "compressor maintenance". The heat map counts how well each topic is covered.

### Topic map

The set of topics for a base. It grows by suggestion: a model proposes topics next to the ones you have, and sources decide what stays.

### Turn

One message and the reply to it.

### Two planes

The split between your knowledge plane and the discovery plane. Data goes one way: sensitive knowledge stays in your plane, and only checked findings come back. See [Security and regions](https://corvair.ai/cks/security.html).

### Undo

The way to reverse a decision the Knowledge Substrate or Memory made on its own. Each is listed with its reason.

### Validity

How far a statement can still be relied on, given its age and what kind of content it is.

### Validity Warrant

A sealed record of what a decision or an answer rested on, who made it and when.

### Vault

The store for files people add and files agents make. Each file is scanned and held only for malware, active content or file type, and personal data is flagged, not held. Only clean, version-pinned files pass the gate to knowledge. See [Vault](https://corvair.ai/cks/vault.html).

### Verify

To check a warrant. Seven mechanical checks need only the warrant, the published key and the timestamp chain.

### Version

A fixed copy of a file. Uploading a changed file makes a new version; old versions never change.

### Warrant

Short for Validity Warrant. A warrant is made for a decision, and for an answer or generated file only when asked.
