Real Estate Estate Inventory

Bottom line

The real-estate estate is not one app. It is a stacked system: DeedSonar at the customer-facing surface; LandOS as the land/property intelligence layer; REI-X as the analyst/product lineage; Recipe Engine / Lead Recipe OS for signal-to-opportunity logic; Territory Engine for geography; APG Land CRM as the historical operating implementation; and a substantial research, case, underwriting, and lead corpus around them.

Important boundary (source): This is a reconciled inventory, not a claim that every byte on every historical drive was directly mounted and rescanned in this runtime.

1. Executive Inventory

Current live database scale (source claims)

All values above are source claims from the 2026-09-22 snapshot. They were not re-verified against live Supabase in this demo build.

2. Canonical Real-Estate Product Family

3. Code, Repository and Deployment Locations

Documented local worktree locations

• /Users/jeramiehicks/neuruh-worktrees/crm-complete-product-v1/apg-land-crm
• /Users/jeramiehicks/neuruh-worktrees/deedsonar-hosted-safe-preview/apg-land-crm
• /Users/jeramiehicks/neuruh-worktrees/p1-activation/landos-engine
• /Users/jeramiehicks/neuruh-worktrees/p1-activation/neuruh-axon
• /Users/jeramiehicks/neuruh-worktrees/p1.1-durable/landos-engine
• /Users/jeramiehicks/neuruh-worktrees/red-domain-cutover/apg-land-crm
• /Users/jeramiehicks/neuruh-worktrees/t7-canonical-orchestrator/landos-engine
• /Users/jeramiehicks/neuruh-repos/AnchorPG/apg-land-crm
• /Users/jeramiehicks/neuruh-organism-build/territory-engine
• ~/Documents/landos-engine
• ~/neuruh-repos/NeuruhAI/landos-ingest
• ~/Documents/NEURUH_CANONICAL_LIBRARY/02_DEEDSONAR_REAL_ESTATE
• ~/Documents/NEURUH_ARCHIVE/02_DEEDSONAR_REAL_ESTATE

These paths come from indexed local-repo/worktree scans and handoff records. The current runtime did not have the historical NEURUH-HD volume mounted, so these are documented locations, not a fresh filesystem assertion.

4. Supabase / Live Data Locations

Project IDs and statuses are source claims from the 2026-09-22 snapshot.

5. Current Lead Geography

Current Deed Sonar Launch owner-lead geography is wider than the earlier June/July Michiana proof cohort. The largest current concentration is North Carolina, followed by LaPorte County, Indiana, then Berrien County, Michigan and additional Michigan/Indiana/North Carolina FIPS. This is a data-estate fact, not a statement of current buying intent.

Core territory doctrine found in the corpus

6. Property and Deal Case Corpus

The search found multiple layers of actual property research. These are not proof that the user personally owns the properties. They are documented acquisition, underwriting, pre-market or client-case targets in the corpus.

7. Full 30-Property HOME_HUNT Shortlist

The source file PREMARKET_HOME_SHORTLIST_20260824.json declares a top-level count of 30 candidates. The 30 addresses below are the top-level candidate list, not every nested address field present elsewhere in the same file.

8. Recipe / Signal / Lead Intelligence

Current active hunts

Canonical recipe catalog

The source lists R1-R7, R9-R29 (R8 is absent from the source listing) plus six unnumbered research variants/aliases: Estate Sale Life Event Research, Fractional Family Ownership, Heir Property Acquisition Research, Long Term Absentee Potential Equity, Published Tax Distress, Stalled Tax Foreclosure Heirship, Tax Foreclosure Curative, Tax Foreclosure Fractional Title. Counted as printed: 28 numbered recipes + 8 unnumbered entries = 36 rows, matching the live registry row count.

9. Canonical Real-Estate File / Library Locations

10. Notable Finished / Historical Real-Estate Artifacts

11. Historical Drive / Physical Storage Evidence

The indexed estate contains a historical scan of the external volume NEURUH-HD. The scan documented the volume as /Volumes/NEURUH-HD, 466 GiB total, and reported no canonical masters and no D0_MECKLENBURG tree at that scan point. The current runtime does not have that volume mounted, so this section is historical evidence only.

12. What This Inventory Says About Physical Property Ownership

No definitive personal-property ownership ledger surfaced. The connected evidence is overwhelmingly an acquisition/intelligence corpus: property candidates, parcel records, research targets, client cases, underwriting packages, and CRM leads. Individual addresses in the report are documented research/case assets, not proof of title ownership by the user.

There are documented transactions/outcomes in the Deed Sonar data model, but the current table census does not by itself establish which properties are personally owned, jointly owned, under contract, assigned, or merely researched. That distinction needs a dedicated ownership ledger or deed/title source if the goal is an inventory of personally controlled real estate.

13. Gaps, Duplicates and Things to Finish

14. Source Trail / Systems Searched

Reconciliation rule used in this report (source): current connector data outranks historical snapshots; canonical product naming outranks legacy naming; built/implemented is not treated as live/healthy; research candidates are not treated as owned property; and FIPS-level long-tail rows are not promoted to named county claims unless the county identity is already explicit in the available evidence.

Interactive Tools

The tables above are the source transcription. The tools below let you explore that transcribed data. Sample data is synthetic and labeled as such; it is not source data.

Sample data loaders (synthetic)

Load sample A: 3 Michiana leads Load sample B: 3 NC leads Load sample C: 2 probate leads Clear samples

No sample loaded.

Completeness meter: inventory record check

Check a record against the fields this inventory expects. Missing fields are listed below the meter.

Completeness: 0% (0 of 5 fields).

Missing fields: address, APN, county, FIPS, score.

Share link (URL hash)

Save the current shortlist filter and sample selection into a shareable link. The state is encoded in the URL hash as base64 JSON; nothing is sent to a server.

Try-it walkthrough

How it works

This page is a faithful transcription of the 2026-09-22 inventory PDF into one searchable HTML document. The shortlist and recipe tables are rendered from data embedded in this file, so the filters run entirely in your browser. The completeness meter scores a record against five fields the inventory itself uses (address, APN, county, FIPS, score). The share link encodes only your current filter and sample choice in the URL hash.

What this is not

• Not a live connection to Supabase, GitHub, or Notion. All figures are source claims from 22 September 2026.
• Not proof of ownership. Section 12 states no personal-property ownership ledger surfaced; addresses here are research/case assets.
• Not current data. The live counts (33,250 owner-leads, 573,166 parcel geometries) are a snapshot, not a live census.
• Not an appraisal, valuation, or title opinion. No prices, comps, or valuations are stated anywhere on this page.

Honest gaps and limits

• NEURUH-HD was not mounted in the source runtime; no fresh recrawl was possible.
• Long-tail FIPS rows (1,600+ MI, 100+ NC) are approximate ranges; exact FIPS are in the source appendix, not transcribed here.
• R8 is absent from the source recipe listing; R8 is not invented here.
• St. Joseph County row: 162 scored + 94 non-seed = 256, but the source total is 244. Printed as stated.
• Layout was not eyeballed in a real browser; DOM checks only.

Sibling modules: Residential Underwriting Engine · E1 Land and Zoning Unlock · Real Estate Agent hub