Neuruh internal canon Document visuals Source: 08_Neuruh_Unified_Ontology_and_World_Landing_Codex_v1.pdf

Unified Ontology and World Landing Codex

Universe, galaxies, Worlds, organisms, biology, anatomy, atoms, physical reality, and governed emergence, bound into one formal ontology.

Version
1.0
Snapshot
August 1, 2026
Prepared for
Jeramie Hicks / Neuruh
Class
Internal founder canon and execution blueprint
Executive ruling

The cosmic, biological, human, and atomic metaphors are all scale views of one governed opportunity architecture. The formal ontology, not the metaphor, controls identity, state, evidence, authority, resources, transformation, lifecycle, and outcomes.

Possibility

Architecture is not runtime proof.

Opportunity

A possibility is not an opportunity until it survives qualification.

Value

An opportunity is not value until an outcome is realized and measured.

CONTROL

Document control and integrity rules

Page 2 of the Codex. These rules govern how every claim in the document is labeled.

Truth hierarchy: canonical contracts and runtime evidence outrank metaphorical explanation. Scope: a formal binding of all metaphors in the source thread and a protocol for entering new digital or physical Worlds. It extends the existing Neuruh Universe and Opportunity Organism canon; it does not introduce a second universe or organism.

Status discipline: every claim carries one of these seven labels

CANONICAL VERIFIED RELEASE QUALIFICATION BUILT-NOT-WIRED SPEC-ONLY HISTORICAL UNKNOWN
Recommendation label

RECOMMENDED V0.1

Recommendations in this document are explicitly labeled RECOMMENDED V0.1, so a proposal is never mistaken for a settled decision.

Change rule

Five-part change gate

Material changes require an architecture decision record, impact analysis, test plan, rollback plan, and a named authority.

No-fabrication rule

Architecture is established. Liveness is not.

The conversation and retrieved canon establish the architecture and direction. They do not prove every adapter, model, provider, integration, workflow, customer, or revenue claim is live. The document separates established decisions from recommended specifications and unresolved evidence.

Known unresolved evidence

Exploratory metaphors, normalized

Some named metaphors in the conversation were exploratory; this document normalizes them into formal objects.

Document map: eight divisions

DIVISION I

Why multiple metaphors appeared

Each metaphor exposes a different design problem.

The conversation moved through Worlds, galaxies, atoms, DNA, proteins, bacteria, brain, nervous system, blood, heart, arms, legs, and physical reality. That movement was not random. Each metaphor exposes a different design problem: scale, composition, specialization, signaling, resource flow, command, protection, adaptation, and emergence.

The danger is literalizing the metaphors into duplicate software: one "atomic" registry, another "DNA" engine, a "brain" router, a "bacteria" swarm, and a "world" store that all represent overlapping truth. The cure is one formal ontology with multiple human-readable views.

Invariant

Metaphor is not ontology. Every named thing must answer seven questions:

Q1

What is its canonical ID?

Q2

Who writes its state?

Q3

What contract does it expose?

Q4

What evidence supports it?

Q5

What authority does it have?

Q6

What resources does it consume?

Q7

What outcomes retire or strengthen it?

DIVISION II

Formal scale ontology

Select any term to read 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. A household asset, a buyer campaign, a product, a company, and a World differ in scope and contracts, not in the need for this grammar.

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
}

Five state values are kept distinct on every node: intended, declared, observed, verified, deployed. Division VIII makes the rule explicit: they are never silently conflated.

DIVISION III

Biology and anatomy mapping

Each metaphor, its formal object, and the failure that follows if it is misunderstood.
MetaphorFormal object / functionFailure if misunderstood
DNA / genomeConstitution, invariants, schemas, recipes, policies, compatibility, lineage, and lifecycle.Treating prompts or marketing language as immutable law without version or evidence.
Amino acid / atomSmallest typed ingredient, capability, or signal node.Components without contracts cannot safely compose.
ProteinAgent or transformation performing work from instructions and context.Giving workers broad identity or authority, or product ownership.
CellBounded runtime unit with state, interfaces, resources, health, and lifecycle.Hidden mutable state and unclear boundary.
Tissue / clusterTemporary interoperable capability assembly for a function.Permanent duplicated teams tied to products.
OrganSpecialist engine with bounded domain truth and authority.One universal model pretending to own every domain.
Nervous systemAXON events, correlation, subscriptions, retry, pause/resume, escalation.Parallel message buses and silent side effects.
BloodEvidence, state, messages, money, compute, attention, trust, and outcomes moving through the system.Data movement without provenance, rights, or economic accounting.
Heart / metabolismResource and value conversion loop that keeps commitments moving and outcomes returning.Activity without closed-loop value or learning.
BrainHuman command, world model, allocator, planning, governance, and conscious review.An agent falsely treated as sovereign or unaccountable.
Arms / hands / legs / feetExecution adapters, field operators, integrations, devices, logistics, and physical actions.Strategy disconnected from real-world capability and constraints.
Immune systemSecurity, governance, policy, shadow analysis, abuse detection, consequence, rollback.Autonomy without containment or stakeholder protection.
Microbiome / bacteriaExternal models, providers, adapters, helpers, and local ecosystems extending capacity.Letting a provider become core truth or silently contaminate state.
DIVISION IV

Physics, atomic, and cosmic mapping

The same objects, read through a physics lens.
MetaphorFormal interpretation
AtomA canonical typed node or ingredient whose interface and state can be composed.
BondA typed relationship or compatibility edge with direction, evidence, authority, and lifecycle.
MoleculeA versioned recipe or workflow assembled from ingredients.
FieldContextual influence over opportunity: demand pull, risk, trust, urgency, decay, strategic gravity, and resource cost.
EnergyFinite capacity to change state: capital, compute, attention, labor, relationship goodwill, time.
EntropyDrift, duplication, unresolved state, stale evidence, unfinished work, and maintenance burden.
GravityA persistent force attracting resources and actors because of expected value, strategic importance, or dependency.
OrbitA recurring but not completed loop around an opportunity, customer, or decision; useful when scheduled, dangerous when it becomes founder rumination.
Planet / WorldBounded domain environment with stable rules, participants, state, and market or workflow surfaces.
GalaxyPortfolio of related Worlds with shared infrastructure, strategy, capital allocation, and interactions.
UniverseThe shared substrate and laws within which all Worlds and components exist.

Formal relationship contract: every bond is a typed, evidenced object

relationship = {
  relationship_id, type, from_id, to_id,
  direction, world_scope, evidence_refs[], confidence,
  rights, authority, constraints[], economics?,
  valid_from, valid_to?, state, provenance, version
}
DIVISION V

Metabolism, microbiome, clusters, and bloom

How the organism converts input into outcomes, and how new structures earn their existence.

The metabolism loop

New Possibility feeds back into the loop as fresh intent and resources. Nothing exits without an outcome returning.

Seven metabolic functions

FunctionSystem mechanism
IngestionSensors, user input, files, feeds, field observations, APIs, transactions.
DigestionNormalization, identity resolution, evidence, context, contradiction, rights.
Energy allocationCockpit allocator assigns compute, capital, people, time, and authority.
SynthesisRecipe Engine composes capabilities into strategies, Foods, and action proposals.
Movement / actionAgents, integrations, humans, logistics, communications, and physical execution.
Waste / removalSuppress, archive, retire, deduplicate, expire, and safely handle failed or harmful state.
Growth / repairOutcomes calibrate recipes and models and build reusable capability, documentation, relationships, and trust.

Microbiome admission rules: what an external provider must satisfy to extend capacity

  1. External model or provider has a typed contract and limited authority.
  2. Data rights, privacy, retention, cost, latency, coverage, and failure are known.
  3. Outputs are evidence, candidate transformations, or proposals, not unquestioned truth.
  4. Health and drift are monitored; fallback or removal is possible.
  5. The organism keeps canonical identity and state and can change providers without losing its memory or product contract.
  6. External capacity improves outcome or economics enough to justify the added entropy.

Cluster-to-bloom gates: seven stages, each with a gate that must be passed

DIVISION VI

World Landing Protocol

The protocol imports laws and capabilities, then specializes only what the domain requires.
STEP 1 / 11

Observe

The world contract: what a landed World must declare

world_definition = {
  world_id, version, name, purpose, owner, status,
  actors[], assets[], events[], demand_supply_models,
  ontology_extensions[], rules[], policies[], jurisdictions[],
  evidence_sources[], identity_methods[],
  installed_ingredients[], organs[], recipes[], products[], emitters[],
  economics, resource_budgets, authority_model,
  success_metrics[], outcomes[], transfer_limits[],
  dependencies[], interfaces[], lifecycle, receipts
}

Ten landing questions, and why each one matters

QuestionWhy it matters
What changes state in this World?Defines events, transitions, decisions, opportunities, and timing.
Who owns or controls what?Identity, authority, incentives, consent, and transaction ability.
What is valuable to whom?Prevents optimizing one actor while destroying value elsewhere.
What evidence is trusted?Determines confidence, claims, qualification, and professional review.
What rules and risks bind action?Jurisdiction, licensing, safety, privacy, ethics, contracts, and irreversibility.
Where is supply, demand, or capacity fragmented?Reveals market or orchestration opportunities.
Which existing capabilities transfer?Reduces build time without assuming domain equivalence.
What must remain human or physical?Sets realistic automation and field requirements.
What outcome closes the loop?Prevents endless analysis and defines learning.
When does this become a product or World?Sets phase-transition gates and avoids metaphor inflation.
DIVISION VII

Physical-world execution

Eight layers, each with required objects and controls.
Physical layerRequired objects and controls
ObservationPhotos, video, audio, documents, IDs, serials, sensor readings, measurements, field notes, time and location, source and rights.
Identity / custodyOwner and authority, asset tag, title, location, custody chain, inspection, transfer, evidence integrity.
Condition / stateObserved, claimed, and verified condition, changes, repairs, environment, uncertainty, safety.
Human capabilitySkill, certification, trust, territory, availability, equipment, insurance, pricing, performance.
LogisticsAccess, route, loading, storage, transport, weather, appointment, handoff, cost, failure.
Execution authorityPermission to enter, inspect, move, repair, communicate, spend, bind, transfer, or dispose.
Outcome proofSignature, photo, telemetry, payment, title or receipt, completion, quality, dispute, satisfaction.
Offline / edgeLocal queue, encrypted cache, synchronization, conflict resolution, and explicit observed versus verified state.

Voice-to-execution: from spoken intent to updated estimate

  1. Preserve the original utterance and timestamp; do not replace it with only a polished summary.
  2. Segment observation, hypothesis, decision, command, question, constraint, and emotion or priority signal.
  3. Link statements to existing objects; create candidates rather than silently rewriting canon.
  4. Expose ambiguity and ask only decisive clarifications.
  5. Generate artifacts and tasks with owners, definitions of done, evidence, and approval classes.
  6. Return execution and outcomes to the same thread or World, so founder understanding evolves with reality.
DIVISION VIII

Engineering contracts and emergence gates

Thirteen universal invariants, then the acceptance tests that prove them.
01

Identity is singular. One canonical identifier; multiple names and representations allowed.

02

State is explicit. Intended, declared, observed, verified, and deployed are not silently conflated.

03

Evidence is traceable and uncertainty survives compression.

04

Authority is bounded and credentials do not grant permission.

05

Resources are finite and economically accounted.

06

Context changes weight. No metric, model, or strategy dominates all Worlds.

07

Learning changes future behavior only after controlled evaluation and promotion.

08

Irreversibility requires stronger evidence and authority.

09

Every object has lifecycle, decay, retirement, and tombstone state.

10

Products and Worlds import core contracts; they do not fork the core.

11

Outcomes outrank persuasive narratives.

12

Negative evidence, disagreement, and failure remain visible.

13

Complexity must pay rent.

Engineering acceptance: seven tests, each with a pass condition

TestPass condition
Semantic zoomThe same object can be inspected from Universe to World to run to ingredient without losing identity or lineage.
No duplicate truthMetaphor views project canonical objects rather than creating separate state stores.
World portabilityA new vertical can install a pack and run through the shared substrate without a core fork.
Transfer limitsCapabilities declare where cross-domain reuse is invalid or unproven.
Physical evidenceObserved field state retains source, time, location, and custody, and is not silently labeled verified.
Emergence gateA product, World, or bloom claim requires repeatable outcome and lifecycle proof.
RetirementStale Worlds, recipes, providers, or nodes can be superseded or retired without erasing history.
PROVENANCE

Source basis and evidence limits

The Codex states its own basis plainly. This board keeps that framing.

This artifact is a synthesis and engineering expansion of the complete spoken thread plus pre-existing Neuruh founder canon retrieved from the File Library. It is not a verbatim transcript. Repeated or hazy dialogue was normalized into decisions, unresolved questions, architectural rulings, recommended specifications, and execution plans.

Source classUse in this documentEvidence limitation
Conversation threadFounder intent, corrections, commercial definition, launch concerns, market thesis, scoring concepts, swarm lanes, world and organism metaphors, desired next build.Spoken exploration contains provisional language and repetition; later founder corrections outrank earlier assistant framing.
Neuruh Universe CanonShared universe laws, world, galaxy, and product relationships, possibility collapse, evidence, authority, resource economics, outcomes, and no-duplication doctrine.Architecture prose is not runtime proof.
Opportunity Organism DossierSense-to-emergence lifecycle, value and consequence layers, recursive architecture, and world-to-outcome logic.Baseline architecture; requires current receipts for maturity claims.
Lead Recipes / Recipe Engine canonIngredient registry, goal-to-food compilation, recipe lifecycle, protected boundaries, Foods, outcome reconciliation, and vertical packs.The exact historical 49 real-estate ingredient inventory was not found as a verified list.
Existing product and operating codicesDeedSonar, real-estate, launch, partner, cockpit, and implementation patterns.Reusable only where current identity, contract, code, and authority are reconciled.
Unresolved evidence

The 49-ingredient question stays open. The founder referenced an existing 49-ingredient real-estate Recipe Engine set. This bundle defines the cross-vertical ingredient contract and starter registries, but it does not pretend to reconstruct the exact 49-item historical inventory without the source artifact.