Neuruh Organism Codex OS · Master Document · Compiled July 15, 2026

One organism. Many organs.

Neuruh is Sovereign Opportunity Intelligence and Execution Infrastructure, implemented as a Modulated Agentic Opportunity Organism. It senses fragmented signals across property, businesses, markets, and physical assets, converts them into evidence-backed opportunities, and deploys specialized systems to capture the value. This board renders the master codex as visuals: the operating model, the real-estate organ pack, the contracts, the N-Cell topology protocol, and the governance plane that holds all of it.

DOCTRINE 01

Do not build isolated tools. Build organs that plug into one organism.

DOCTRINE 02

The organism owns memory, evidence, governance, orchestration, and output. Products own domain workflows and user-facing experiences.

DOCTRINE 03

Every claim traceable to evidence. Every calculation deterministic. Every external action passes governance.

10organism layers
16 + 6real-estate organs + shared organs
1,181IP registry records reconciled
59registered agents enumerated
103Autonomous Builder IP assets
71Dev Log project rows

The organism at a glance

Sense to outcome, one loop

Products are sensors, organs, recipes, interfaces, or emitters on one shared substrate. Nothing runs outside the loop: every execution returns evidence and outcomes to memory, so the whole system compounds instead of resetting.

Controlled learning closes the loop. N-Observer captures traces, N-Lab evaluates proposed changes in quarantine, governance approves promotion, and rollback stays available. Model outputs are not promoted to fact without provenance, freshness, conflict state, and policy handling. Model output is evidence, never command authority.

Section 2 · Operating model

The ten organism layers

The model separates core intelligence infrastructure from domain applications, so no product ships its own user table, data layer, prompt logic, reporting format, and half-baked memory system. Select a layer to see its responsibility and how it shows up in two different products.

Core rule: one organism, many organs. A product may own a UI and a domain workflow, but it must not own a separate memory layer, evidence layer, governance layer, or report engine. Every new product answers four questions: which contracts does it use, which organs does it call, which events does it emit, and which governance policies control it?

Section 4 · Product classification

Every product is one of five things

A sensor, an organ, a recipe, an interface, or an emitter. Some products combine roles, but the boundaries stay clean, and that is what lets hundreds of prompts, tools, agents, and apps cooperate without losing provenance or control.

Sensor

Finds signals in the world.

Neuruh SCANDeal RadarProbate Miner Permit MonitorDemand RadarLead Hunter SONA-X sensors

Organ

Performs specialist reasoning or calculation.

LandOSREI-XTaxShield AI UnderwriteXBusiness Buyability Analyzer Collector AIMIRROR-X1

Recipe

Coordinates several organs toward one outcome.

Acquire an off-market houseSplit and sell a parcel Buy an aging HVAC businessCatalog and resell an estate collection Missed roofing calls → appointmentsArchive → licensed IP

Interface

Lets a human operate the organism.

APG Land CRMDealOSNeuruh Cockpit FounderOSBookeitCustomer-facing apps

Emitter

Packages the result for the outside world.

Investor reportSeller offerAcquisition list CRM noteDevelopment memoContent package White-label agentAPIContractor scope Security alert

The moat

Not one prompt. The contract layer.

The real moat is the contract layer that lets the whole portfolio cooperate: shared identity, evidence, memory, orchestration, governance, and reports underneath every product.

Product = UI + domain recipes + permissions + customer context

What the customer sees and operates.

Organism = identity + evidence + memory + orchestration + governance + reports

What every product shares and none of them rebuild.

Section 4 · Product and service layer map

The portfolio on one substrate

Each product classified by its primary role and how it plugs into the organism. Filter by role.

Section 5 · Real Estate Organ Pack

Sixteen specialist organs, six shared

The domain package that turns the general organism into a deal acquisition engine: sixteen underwriting organs plus the shared comp, repair, market, risk, and offer infrastructure every one of them draws on.

Shared intelligence organs

Comparable Intelligence

Discovers, scores, rejects, adjusts, and explains comps. Rejected comps keep their reasons.

Used by: ARV, land, rental, multifamily, commercial, resale

Photo Repair Estimator

Turns property photos into repair scopes and inspection flags: rent-ready, wholetail, and retail-grade.

Used by: ARV, fix/flip, rental, wholetail, resale

Market Velocity

Measures liquidity, demand, supply, DOM, absorption, and heat, with input counts and data-sufficiency notes.

Used by: all acquisition engines

Offer Architecture

Builds cash, wholesale, novation, wholetail, seller-finance, and hybrid offers from approved scenarios.

Used by: all monetizable deals

Risk and Kill-Switch

Centralized red / yellow / green gating and escalation for every domain workflow.

Used by: all domain workflows

Strategy Composer

Compares routes on profit, risk, time, capital, and seller fit before an offer is proposed.

Used by: DealOS, APG CRM, REI-X

Section 3 · APG Land CRM on the organism

One deal, intake to receipt

APG Land CRM is the real-estate cockpit, not the brain. It captures leads and displays deal state; the heavy intelligence lives beneath it in the organs. Step through a single deal's path.

What the CRM must never do

  • Silently change ARV, MAO, repair math, or market velocity formulas.
  • Generate seller-facing offers without governance approval.
  • Store unsupported facts as truth. Facts are stored as claims with an evidence status.
  • Resolve zoning, title, legal, or tax conflicts without a human review path.
  • Become a second organism. The CRM is the cockpit. The organism is the machine.

Section 6 · Universal DealOS core

The opportunity lifecycle

DealOS is the shared real-world opportunity pipeline: real estate first, then resale, tax, bookings, content, and other verticals. Every opportunity moves through the same twelve states, and every state transition is an AXON event.

The ten core services underneath

Identity Service

Deduplicates people, companies, properties, assets, and opportunities. Canonical IDs, merge review, aliases, conflicting identifiers.

Universal Intake

Normalizes raw inputs into opportunities and evidence claims: forms, CSV, email, attachments, photos, notes, transcripts.

Evidence Service

Stores raw evidence and normalized facts with provenance. Immutable raw payloads, field-level evidence, conflict ledger.

Asset Router

Chooses which organs should run, with a multi-organ routing explanation and confidence.

Orchestrator

Coordinates events, retries, pauses, approvals, and receipts on the AXON event bus. Idempotent tasks, run correlation.

Calculation Service

Executes deterministic formulas: versioned formulas, decimal math, trace outputs.

Scenario Engine

Composes exit strategies and alternatives, compared on profit, cash, risk, timeline, and confidence.

Governance Core

Approves, blocks, or escalates actions. Policy-as-code, evidence thresholds, audit log.

Report Service

Builds outputs from approved results only: PDF, DOCX, CRM note, investor packet, API JSON.

Evaluation Harness

Tests engines against fixtures and expected outputs: formula tests, schema validation, regression cases.

Sections 7–8 · Data contracts and AXON events

The codex lives or dies by contracts

Prompts are flexible. Production systems are not. Seven core contracts are shared by every product; eleven real-estate contracts extend them. Every fact references evidence or is explicitly marked as an assumption.

Real-estate domain contracts:
dealpropertyparcel comparableadjustment-ledgerrepair-scope market-snapshotunderwriting-resultoffer-structure risk-assessmentdisposition-plan

An evidence object

{
  "evidence_id": "ev_01JREAL_0001",
  "domain": "real_estate",
  "source_type": "county_assessor",
  "source_name": "St. Joseph County Assessor",
  "source_url": "https://example.gov/property/12345",
  "retrieved_at": "2026-07-15T15:10:00-04:00",
  "raw_storage_uri": "s3://neuruh-evidence/raw/ev_01JREAL_0001.json",
  "facts": [
    { "field": "bedrooms", "value": 2, "confidence": 0.92 },
    { "field": "bathrooms", "value": 1, "confidence": 0.91 },
    { "field": "living_area_sf", "value": 984, "confidence": 0.88 }
  ],
  "conflicts": [],
  "license_policy": "internal_use_only"
}

An AXON event envelope

{
  "event_id": "evt_01JREAL_0001",
  "event_type": "realestate.underwriting.completed",
  "version": "1.0.0",
  "occurred_at": "2026-07-15T15:18:00-04:00",
  "correlation_id": "deal_935_s_28th_st",
  "run_id": "run_01JREAL_0007",
  "actor": { "type": "organ", "id": "residential_arv:v2.0.0" },
  "payload_ref": "s3://neuruh-events/payloads/evt_01JREAL_0001.json",
  "idempotency_key": "deal_935_s_28th_st:residential_arv:v2.0.0"
}

Engines do not call each other directly outside a local execution context. Events keep the organism replayable, auditable, and upgradeable.

Event namespaces

NamespaceExample eventsOwner
core.identityidentity.created · identity.merged · identity.conflict_detectedIdentity Service
evidenceevidence.attached · evidence.normalized · evidence.conflict_detectedEvidence Service
realestate.dealreceived · normalized · staged · dispositioned · outcome_recordedAPG CRM / DealOS
realestate.compsearch_requested · candidate_found · candidate_rejected · set_approvedComparable Intelligence
realestate.marketsnapshot_requested · snapshot_generated · heat_score_updatedMarket Velocity
realestate.repairphotos_received · scope_generated · inspection_flaggedPhoto Repair Organ
realestate.underwritingrequested · completed · failed · supersededEngine Orchestrator
realestate.offerproposed · approved · rejected · sent · accepted · expiredOffer Architecture + Governance
world.emitreport_requested · report_emitted · crm_note_created · packet_sentWorld Emitter
governancereview_required · approved · blocked · escalated · policy_updatedGovernance Core

N-Cell position paper · Governed Adaptive Topology Protocol

N-Cell: one byte of local topology

At any moment the organism is a directed, attributed graph: G_t = (V, E_t, X_t, P_t), the registry, the active topology, the state, and the governance constraints. Each node carries an eight-bit routing mask over its Moore neighborhood. Toggle the neighbors of node v to build its route mask.

b7 NW b6 N b5 NE b4 W v NODE b3 E b2 SW b1 S b0 SE

R_v(t) = Σi=0..7 b_i(t) · 2i,  b_i ∈ {0,1}  →  256 local activation patterns

The eight bits may represent spatial directions, logical neighbor classes, event channels, or registered capability edges. The mapping must be declared in a versioned schema. A practical organism uses multiple masks rather than forcing all meaning into one byte, which is what the N-Cell/64 header does:

BYTE 0routeMask

Permitted local event routes or neighbor relationships.

BYTE 1organMask

Active specialist organs or capability families.

BYTE 2lifecycleMask

Workflow stage and completion state.

BYTE 3authorityMask

Observe, recommend, draft, stage, execute, emergency block.

BYTE 4memoryMask

Permitted working, episodic, semantic, procedural, prospective, founder, and outcome planes.

BYTE 5confidence

Quantized evidence or decision confidence, 0–255.

BYTE 6risk

Quantized escalation or hazard score, 0–255.

BYTE 7outputMask

Permitted artifacts, messages, APIs, physical commands, or World emission state.

Governance as graph reduction

E*_t = E_proposed(t) ∩ E_allowed(t) ∩ E_available(t)

Proposedwhat the planner wants to run
∩
Allowedwhat policy permits
∩
Availablewhat infrastructure can provide now
=
Executable topologyevery blocked edge is explicit, and each reduction writes a governance receipt
Topology receipts: ΔG_t = G_t ⊕ G_(t−1). XOR flags what changed; the receipt still carries the semantic evidence: why a route changed, which policy acted, which model proposed the change, and what outcome followed. N-Cell is a compact signature and observability layer on the existing organism, not a replacement architecture and not a substitute for the Vault.

Codex V2 · The modulated agentic system

Twelve runtime variables, one fixed identity

A conventional multi-agent system assigns fixed roles and fixed workflows. Neuruh modulates all twelve of these variables per opportunity, while identity, contracts, memory, evidence requirements, governance, and operating doctrine stay fixed.

Environment

Where the run executes and what infrastructure is actually available.

Opportunity type

The class of value being pursued: transition, land, business, asset, IP.

Agent role

Which registered agents compose the temporary topology.

Model

Which model serves which node, routed by task and cost.

Memory scope

Which Vault planes a node may read, and nothing beyond them.

Tool access

Which tools and adapters are bound to the run.

Collaboration topology

How nodes communicate: the N-Cell graph for this run.

Authority

Observe → recommend → draft → stage → execute → emergency block.

Risk threshold

How much hazard a run may carry before it must escalate.

Economics

Budget, cost envelope, and expected value of the opportunity.

Output contract

Which artifacts the run may emit, and to whom.

Evaluation standard

The harness and thresholds the result is scored against.

The core systems problem: given an objective, an environment, available capabilities, and policy constraints, select and execute the smallest sufficient topology of agents, tools, models, memories, deterministic organs, and human approvals that maximizes expected outcome quality while minimizing cost, latency, risk, and unsupported claims. Fixed orchestration fails because the same team is overbuilt for simple work, underbuilt for complex work, and cannot respond cleanly to missing evidence, tool failure, or changed risk.

Codex V3 · Full Notion audit

Two spines, seven lanes, one deployment chain

The audit exposed the backbone the earlier codex under-described: a revenue spine that turns signals into outcomes, a knowledge spine that turns canon and evidence into repeatable intelligence, the formal t0–t6 lanes, and the Galaxy-to-Product deployment model.

Revenue spine

Signals become outcomes, and outcomes reweight the system.

Signals
→
LandOS analysis
→
CRM workflow
→
Human action
→
Outcomes
→
Reweight

Knowledge spine

Canon becomes retrievable intelligence, and receipts flow back into canon.

Notion canon
→
Vault / Galaxy
→
RAGAnythingLLM / Qdrant
→
AXON / IAR
→
Receipts
→
Canon update

The t0–t6 lanes

LaneRoleStatus at the July 15, 2026 build session
t0  OperatorHuman fire: approvals and irreversible actionsOPERATOR-DEPENDENT
t1  EngineLandOS engine + ingestDOWN LOCALLY demo fixtures carried the visual
t2  VaultVault Galaxy substratePARTIAL git vault present; Galaxy Live UI down
t3  AEGISIAR decision and model-routing plane + governanceLIVE :8090
t4  EmitterWorld EmitterLIVE :4174
t5  CRMAPG Land CRM cockpit surfaceCOCKPIT
t6  CockpitNeuruh Cockpit + AXON execution planeDEGRADED AXON daemon healthy; gateway degraded with Bonsai offline

AEGIS/IAR is the decision plane. AXON is the execution plane. MOTHER is health and clock, built but not wired as a continuous supervisor. The Governance Core is an allow / escalate / block evaluator behind a gated boundary.

Galaxy to product

A World is a bounded projection of the organism, never a new source of truth. The organism stays broad internally; products stay narrow and outcome-specific externally. The market buys individual results while Neuruh compounds underneath them.

Section 10 · Immune system

Governance and the kill-switch

The immune system protects the organism from unsupported conclusions, legal risk, financial overreach, and operational chaos. Policy-driven and auditable: every policy area defines what is blocked automatically, what escalates to a human, and what proceeds with a visible warning.

Policy areaAutomatic blockEscalationAllowed with warning
Evidence sufficiency BlockARV report with fewer than three acceptable comps and no documented fallback. EscalateSparse data but a transparent confidence score. WarnThree comps present, confidence below target.
Seller-facing offers BlockOwnership unverified or seller authority unclear. EscalateConflicting seller notes or title flags. WarnVerified seller, approved offer, sufficient confidence.
Creative finance BlockNo loan details, arrears, or seller-consent path. EscalateDue-on-sale or legal structure unclear. WarnTerms modeled with an attorney-review flag.
Zoning and development BlockBuildability claim without zoning or source evidence. EscalateAmbiguous ordinance or conflicting GIS layers. WarnConceptual HBU marked non-binding.
Tax and legal BlockDirect legal or tax conclusion without professional review. EscalateEntity, lien, probate, or tax exposure involved. WarnEducational estimate with disclaimer and review path.
Data licensing BlockRestricted provider data used in a public report. EscalateReuse rights unclear. WarnInternal-only source properly marked.

The emitter rule

  • Reports can summarize evidence. They cannot create evidence.
  • Seller-facing outputs require governance approval, every time.
  • Any unsupported assumption is labeled as an assumption or excluded.

Anti-patterns, blocked by design

  • Standalone code recreating identity, evidence, memory, governance, or reporting.
  • LLM-written dollar values that bypass deterministic formulas.
  • Comp selection with no rejected-comp audit trail.
  • Zoning conclusions with no ordinance or GIS evidence.
  • Outcome learning that changes behavior without versioned policy approval.
  • A CRM treated as the source of truth for facts it merely displayed.

Risk categories under watch: title, lien, probate, ownership, authority, tax delinquency, foreclosure, and redemption; zoning, land-use, floodplain, wetland, environmental, utility, access, and easement; structural, roof, foundation, mechanical, occupancy, tenant, code, and permit; market liquidity, rental demand, investor appetite, buyer financeability, and disposition; data quality, conflicting facts, stale evidence, missing comps, and low-confidence model output.

Section 9 · Memory, learning, and the Vault

Six memory types, one governed learning loop

The Vault is not a flat chat log. It holds typed memory with permissions, decay rules, and an outcome calibration loop, so the organism develops continuity instead of amnesia.

Episodic

Specific runs and deal histories.

“The 935 S 28th St underwriting run and its final disposition.”

Semantic

Durable knowledge and market facts.

“River Park 2/1 homes lease within a supported band, given the data.”

Procedural

How to perform a workflow.

“The residential ARV comp-selection relaxation order.”

Prospective

Future follow-ups and pending actions.

“Re-check the inspection report when the seller uploads it.”

Priority State

Current active objectives.

“Build Real Estate Organ Pack V1 integration.”

User / Brand Preference

Stable preferences and templates.

“APG visual language, report formatting, acquisition thresholds.”

The outcome learning loop

1

Store the original prediction with its formulas, assumptions, evidence, and model version.

2

Record the actual outcome: purchase price, repair cost, resale or rent, DOM, profit, timeline.

3

Calculate the variance between predicted and actual values.

4

Tag the variance source: bad evidence, market shift, repair miss, comp mistake, or execution issue.

5

Calibrate only through governed rule updates. Never silent prompt drift.

N-Cell paper · Prior art and novelty boundaries

What is proven, what is synthesis, what is hypothesis

The paper's own discipline, applied to itself: the architecture is real enough to formalize and test, not yet proven enough to market as AGI. Microsoft, OpenAI, Anthropic, LangChain, Palantir, ServiceNow, Salesforce, and the dynamic-topology research line already cover many of the primitives. The defensible ground is the integration.

EstablishedSubstantial prior art exists. Language: “uses” or “implements,” never “invented.”
SynthesizedA new arrangement of established mechanisms. Language: “proposes an integrated architecture.”
ImplementedCode or deployment evidence exists, with exact repo, version, and test.
ValidatedA controlled benchmark supports the claim, with metrics and limitations reported.
ReplicatedAn independent party reproduces the result from a named package.
SpeculativeUnverified hypothesis or design intuition. Language: “requires testing.”
ClaimClassificationDefensibility
Eight-neighbor lattice and bitmask routingEstablished prior artDo not claim as invention.
Dynamic agent-team and communication topologyEstablished, rapidly advancingUse as foundation; differentiate implementation and objective function.
Agent operating systemEstablished research categoryDo not claim category ownership.
Governance intersection: proposed ∩ allowed ∩ availableSynthesisImplementation claim only if contracts, receipts, and runtime behavior are specific and novel.
Intent-to-topology compiler for opportunity objectsPotentially distinctive synthesisRequires a precise algorithm, baselines, and experiments.
Topology receipts tied to evidence, authority, cost, and outcomePotentially strong claim areaRequires schema, runtime implementation, and demonstrated learning value.
Galaxy-to-World emission from one organismPotential category claimMust be defined in machine-verifiable contracts, not narrative alone.
Cross-domain opportunity discovery + execution + outcome compoundingStrongest commercial synthesisThe moat depends on proprietary recipes, data rights, outcome history, and repeatability.
N-Cell/64 headerPotential protocol claimNovelty depends on exact field semantics, interoperability, and measured advantage.

Eight falsifiable hypotheses

H1

Task-adaptive topology improves success versus the best fixed topology, using identical models and tools.

H2

N-Cell state signatures reduce debugging and incident-resolution time without losing semantic traceability.

H3

Governance graph reduction lowers the unauthorized-action rate while preserving useful completion.

H4

Outcome-linked memory changes future topology selection in a direction that improves calibration.

H5

Sparse route activation reduces token and latency cost at equal or better quality than dense communication.

H6

One canonical substrate transfers across at least five Worlds with limited domain-specific orchestration code.

H7

Topology receipts improve reproducibility of stochastic agent runs.

H8

Opportunity-centered composition produces higher measurable economic value than task-centered automation alone.

“Neuruh is not presented as AGI. It is a governed adaptive agentic operating organism designed to compile objectives into temporary computational organizations, execute through evidence and authority constraints, and learn which organizational structures create measurable value.” The paper's clean language for investors and researchers. Current classification: infrastructure and system architecture. AGI: not demonstrated. ASI: no.

Sections 14–16 · Build plan and commercial shape

Phases, status ladder, and the money

The build is fixture-first with hard stop conditions per phase, and every asset carries a status on a strict ladder. Built, deployed, live, and revenue-active are different states, and conflating them is a named failure mode: registry inflation.

PhaseDeliverablesStop condition
0 · Contract ReconciliationInventory of existing modules, reuse / refactor / retire map, core and domain schemas.All schemas validate; no duplicate organism services introduced.
1 · Universal Intake + EvidenceOpportunity assembler, evidence ledger, conflict detection, source policy.A deal object builds from sparse and conflicting inputs.
2 · Core Real Estate OrgansComparable Intelligence, Market Velocity, Photo Repair, Residential ARV, Land Zoning.Fixtures pass deterministic formula and schema tests.
3 · Strategy OrgansRental / BRRRR, multifamily, development, creative finance, offer architecture.Scenarios compare profit, risk, capital, and time.
4 · Governance + RiskKill-switch policies, approval gates, data-sufficiency checks.Blocked and escalated actions behave predictably.
5 · APG Cockpit + EmittersDeal views, review screens, report templates, CRM notes.An operator can review and approve a deal from intake to report.
6 · Outcome IntelligenceOutcome capture, variance scoring, calibration workflow.Predicted vs. actual feeds the governed learning loop.

Six fixture types gate every phase: baseline clean, sparse data, conflict, unique asset, risk, and outcome. Acceptance requires schema validation, unit-tested formulas with known outputs, evidence or an explicit assumption label on every claimed fact, and a run receipt with versioned prompts, formulas, sources, inputs, warnings, and output IDs.

One intelligence, monetized eight ways

Internal acquisition edge

APG CRM + organ pack finds and structures deals faster. Customer: the Neuruh / APG operating team.

Investor reports

Paid underwriting packets and deal opinions. Customer: wholesalers, buyers, agents, lenders.

White-label CRM

APG Land CRM powered by Neuruh organs. Customer: land buyers, wholesalers, small brokerages.

API access

Underwriting, comp scoring, market heat, repair scope endpoints. Customer: proptech, CRMs, agencies, investors.

Data products

Market heat, parcel unlocks, owner signals, distressed lists. Customer: investors and acquisition teams.

Done-for-you services

Lead analysis, offer packages, seller scripts, investor packets. Customer: operators who need output, not software.

Vertical expansion

Resale, TaxShield, StudioGPT, Bookeit, defense, optimization. Customer: industry-specific buyers.

The tagline

“Neuruh finds hidden value, proves it, and builds the system that captures it.”