Skip to content

Polymorphism and Reference Workloads

V9 is designed around one common architecture and many native knowledge shapes.

Pokémon

Large homogeneous relations stress factorization, dictionaries, segmentation and localized reads/rebuilds.

Recipes

A ProcedureGraph is a domain-native DAG. Portable v6 assertions can be derived without replacing the procedure graph as canon.

DOMAIN-NATIVE CANON != PORTABLE PROJECTION

VehicleDiag

Conditional multiplex graphs require ports, typed connections, operating-state conditions and path convergence. Generic flattening must not destroy operational structure.

Pi Theory / PrimeBridge

Small or research-oriented corpora can remain composite/inline. V9 must not impose large-scale storage machinery on them.

HospitalOps

Composition must preserve security and authority boundaries between commons, practice, identity vaults and audit systems.

UCKK

Hierarchical parent Kristals pin child states without copying child semantic content.

MathKristal

Formula IR, Theory Graph, Proof Graph, Representation Graph and derived Action Graph remain distinct authorities/contracts.

kOA Ecosystem

A heterogeneous property graph preserves repository, capability, authority and workflow distinctions.

Acceptance question

For every proposed core feature ask:

  1. Does it preserve native logical shape?
  2. Does it preserve authority boundaries?
  3. Can a small Kristal remain simple?
  4. Can a huge Kristal avoid monolithic amplification?
  5. Can indexes be deleted without destroying canon?
  6. Can multiple physical encodings share one Logical Commitment?

If not, the feature likely belongs in an optional profile/tool rather than the v9 core.