Skip to content
EN FR

Persistent Hypergraph Architecture

Documentation status: architecture — see Maturity and evidence.

The conceptual hypergraph has a persistent execution path in the current engine. Persistence is not modeled as a separate business graph: it is an implementation of the same conceptual identities, nodes, relations and indexes with durable storage responsibilities.

Verified architectural responsibilities

The current engine source shows a persistent hypergraph layer with:

  • disk-backed segment management;
  • memory-mapped file support;
  • stable node identifiers across stored segments;
  • persistent indexing, including formal-name/string indexing paths;
  • transaction contexts scoped to execution threads;
  • explicit and automatic transaction modes;
  • write-ahead journal staging before durable data application;
  • background coordination for journal processing and indexing.

Transaction boundary

Writes are associated with a transaction. An explicit transaction is committed by the caller; automatic transactions can be created for isolated write operations. A transaction reaches a commit state before its staged changes are emitted as a committed journal batch.

conceptual change
  -> transaction context
  -> staged journal records
  -> commit boundary
  -> durable segment/index application

This separation is important because conceptual mutation, transaction intent and physical persistence are different concerns.

Public programming rule

Application code should use the public Runtime/model transaction and persistence contracts. Disk segments, journal block layouts, memory mapping and internal coordinator threads are implementation details and may change without changing the conceptual model.

What this page does not promise

The source clearly establishes persistent storage and write-ahead journaling architecture. This page does not define a public recovery-point objective, recovery-time objective, replication guarantee or crash-recovery SLA. Those guarantees require a separately certified operational contract and test matrix.

See Durability and WAL for the journal boundary.