Expand description
§pr4xis-runtime — load a .prx ontology as data, interpret it
The data-driven half of the North Star “praxis = .prx files + a runtime”.
Where pr4xis is the COMPILE-TIME ontology model (the ontology! macro and
the Category / Functor / FreeCategory traits) and pr4xis-domains holds
the compiled-in ontologies, this crate is the RUNTIME: it loads a .prx —
the serialized ontology — as DATA and interprets it, without the ontology
being compiled in.
§The load/store cycle is the free ⊣ forgetful adjunction
- A
.prxis a free-category presentation: generators + relations + connections-as-action-on-generators — open-world-generic by construction. - Load deserializes the bytes into that free form — always possible, no compiled types required.
- Rebind uses each connection’s serialized action-on-generators as the
interpretation a
FreeExtensionneeds to map the free generators into a closed-worldCategory: partially (unknown generators stay free — graceful open-world) and faithfully (a generator rebinds to a concept only when their content addresses agree).
§The runtime grounds only the hash
Everything the runtime knows about the .prx FORMAT it learns from the
meta-.prx (the ontology that defines the format). The one thing it cannot
learn by reference — because it is what reference MEANS — is the
content-address primitive (address). Identity bottoms out there.
§Status
Scaffolding the runtime kernel. First primitive: address (the hash
ground). The loader (bytes → free category), the rebind (FreeExtension →
closed world), the canonical codec, and the meta-.prx interpreter land on
top of it, per the consolidated build spine.
Modules§
- address
- Content-addressing — the one primitive the runtime GROUNDS.
- apply
apply— the data-drivenFreeExtension: interpret a loaded projection (GeneratorAction) over a sourceArchive, producing the target.- archive
- The
.prxarchive — the serialized ontology as a content-addressed set of definition-bearing nodes and the connections (morphisms) over them. - codec
- Canonical codec — DAG-CBOR, the deterministic encoding the content address is computed over.
- connection
- The connection — the uniform serialized morphism.
- definition
- Definition-bearing addressing — a node’s identity is the content address of its DEFINITION, not its name.
- grounding
- Grounding resolution — turning a
Groundededge’s foreign atom back into theDefinitionit names, by content-address agreement across the connected ontologies an archive declares. - load
- The fail-closed load gate — admit a
.prxonly after re-deriving its root and checking it against the trusted root. - meta
- The meta-ontology — the
.prxformat defined IN a.prx. - rebind
- Rebind — the closing half of the free ⊣ forgetful load/store cycle.
- recursive_
address - Recursive content-addressing — a concept’s address that transitively fixes its definition (referents by ADDRESS, not name), cycle-safe.