Skip to content
EN FR

Hypergraph Implementation Boundary

Documentation status: architecture — see Maturity and evidence.

The Runtime implements conceptual hypergraph semantics across in-memory and persistent execution paths. Public documentation describes the invariants that applications can depend on, not private classes or storage layouts.

Stable responsibilities

The implementation must preserve:

  • conceptual and instance identity;
  • typed/polyadic relation roles;
  • constraints and special dimensions;
  • traversal and iterators;
  • indexes and formal-name resolution;
  • transaction boundaries;
  • persistent storage when configured;
  • observable errors and diagnostics through public Runtime contracts.

Memory and persistence are execution choices

A conceptual model should not be rewritten merely because its hypergraph is memory-resident or disk-backed. Persistence adds storage, transaction and durability responsibilities while keeping the conceptual contract stable.