Master Convergence Handoff

Bottom line

The work is further along than older handoffs suggested

Core DeedSonar closure PR #140 is merged and production is serving 3a0691b. Governance hardening is merged at d4c73af and neuruh-sops now pins it at d4c73af. The remaining work is not another architecture rebuild. It is proof, runtime promotion, local-worktree custody, continuous execution closure, commercial and public-surface completion, and canon reconciliation.

Source claim: all state in this demo is as recorded in the 2026-09-24 handoff. Nothing here re-verifies live GitHub, Vercel, or Supabase state.

How to read this document

0Labels, used literally

Use the labels literally. DONE means implementation or evidence is complete at the stated layer. LIVE means a production or supervised runtime proof exists. HELD means intentionally paused. OPEN means not yet completed. BLOCKED means an explicit dependency prevents closure. HISTORICAL means the statement describes an earlier state and must not be mistaken for current truth.

DONE LIVE MERGED OPEN BLOCKED HELD HISTORICAL

Truth precedence in the Neuruh Topology Notebook (source claim): current provider / runtime, then exact Git / deploy / DB, then sealed independent receipt / court, then Vault / current live ops, then current mission checkpoint, then historical canon, then legacy artifacts, then model memory.

Section 1

1Executive state map

The system is in final convergence, not initial construction. The dominant pattern is: code has been merged, some production changes are live, but several independent proofs have not yet been rerun after the latest merges. Do not treat merged code as equivalent to live organism behavior.

Section 2

2Truth precedence and stale-handoff corrections

• DONE PR #134 is not open. It merged during the 2026-09-22 DeedSonar / LRO convergence sequence and is part of the current DeedSonar history.
• DONE Governance PR #5 is merged at d4c73af. The older statement that only 456db4fc was on main is superseded.
• DONE neuruh-sops PR #38 is merged at 31e740892, and PR #39 is merged at 218ea590. The SOPS pin now names d4c73af.
• DONE DeedSonar PR #140 is merged at 3a0691b and Vercel production is READY on that exact SHA.
• HISTORICAL The old Round 10 court result against 28e04e6 is historical. It failed six checks. It is not a verdict against 3a0691b.
• OPEN T02 live runtime is not automatically closed by repo merges. The local supervised process must be restarted and fingerprinted against the new pin.
• BLOCKED Notion was not intentionally skipped. The attempted canonical update returned a workspace free-block exhaustion error.

Section 3

3Architecture and organism convergence

The business chain and control chain remain separate but convergent. The property / lead chain is the economic workload; the organism control chain is the authority and proof system that governs execution.

Current final organism receipt (source claim). Historical T5 final receipt: T5_FINAL_ORGANISM_CONVERGENCE_RECEIPT_20260913.md, section A at approximately 21:40Z, recorded: ORGANISM_CONVERGED_AS_TOPOLOGY / AUTONOMOUS_EXECUTION_NOT_PROVEN / BLOCKED_HUMAN. Its exact merged heads at that time were workers c013c76f, sentinel-court 84c7e130, sops 3433662c, live-integration 9a17a4af, governance 79bd6e89. Governance has since advanced, so that T5 governance SHA is historical.

Major topology seam still material

• The live execution chain was not proven through the full receipt, Sentinel, ingest, custody, promotion sequence.
• Mission-fabric tick still lacked a proven no-op budget / three-cycle stall behavior in the final convergence notes.
• The historical O3 seam identified a git_custodian registration ceiling at R3 with git_inspect / read / merge classes, source SHA e36d1bf, and expired T02 ratification at that time. Current live registration must be rechecked rather than assumed fixed.
• The final organism needed a bounded founder-gated path, not a bypass. Founder gates remained explicit and intentional.

Sections 4 to 6

4DeedSonar: current production spine

DeedSonar is the APG customer-facing product and the principal production proof surface for the land / property intelligence system. The canonical Supabase production project is efxo: Deed Sonar Launch, in us-east-2, ACTIVE_HEALTHY, PostgreSQL 17.6.1.166. Source claim.

Round 10 production failures that triggered PR #140

The prior release court ran against 28e04e631a34763cf9ee4bc4afa8c8ef72255b97 and returned six failures. None were waived as Rule 1 / Rule 2 contamination.

• G3 DNC chips: the UI showed an em dash while SQL had NULL=22,584 in the estate census. The failure was a deterministic first-paint data race, not a mere latency issue.
• G5 map camera: map settled at the wrong camera over Ohio instead of the intended North Carolina estate view. The style-source change was implicated, but the failure itself was a real position error.
• O6 Wake County place report: report loaded, but ranked homes were 0. The court had not yet established whether core had no rows or the DeedSonar report dropped them.
• The machine also showed elevated swap and Chrome CPU, but those conditions did not explain away the three named deterministic seams.

PR #140 changes

5 DeedSonar history that matters

Standing DeedSonar founder boundary. No paid enrichment, skip-trace, or data purchase without explicit founder approval. Tracerfy is off. Free paths only unless the founder explicitly changes the rule. Do not treat the 938 / 941 phone-bearing RESEARCH candidates as outreach-ready. They were parked pending founder decision and did not meet the qualified threshold. Do not silently delete the two test-looking production users. Prior work established that they are in the real tenant and were inherited from the old database lineage.

6 DeedSonar data / estate state snapshots

Several row counts exist at different timestamps. They must not be collapsed into a single number.

Do not re-use dated counts as sales proof without refreshing them. The sales playbook itself explicitly says its numbers are dated snapshots and should be refreshed before pitching.

Sections 7 to 8

7Lead Recipe OS: current canonical core

Lead Recipe OS is no longer place-specific. The canonical main in the last verified convergence was 60e766d63eb843a89ef05e1108da0c831376c234. Source claim.

Mode 2 verified ranking snapshot

Mode 1 verified examples

• Wake: 3,381 opportunities, 3,377 MATCH, 356 recipes evaluated.
• Berrien: 129 candidates all UNKNOWN in the verified run.
• Delaware IN: 76 candidates all UNKNOWN in the verified run.
• New Carlisle: 678 MATCH versus the older baseline of 87.
• 617 New Carlisle entity-watch matches existed and required a 10-row manual sample before any outreach use.

LRO technical debts that remain

• The evaluations table grows rapidly. A prior storage event showed roughly 12 GB run storage reduced to about 517 MB after compaction, but the evaluations table still grows around 1 GB per approximately 3,000-candidate run. Trim policy is required before another heavy Mode 1 run.
• Estate death-signal fetchers were not completed. Priority sources were public notices / probate, with LaPorte, St. Joseph and Berrien first.
• The New Carlisle 617 entity-watch set needs a 10-row manual check before outreach use.
• The direct-to-main SOPS re-pin at cb67eaa is a process deviation and must be recorded in canon. Future pin changes should go through PR only.

8 LANDOS / Recipe Engine / estate intelligence

LandOS and Recipe Engine form the supply-side intelligence chain feeding DeedSonar. The important state is not that every possible signal exists. It is that the canonical pieces are already wired enough to produce live candidate and place outputs, while some advanced death / estate signals remain unfinished.

• LandOS schema parity and ingestion work had been reconciled against the efxo production shape in the earlier migration sequence.
• Recipe Engine acceptance had a canonical main and receipt path; do not create a parallel recipe engine.
• The user intent remains property intelligence with bounded recipes, not a generic CRM rebuild.
• Local land-lead concept retained in the canonical system: a recipe-driven search for high-value river-corridor opportunities around the St. Joseph River / Michiana region, including older-owner signals, underused narrow river-adjacent parcels, and potential compliant small overnight-stay concepts. This is a recipe / signal / lead-generation use case under the canonical system, not a separate product.

Sections 9 to 12

9Governance / T02: code is now fixed, runtime proof is the gap

This is the largest example of a stale handoff becoming misleading. The governance code defect was fixed and merged, and SOPS was repinned. What remains is proving the live checkout is actually serving the new code.

Promotion-minting fix details. Founder secret must arrive from a 0600 secret file. GOVERNANCE_FOUNDER_SECRET is refused rather than trusted. --config is mandatory. Validation occurs against the actual unmodified config. Tests cover environment refusal, missing secret / config, permissions, TTL, scope binding, replay, and executor binding.

T02 live runtime closure checklist

10 SOPS / supervision / live integration

The supervision layer had a recurring failure mode in prior work: repo state, pin state, and live process state could diverge. This handoff must therefore treat pin, checkout, process, and receipt as separate predicates.

• Prior T16 runtime proof had every organ pinned to HEAD = origin/main with health OK, but later drift in SOPS caused fr-dispatch refusal and nsv-invoke exit 78. This is the exact class of failure that must be closed with a current live proof, not a repo-only assertion.
• A dirty SOPS checkout previously caused dispatch refusal with WORKERS_PROVENANCE_OR_BRIDGE_INVALID / SOPS checkout dirty.
• The final convergence instructions explicitly reject the states merged-but-not-running, running-but-behind-main, stale supervision pin, stale local branch, old checkout accidentally serving traffic, unexplained restart loops, and missing failure receipts.

Current required verification: SOPS working tree clean. Current pin file names the intended SHAs. Supervised processes load exactly those SHAs. Health endpoints and supervision ledger agree. One bounded mission can dispatch without silently using a stale checkout.

11 Sentinel court / workers / safety proof

The worker and sentinel repos were part of the earlier organism convergence and the current GitHub open-PR sweep shows no open PRs in the core worker / sentinel repos. That is a custody fact, not an autonomous-execution proof.

12 CRUCIBLE: safety fix complete, benchmark negative result preserved

CRUCIBLE had a serious fail-open defect: IAR timeouts previously fell back to heuristic verdicts and could publish PASS / FLAG without the judge answering. That defect was fixed and merged at 034f0f2. The safe behavior is now fail-closed.

Interpretation. This is a successful safety outcome and an unsuccessful judge-calibration outcome. The important proof is that the gate refused to publish an unsupported benchmark. The next step is a founder decision about a new judge or a different evaluation path. Do not silently convert the 48-row negative calibration into a green benchmark.

Sections 13 to 18

13PRBench

LIVE bench.neuruh.com was live in the prior handoff. OPEN Pinned API-model runs were still pending in the last recorded state. This is lower priority than closing the production DeedSonar court and T02 runtime. It remains part of the research and evaluation layer, not the immediate revenue path.

14 Neuruh.com public surface

Neuruh.com is intended to be the public witness of the canonical organism. A current GitHub issue remains open in NeuruhAI/neuruh-web (#10): public-surface convergence and 10x front door. The issue is detailed enough to function as a backlog / spec and explicitly forbids creating a parallel backend, CRM, checkout, or truth system.

Issue #10 key workstreams. Re-court public truth from canonical truth infrastructure and explicitly distinguish ATTESTED, VERIFIED SNAPSHOT, and HISTORICAL. Home hierarchy around AI THAT CAN INVESTIGATE. DECIDE. ACT. PROVE. Create /solve as a composition over existing capabilities, not a new backend. Turn /proof into a first-party public proof surface with proof ID, evidence class, verified time, public safety and wording ceiling. Commercial completeness: O01 Data Rescue $299, O02 Opportunity Dossier $499, O05 Workflow Sprint $1,250, and quoted Property Scan / Lead Rescue where canonical. Preserve attribution fields: world, offer, source, campaign, landing, referrer, first_touch, last_touch. Repair discovery, FAQ, structured data, sitemap, robots, canonicals, and Search Console only where credentials / config actually exist. Add public negative controls so stale truth, invented live connectivity, invented pricing, or candidate products cannot leak into the public surface.

This public work is a separate release track from DeedSonar. It should not block the property product from being sold privately, but it blocks the broader claim that the whole Neuruh organism is publicly witnessed as live. Note: the issue #10 prices ($299 / $499 / $1,250) differ from the sales playbook prices in Section 15. That conflict is recorded in the gaps section, not reconciled here.

15 Commercial layer: sales playbook

The sales playbook pasted on 2026-09-23 provides a coherent commercial operating procedure around the existing intelligence system. It is not a reason to rebuild the product.

Commercial cleanup items. The source material had two $499 names: Opportunity Intelligence Dossier and Property Intelligence Dossier. Pick one canonical public name or clearly distinguish them by scope. The $100 scan appeared only on re.neuruh.com and not the main offers surface. The canonical commercial entry point should be explicit. Do not pitch sealed / candidate products such as FindSellProfit, Bookeit, CurbClaim, ProofOS, Liquidity Engine, or Venture Factory as current production offers. Dated proof numbers must be refreshed before sales use. Revenue-to-date was stated as $0 in the 2026-09-23 playbook. Preserve this as the source-derived state until a newer financial receipt exists.

16 Instinct / Muse: operator interface

The Instinct capability document describes a human-in-the-loop operator interface via iMessage. Its critical governance property is approval at the external side effect boundary: Instinct can research, draft and prepare, but the user approves anything sent, booked, bought or shared externally.

This is conceptually aligned with the founder gate in the organism: bounded execution with a receipt and an explicit human authorization boundary.

17 Outbound email / Resend / Gmail Send-as

The prior handoff delegated the re.neuruh.com sales email path to Muse. The technical plan was concrete but the result was pending in the latest pasted handoff.

18 Notion / canonical documentation

The established canon is the Neuruh Topology Notebook and Mission Registry. The rule is update before create. Do not create another master page merely because the existing workspace is full.

Relevant existing chapters. Chapter 10, Current Convergence Frontier: definition of done is implementation, test, independent court, remote custody, CI, authorized promotion, runtime proof, outcome receipt. Chapter 47, Merge-First Convergence: closure of known seams comes before new architecture. Chapter 28, Public Proof / Neuruh.com / discovery / proofstream / marketplace distribution. Mission Registry: bounded agents, states, priorities, roles, repo, done predicate, next action, evidence root and receipt destination.

BLOCKED Canonical page update was attempted using the new state, but Notion reported that the workspace had used all free blocks. No duplicate master was created.

Sections 19 to 21

19Local Mac / worktree / disk state

The local Mac remains a real operational dependency because many of the release courts, supervised runtimes and receipts execute there. This environment has repeatedly contaminated benchmarks and courts through Chrome, swap pressure, dead model servers, stale launchd jobs, and competing worktrees.

Local state traps that must be checked before declaring live. A branch can be merged on GitHub while a local worktree still serves an older SHA. A supervised process can be pinned to an old SOPS checkout even after main advances. A dead MLX / local model process can hold swap while appearing idle in an instantaneous CPU sample. Chrome can remain alive after the UI says it is quit, contaminating court timing and memory. launchd can have duplicate jobs fighting over the same port. A historical example was com.neuruh.landos-engine conflicting with com.neuruh.landos-engine.api on port 8410. Do not use destructive worktree cleanup as a shortcut. The explicit final-convergence instructions prohibited resetting or cleaning worktrees without evidence.

20 Security / data / provenance boundaries

• A standing DeedSonar rule prohibits paid enrichment, skip-trace and data purchase without founder approval.
• The previous voter-file cleanup moved 5 county ZIPs to ~/.neuruh/private/ncsbe_20260922/ and removed the 1.26 GB unzipped text from NEURUH-HD. The drive search found 0 voter files in the checked drive locations.
• Database passwords and LANDOS_SECRET appearing in transcripts were identified as requiring rotation independent of the drive scan.
• The direct-to-main LRO re-pin at cb67eaa must remain explicitly recorded as a deviation.
• Do not publish internal recipes, weights, thresholds, source routing, NBE implementation, full internal schemas, identity / contact mechanics, prompts, model topology, governance implementation, DB schema, webhooks, internal APIs or secrets.

21 Open issues / external backlog found in the current GitHub sweep

The current GitHub PR sweep across the core repositories returned 0 open PRs. The broader organization sweep did identify unrelated open work. It is listed here so it is not silently forgotten, but these items are not blockers for the DeedSonar production court.

Section 22 | Trackable checklist

22Master pending list, reordered by what actually makes the organism live

Tick items as they are proven, not as they are started. The completeness meter below counts these 13 items plus the 7 T02 items and the 6 required handoff fields. Use the sample loaders or the share link to restore a saved state.

Required handoff fields

Reset checklist and fields

Convergence record explorer

Explore the convergence record

Filter the full record by status, or search by text. Every row is a source claim from the 2026-09-24 handoff.

Section explorer

All 29 sections plus appendices. Open any section to see its one-line record.

SHA explorer

Historical SHAs and why they should not be mixed (Section 26).

Working calculators | source-defined math only

Calculators

Try-it walkthrough

TTry it: close one P0 seam in six steps

1. Load sample 1 below (Round 10 court rerun, pass). It fills the DeedSonar SHA, the verdict, and checks the P0 court item.
2. Run calculator A with the defaults (20,734 total, 306 qualified). Confirm the qualified rate reads 1.48%.
3. Run calculator B with the defaults (TP 21, FP 24, FN 0, TN 0). Confirm accuracy reads 46.67% and the stop rule fires.
4. Open the explorer and filter by BLOCKED. Confirm Notion canon is the only BLOCKED record in the main sweep.
5. Load sample 2 (T02 governance proof). Confirm the T02 checklist items check off and the meter rises.
6. Copy the share link. Open it in a new tab and confirm your checks and fields restore from the hash.

Sample loaders

Each loader fills the fields, checks the matching items, and runs the matching calculator. Nothing here writes to any live system.

Sample 1: Round 10 court rerun (pass) Sample 2: T02 governance proof Sample 3: CRUCIBLE negative calibration

Section 23

23Exact definition of "live"

LIVE IS NOT "MERGED". A component is live only when the code is in remote custody, the intended runtime serves that exact code, the external interface responds, the health / ledger evidence matches, and an independent proof or court verifies the behavior.

24 Exact handoff for Claude / Cursor terminal on the Mac

The following is a bounded execution checklist distilled from the prior instructions. It is deliberately not a new audit or rebuild.

25 Evidence / receipt inventory

27 Final state: what is actually left

THE WORK IS CONVERGING. The remaining work is no longer "build the organism." It is "prove the exact merged organism is the organism actually running, then close the continuity loop."

• DeedSonar: one independent current court against 3a0691b.
• Governance: one live-process proof against d4c73af plus the renewal dry-run.
• Supervision: one bounded proof that pin, checkout, process and health all agree.
• Organism: one current end-to-end receipt / Sentinel / custody / promotion proof.
• LRO: storage discipline, death signals, and 10-row New Carlisle sample before outreach.
• Commercial: resolve offer naming, refresh proof, finish outbound email proof.
• Public: execute the existing Neuruh.com issue without creating parallel infrastructure.
• Canon: update the existing Notion chapters once workspace quota allows it.
• Local: clean enough Mac capacity and worktree custody to stop environment contamination from masquerading as product failure.

28 Master go / no-go conditions

29 Closing handoff

The correct next operator should not restart the archaeology, redesign the topology, or create a new system. The highest-value behavior is to take this handoff as a state map, verify each P0 predicate at the live boundary, and write receipts as the organism crosses each seam.

The most important conceptual correction from the prior chats is this: merged is not live, deployed is not proven, a passing unit suite is not an end-to-end receipt, and a historical handoff is not current truth. The current system is substantially converged. What remains is to turn convergence into continuously evidenced execution.

Appendix A. Source basis and limitations

This PDF was assembled from the accessible conversation history and retrieved source artifacts available in the current session, plus live connector checks against GitHub, Vercel, and the canonical DeedSonar Supabase project. It is not a byte-for-byte export of every historical chat message. Where a statement could not be freshly reverified, it is labeled historical, pending, or dependent on the prior receipt. Primary source artifacts relied upon include: CURRENT_STATE_20260921.md and related T16 handoff material; T16_DECISIONS_20260922_RECEIPT.md and its Round 7-10 court history; T5 final organism convergence receipt and T16 runtime convergence material; DONE-20260922-place-agnostic.md for Lead Recipe OS; CRUCIBLE overnight receipt and prior fail-open defect record; 2026-09-23 sales playbook and Instinct capability text; current GitHub PR states for DeedSonar #140, autonomous-governance-core #5, neuruh-sops #38 / #39, and the current open-PR sweep across the core repositories; current Vercel deployment dpl_HrfW4CjXXr5ZxZZuxR9Yg3DX5DmY; current Supabase project efxowqudmsfqjmbeidjc and migration ledger through 20260924150000.

Appendix B. Current core repository open-PR sweep

NeuruhAI/deedsonar 0 (current main includes #140). NeuruhAI/lead-recipe-os 0 (60e766d convergence reference). NeuruhAI/neuruh-sops 0 (current governance pin d4c73af). NeuruhAI/recipe-engine 0. NeuruhAI/landos-engine 0. NeuruhAI/autonomous-governance-core 0 (#5 merged). NeuruhAI/crucible 0 (fail-closed merged at 034f0f2). NeuruhAI/prbench 0 (pinned runs still pending). NeuruhAI/neuruh-sentinel-court 0. NeuruhAI/neuruh-workers 0. NeuruhAI/neuruh-vault 0. NeuruhAI/neuruh-live-integration 0.

Appendix C. Current provider facts verified for this handoff

• Vercel: production deployment dpl_HrfW4CjXXr5ZxZZuxR9Yg3DX5DmY is READY, target production, Git ref main, Git SHA 3a0691b97..., canonical aliases intact, and the selected runtime-error window reported no runtime errors.
• Supabase: Deed Sonar Launch project efxo is ACTIVE_HEALTHY in us-east-2 on PostgreSQL 17.6.1.166. Migration head is 20260924150000 estate_page_dnc_census_v1.
• GitHub: core repository open-PR sweep returned zero open PRs for the current core repo set. Separate non-core open work remains in public web, cockpit continuity, and OSS scaffold repositories.

About this demo

How it works / What this is not

Honest gaps

Honest gaps on this page

• Stale by design. Source state is 2026-09-24. This demo was built 2026-11-04. No live state was re-checked, so every LIVE / MERGED label is a 2026-09-24 source claim, not a 2026-11-04 fact.
• Deadline passed. The T02 ratification deadline (2026-09-29 10:52 AM EDT) is past. The demo does not know whether renewal happened.
• Price conflict preserved, not resolved. Issue #10 prices (O01 $299, O02 $499, O05 $1,250) match the playbook in Section 15, but the playbook also lists a $100 scan and scoped audit that issue #10 does not price the same way, and the two $499 dossier names remain unresolved in the source.
• Phone-count ambiguity. The source gives both 938 and 941 phone-bearing RESEARCH candidates in different places. Both figures are shown as written; neither is reconciled.
• Mode 2 custody rows. The source table lists custody rows (11,148) only for Wake NC. The other nine places have no custody-row figure in the source, so the cells are blank, not zero.
• SOPS PR #39 SHA. The source prints the #39 SHA across a line break ("218ea590fc1756c47046c1a753a4aca5e9fb6 517"). It is reproduced as printed; the trailing fragment is not corrected.
• Layout not eyeballed. Layout was not checked in a real browser. Controls were tested in jsdom only.
• No live data. Calculators use source numbers as defaults. They compute, they do not fetch.

Sibling sites: Neuruh Hub. Related builds in the hub cover DeedSonar, Lead Recipe OS, LANDOS, CRUCIBLE, and the public proof surface. This demo links only to the hub; it does not claim any sibling state.