Neuruh · Unified Ontology and World Landing Codex

The ontology, running live

One formal ontology under every metaphor: Universe, Galaxy, World, organism, organ, atom. Pick a system, pick a candidate World, press run, and watch it execute. Land a World through the 11-step protocol, run the metabolism loop, climb the cluster-to-bloom ladder, or zoom one object from Universe to ingredient without losing its identity. Break it on purpose: the invariants and the emergence gate are the point of the demo.

Doctrine · possibility to value0 of 5 stages lit
Architecture is not runtime proof. A possibility is not an opportunity until it survives qualification. An opportunity is not value until an outcome is realized and measured.

World Landing Protocol

Speed

    Presenter script

    Six moves that show the whole ontology in about three minutes.

    1. Land the real-estate World. Run the Landing Protocol end to end. Approve the one founder gate at Run contained. Every step writes a receipt, and the doctrine strip fills: possibility, qualified, opportunity, outcome, value.
    2. Switch the candidate to the unbounded platform. Run again. The landing holds at Hypothesize value: no bounded domain, no named payer, no outcome that closes the loop. A possibility that cannot answer those is not an opportunity.
    3. Run the metabolism loop. Two full cycles. Watch Outcome feed Memory / Calibration / Capability, and New Possibility re-enter as fresh intent. Nothing exits the loop without an outcome returning.
    4. Climb the bloom ladder with evidence incomplete. The first gate holds. Flip evidence to complete and resume: the ladder only promotes what carries repeatable outcome and lifecycle proof.
    5. Inject a violation mid-run. Observed state labeled verified, a provider crowned as core truth, a core fork: the run halts on the spot and the log names the invariant it broke.
    6. Run the semantic zoom. One parcel signal descends Universe to ingredient. Same node_id at every level, lineage intact. That is acceptance test one, passing live.

    Seven questions

    Metaphor is not ontology. Every named thing in the system must answer all seven, or it is a label, not an object.

    • Q1 · Canonical ID
      What is its canonical ID?
    • Q2 · State writer
      Who writes its state?
    • Q3 · Contract
      What contract does it expose?
    • Q4 · Evidence
      What evidence supports it?
    • Q5 · Authority
      What authority does it have?
    • Q6 · Resources
      What resources does it consume?
    • Q7 · Outcomes
      What outcomes retire or strengthen it?

    Status discipline · every claim carries one label

    CANONICALVERIFIEDRELEASE QUALIFICATIONBUILT-NOT-WIREDSPEC-ONLYHISTORICALUNKNOWN

    Intended, declared, observed, verified, and deployed are five distinct state values on every node. They are never silently conflated.

    Invariants and acceptance tests

    Thirteen universal invariants bind every run on this page. The inject control breaks one on purpose; the seven acceptance tests are what a build must pass to claim the ontology works.

    Invariants

      Acceptance tests

        Formal scale ontology

        The containment stack, the substrate that runs through every level, and emergence. Select any term for its formal definition, exactly as the Codex states it. Scale invariance: the same grammar applies at every scale. An object has identity, state, relationships, evidence, capabilities, constraints, resources, authority, lifecycle, events, goals, actions, outcomes, and learning.

        Containment: largest to smallest
        Substrate: what runs through every level
        Emergence
        Term

        Universe

        The canonical node: one object shape at every scale.

        canonical_node = {
          node_id, node_type, names[], world_id?, parent_ids[],
          state: {intended, declared, observed, verified, deployed},
          evidence_refs[], claims[], conflicts[],
          capabilities[], constraints[], resources[], authority,
          relationships[], lifecycle, events[], goals[],
          actions[], outcomes[], versions[], provenance
        }