The vocabulary behind current state.

Governed state

Shared database state accepted from observations under the configured ontology and policies. Current state and mutation history are separate views.

Record

An entity and its current facts and relations after consolidation.

Proposal

A candidate change evaluated by the service. It may be applied, skipped, refused, or held for review.

Flexible

Database mode in which agents can propose schema changes with vocabulary and consistency checks. The API value is free; this mode does not override class or field constraints.

Model-driven

Database mode based on an explicitly adopted model. Semi-restricted allows validated agent schema proposals; Restricted reserves schema changes for authenticated human editors.

Open class

A class that accepts undeclared fields. Supported conformance findings are advisory unless a field is enforced or an opt-in policy refuses the proposal.

Strict class

A class that refuses undeclared fields and supported type, value, or relation mismatches. Strictness is inherited; missing required fields remain advisory.

Supersede

Replace a previous current fact with a new current value while preserving the earlier value in history.

Review

An authorized human or agent decision on a proposal held by policy. A held proposal is not yet current state.

Canonical ID

The entity reference returned by the service, typically type:slug. Save it or the entity UUID from the receipt; an input entityRef may normalize differently.

Observation

The write primitive. A proposal about the world — entity type, data, optional relations, and required provenance — not a direct edit to stored state.

Consolidation

The step that turns an observation into typed operations. Duplicates collapse into the existing record, new values supersede old ones, and policy can refuse a write or hold it for review.

Ontology

The schema that governs what can exist: classes, predicates with value types and cardinality, and typed relation types with a domain and range. Strict classes refuse undeclared fields and invalid values. Open classes report supported violations without blocking, unless a predicate is enforced. Required fields remain advisory.

Fact

A predicate and value on an entity, with a status of current, superseded, retracted, disputed, or pending review.

Current state

The records accepted under the configured rules and received observations. Read the current record for an action, or inspect earlier values and changes through history.

Provenance

The origin recorded on every mutation: source, actor, confidence, timestamp, and extraction method.

Policy

The per-class and per-predicate rules that decide an update: supersede, confidence-weighted arbitration, rejection, or routing to human review.

Bitemporal fact

A fact carrying both valid time (when the value was true of the world) and transaction time (when it was recorded), with historical entity reads along the valid-time axis.

Projection

A derived view of database state — a Markdown entity page, a summary, an export. Projections are never the source of record, and editing one changes nothing.

Console actions use “Propose an update” and “Search current state”. Tool names such as memory_insert and public API fields remain unchanged. Older database mode labels “Free” and “Open schema” correspond to Flexible; Open and Strict describe classes.