From county parcel file to scored, ranked leads with provenance receipts, step by step.
Document
Buyer walkthrough, v0.1
Date
2026-11-03
Data
Synthetic only
Live data
None in this demo
Status
Demonstration, not a live system
Synthetic county data only. Every parcel, owner note, address, and score in this walkthrough is invented for demonstration. No live data is used, and no live-data claim is made.
Live-data claims are blocked: the Supabase lead pull has failed 18 straight nights, so nothing here is connected to a live county feed, a live lead list, or a live CRM. The one historical fact on this page is the 2026-09-16 hunt job 6071b7ad, in which 153 leads were scored and 153 were synced to CRM. That is history, not a promise of future volume.
1. What LANDOS is
The land signal engine. It turns county parcel records into scored, ranked opportunity leads, with a receipt for every lead.
Ingest: county parcel ingestion with source handling and provenance. Free-first acquisition: free public sources first, paid sources only behind controlled acquisition logic.
Engine: scoring, lead generation, opportunity ranking, provenance, and downstream synchronization to the CRM.
Signals: a 50-signal model. This demo names 12 of the 50 signals and scores on those 12. The other 38 are not disclosed in this demo.
Provenance: every scored lead carries a SHA-256 receipt naming its inputs, its detected signals, its score, and its rank.
Recipes: the live system surfaces leads through hunt recipes from Lead Recipe OS, which holds 30 canonical recipe families and 36 live registry rows. In this demo, recipe labels are demo-only placeholders, not live recipe attribution.
Geography: the production estate is Davidson County, North Carolina. The doctrine territory is Michiana: Berrien, St. Joseph (IN), LaPorte, and Elkhart counties. This demo uses a fictional county, Demo County, and no real geography.
How the score works in this demo
Each detected signal adds fixed points. The score is the sum of detected signal points, on a 0 to 100 scale. Category caps: Tax 25, Ownership 25, Land 25, Market 20, Condition 5. Bands: 70 and above is Priority, 50 to 69 is Qualified, below 50 is Watch. The scoring math is deterministic: the same signals always give the same score.
Signal
Category
Points
The 12 named signals are a subset of the documented 50-signal model. Weights in this demo are illustrative and fixed for demonstration. They are not the production weights.
2. The synthetic dataset
Three invented parcels in a fictional county. No real owner names, no real addresses, no real parcel IDs.
Parcel
Lot
Acres
Zoning
Assessed value (synthetic)
Owner
SYN-001 Synthetic
North Field
4.2
R-1
$18,000
Withheld in demo
SYN-002 Synthetic
Creek Lot
1.1
R-1
$12,000
Withheld in demo
SYN-003 Synthetic
Old Grove Tract
9.6
AG
$41,000
Withheld in demo
Do not treat these as real parcels. Demo County does not exist. Lot names are invented. Assessed values are invented. Owner information is withheld by design; no owner PII appears anywhere in this demo.
Run the full pipeline at once, or step through it one stage at a time. Five stages: ingest, signal detection, scoring, ranking, provenance receipts.
Stage 0 of 5: idle
Stage 1: Ingest
Synthetic county file loaded. Source: synthetic-demo-2026-11-03. Records: 3 parcels, Demo County. Live records: 0. Owner PII: none. The file is a stand-in for a county parcel pull; no live feed was contacted.
Stage 2: Signal detection
The 50-signal model ran over the 3 synthetic parcels. 12 named signals are shown. Detections: SYN-001 6 signals, SYN-002 6 signals, SYN-003 9 signals.
Stage 3: Scoring
Score equals the sum of detected signal points. The table below is computed live from the signal data, not typed in.
Stage 4: Ranking
Leads ranked by score, highest first. Bands: 70 and above Priority, 50 to 69 Qualified, below 50 Watch.
Stage 5: Provenance receipts
One SHA-256 receipt per parcel. A receipt names the dataset, the source, the detected signals, the points, the score, the band, and the rank. The hash covers the canonical receipt text. Downstream sync is shown as queued, not sent: this demo sends nothing anywhere.
Receipts are also available in the viewer below.
4. Provenance receipts
Select a parcel to inspect its receipt. Copy the receipt, or copy the full run as one JSON document.
Selected parcel:SYN-003 (highest score)
Nothing copied yet.
The receipt hash is a real SHA-256 of the canonical receipt text, computed in your browser. You can verify it: take the canonical text shown in the receipt under hash_input, hash it with any SHA-256 tool, and compare it to sha256.
5. What you would get as a buyer
In the live system, not in this demo. This section describes the deliverable, so you can judge it against the demo above.
Scored leads: parcels ranked by signal score, with the signals that produced each score shown, not hidden.
Provenance receipts: a SHA-256 receipt per lead naming inputs, signals, score, and rank, so a lead can be re-checked later.
Recipe attribution: which hunt recipe surfaced each lead, from the Lead Recipe OS registry.
Ranking with reasons: Priority, Qualified, and Watch bands, with the category subtotals behind each score.
Downstream sync: scored leads synchronized to the CRM, as in hunt job 6071b7ad, where 153 leads were scored and 153 were synced.
Freshness discipline: leads carry their pull date and source. A stale list is labelled stale. This demo is labelled synthetic, and the live list is currently blocked by the Supabase pull outage, which is stated here rather than hidden.
6. What this is not
Not live data. Nothing here comes from a county feed, a live lead pull, or a CRM. All parcels are synthetic.
Not a guarantee. A high synthetic score predicts nothing about any real parcel. Real scores require real signals, real sources, and measured outcomes.
Not an appraisal or a valuation. Assessed values in the demo are invented. LANDOS scores opportunity signals; it does not appraise property.
Not an offer. No price, no terms, and no offer are made here. Any offer requires the founder.
Not a promise of volume. The 153-lead hunt job is one historical run. It does not promise 153 leads per run, per county, or per month.
Not owner data. No owner names, addresses, or contact details appear in this demo, and none are for sale here.
7. Historical record
One documented LANDOS run, stated as history:
Hunt job 6071b7ad, 2026-09-16: 153 leads scored, 153 leads synchronized to CRM, end to end.
Current state: the Supabase lead pull has failed 18 straight nights. Live-data claims are blocked until the pull is reachable again. This demo exists so the pipeline can be inspected without pretending the live feed is working.