Specification
Versions
Versioning policy: additive within a major · breaking ⇒ new major + migration path
Graph-native data model: typed nodes and edges, activation energy, Hebbian weights, temporal decay, graph-merge composition, scoped names, three conformance levels.
Five static layers (knowledge, patterns, graph, session, gotchas). Readable by every v2 implementation via the documented v1→v2 mapping.
Stability promise
In plain terms: the specification is the rulebook — it defines exactly what
a .ctxpkg file is, so every tool reads it the same way. Published
versions never change behind your back.
A published specification document never changes retroactively — errata are
listed, never silently merged. Drafts (-draft) carry no stability
promise. The node-type and edge-type taxonomies are registries: entries are
never removed, only deprecated. See Governance for
the full versioning policy and RFC process.