A current record you can inspect.

Information can be late, duplicated, incomplete, or conflicting. Consolidation checks each proposal against the model, current state, and policy. The caller sees what was applied, skipped, or held, along with violations, and can act on that result.

Current-state queries read accepted facts directly. Earlier values stay available separately, with the periods when they were recorded as valid. This lets an agent answer a current question and investigate an earlier value without mixing the two.

Open classes accept undeclared fields and report type, allowed-value, and relationship mismatches without blocking unless a field is enforced. Strict classes refuse those writes. An enforced field can reject an invalid type or value on an open class. Missing required fields are advisory in both modes.

Schema changes go through a proposal service that validates the complete candidate schema before applying it. An expected revision can guard against a stale change, and applied changes are audited. Templates are adopted explicitly. Agent permission to change schema depends on the instance’s governance settings; human administration requires authenticated user access.

Source, actor, confidence, timestamp, and extraction method make each mutation inspectable and support conflict decisions and review. They document the evidence behind a recorded fact. The quality of that fact still depends on the observations and policies you provide.

Markdown pages, summaries, and exports are generated from the database. Editing one does not mutate stored state. A correction goes back through the proposal path, where the same ontology, policy, and provenance requirements apply.

Inside the managed ConceptMem service. Clients submit observations and schema proposals through hosted REST or MCP; the TypeScript SDK is in preview. The service validates and applies proposals according to the caller’s authority and workspace rules.