Universe, galaxies, Worlds, organisms, biology, anatomy, atoms, physical reality, and governed emergence, bound into one formal ontology.
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.
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.
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
Recommendations in this document are explicitly labeled RECOMMENDED V0.1, so a proposal is never mistaken for a settled decision.
Material changes require an architecture decision record, impact analysis, test plan, rollback plan, and a named authority.
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.
Some named metaphors in the conversation were exploratory; this document normalizes them into formal objects.
Document map: eight divisions
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.
Metaphor is not ontology. Every named thing must answer seven questions:
What is its canonical ID?
Who writes its state?
What contract does it expose?
What evidence supports it?
What authority does it have?
What resources does it consume?
What outcomes retire or strengthen 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.
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.
| Metaphor | Formal object / function | Failure if misunderstood |
|---|---|---|
| DNA / genome | Constitution, invariants, schemas, recipes, policies, compatibility, lineage, and lifecycle. | Treating prompts or marketing language as immutable law without version or evidence. |
| Amino acid / atom | Smallest typed ingredient, capability, or signal node. | Components without contracts cannot safely compose. |
| Protein | Agent or transformation performing work from instructions and context. | Giving workers broad identity or authority, or product ownership. |
| Cell | Bounded runtime unit with state, interfaces, resources, health, and lifecycle. | Hidden mutable state and unclear boundary. |
| Tissue / cluster | Temporary interoperable capability assembly for a function. | Permanent duplicated teams tied to products. |
| Organ | Specialist engine with bounded domain truth and authority. | One universal model pretending to own every domain. |
| Nervous system | AXON events, correlation, subscriptions, retry, pause/resume, escalation. | Parallel message buses and silent side effects. |
| Blood | Evidence, state, messages, money, compute, attention, trust, and outcomes moving through the system. | Data movement without provenance, rights, or economic accounting. |
| Heart / metabolism | Resource and value conversion loop that keeps commitments moving and outcomes returning. | Activity without closed-loop value or learning. |
| Brain | Human command, world model, allocator, planning, governance, and conscious review. | An agent falsely treated as sovereign or unaccountable. |
| Arms / hands / legs / feet | Execution adapters, field operators, integrations, devices, logistics, and physical actions. | Strategy disconnected from real-world capability and constraints. |
| Immune system | Security, governance, policy, shadow analysis, abuse detection, consequence, rollback. | Autonomy without containment or stakeholder protection. |
| Microbiome / bacteria | External models, providers, adapters, helpers, and local ecosystems extending capacity. | Letting a provider become core truth or silently contaminate state. |
| Metaphor | Formal interpretation |
|---|---|
| Atom | A canonical typed node or ingredient whose interface and state can be composed. |
| Bond | A typed relationship or compatibility edge with direction, evidence, authority, and lifecycle. |
| Molecule | A versioned recipe or workflow assembled from ingredients. |
| Field | Contextual influence over opportunity: demand pull, risk, trust, urgency, decay, strategic gravity, and resource cost. |
| Energy | Finite capacity to change state: capital, compute, attention, labor, relationship goodwill, time. |
| Entropy | Drift, duplication, unresolved state, stale evidence, unfinished work, and maintenance burden. |
| Gravity | A persistent force attracting resources and actors because of expected value, strategic importance, or dependency. |
| Orbit | A recurring but not completed loop around an opportunity, customer, or decision; useful when scheduled, dangerous when it becomes founder rumination. |
| Planet / World | Bounded domain environment with stable rules, participants, state, and market or workflow surfaces. |
| Galaxy | Portfolio of related Worlds with shared infrastructure, strategy, capital allocation, and interactions. |
| Universe | The 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
}
The metabolism loop
Seven metabolic functions
| Function | System mechanism |
|---|---|
| Ingestion | Sensors, user input, files, feeds, field observations, APIs, transactions. |
| Digestion | Normalization, identity resolution, evidence, context, contradiction, rights. |
| Energy allocation | Cockpit allocator assigns compute, capital, people, time, and authority. |
| Synthesis | Recipe Engine composes capabilities into strategies, Foods, and action proposals. |
| Movement / action | Agents, integrations, humans, logistics, communications, and physical execution. |
| Waste / removal | Suppress, archive, retire, deduplicate, expire, and safely handle failed or harmful state. |
| Growth / repair | Outcomes calibrate recipes and models and build reusable capability, documentation, relationships, and trust. |
Microbiome admission rules: what an external provider must satisfy to extend capacity
Cluster-to-bloom gates: seven stages, each with a gate that must be passed
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
| Question | Why 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. |
| Physical layer | Required objects and controls |
|---|---|
| Observation | Photos, video, audio, documents, IDs, serials, sensor readings, measurements, field notes, time and location, source and rights. |
| Identity / custody | Owner and authority, asset tag, title, location, custody chain, inspection, transfer, evidence integrity. |
| Condition / state | Observed, claimed, and verified condition, changes, repairs, environment, uncertainty, safety. |
| Human capability | Skill, certification, trust, territory, availability, equipment, insurance, pricing, performance. |
| Logistics | Access, route, loading, storage, transport, weather, appointment, handoff, cost, failure. |
| Execution authority | Permission to enter, inspect, move, repair, communicate, spend, bind, transfer, or dispose. |
| Outcome proof | Signature, photo, telemetry, payment, title or receipt, completion, quality, dispute, satisfaction. |
| Offline / edge | Local queue, encrypted cache, synchronization, conflict resolution, and explicit observed versus verified state. |
Voice-to-execution: from spoken intent to updated estimate
Identity is singular. One canonical identifier; multiple names and representations allowed.
State is explicit. Intended, declared, observed, verified, and deployed are not silently conflated.
Evidence is traceable and uncertainty survives compression.
Authority is bounded and credentials do not grant permission.
Resources are finite and economically accounted.
Context changes weight. No metric, model, or strategy dominates all Worlds.
Learning changes future behavior only after controlled evaluation and promotion.
Irreversibility requires stronger evidence and authority.
Every object has lifecycle, decay, retirement, and tombstone state.
Products and Worlds import core contracts; they do not fork the core.
Outcomes outrank persuasive narratives.
Negative evidence, disagreement, and failure remain visible.
Complexity must pay rent.
Engineering acceptance: seven tests, each with a pass condition
| Test | Pass condition |
|---|---|
| Semantic zoom | The same object can be inspected from Universe to World to run to ingredient without losing identity or lineage. |
| No duplicate truth | Metaphor views project canonical objects rather than creating separate state stores. |
| World portability | A new vertical can install a pack and run through the shared substrate without a core fork. |
| Transfer limits | Capabilities declare where cross-domain reuse is invalid or unproven. |
| Physical evidence | Observed field state retains source, time, location, and custody, and is not silently labeled verified. |
| Emergence gate | A product, World, or bloom claim requires repeatable outcome and lifecycle proof. |
| Retirement | Stale Worlds, recipes, providers, or nodes can be superseded or retired without erasing history. |
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 class | Use in this document | Evidence limitation |
|---|---|---|
| Conversation thread | Founder 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 Canon | Shared 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 Dossier | Sense-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 canon | Ingredient 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 codices | DeedSonar, real-estate, launch, partner, cockpit, and implementation patterns. | Reusable only where current identity, contract, code, and authority are reconciled. |
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.