Recipe picker plus a worked scoring run on synthetic parcels. Simulation in your browser. Synthetic parcels only. Nothing here touches a live system, a live registry, or real owner data.
A recipe is a repeatable, machine-readable acquisition pattern that turns evidence and signals into a qualified opportunity. It is not prompt templates, and it is not DeedSonar-specific. The kernel is domain-neutral and place-agnostic by design, with real estate as its proving ground.
The pipeline is: county parcel data comes in, distress is scored across 50 LANDOS signals, the results run through a recipe, and the recipe produces ranked, qualified opportunities with a provenance receipt on each record. One documented production run, the LANDOS hunt job 6071b7ad on September 16, 2026, scored 153 leads and synced 153 to the CRM end to end.
Governance sits over the whole thing, enforced by recipe-engine: AI can generate is not AI can authorize is not AI can execute. Founder approval (G-1) is the authorization gate. A recipe proposes and scores. It never authorizes an offer on its own.
In this demo the flow is the same shape at small scale. Pick a recipe family. The demo reads three synthetic parcels, computes each signal in the recipe from the parcel attributes, applies the recipe weights, and ranks the parcels. Every number is visible, every weight is editable, and the receipt records the inputs, the weights, and the scores.
Seven families are named in the available sources: tax, probate, estate, heir, lien, code, absentee. The other 23 families are counted in the 30-family registry, but their names, signals, and evidence requirements are not documented in the sources available to this demo. They are listed below as undocumented rather than filled in with invented names. The R-number order for R1 to R7 follows the order in which the sources list the families.
Four hunt recipes are documented as active in the registry. A hunt is a named, running instance of a family, not a separate family. Click one to select the family it runs on. The plain reading of each name is given; detailed definitions beyond the name are not in the available sources.
| Hunt | Plain reading of the name | Family |
|---|---|---|
| Berrien90+ | Berrien County hunt for properties 90 or more days tax-delinquent. | R1 Tax |
| LIVE_PROVEN tax lien | Tax lien hunt, marked live and proven in the registry. | R1 Tax |
| FLOW_C multi-territory taxsale | Tax sale hunt run across multiple territories. | R1 Tax |
| FLOW_C probate/estate | Probate and estate hunt. | R2 Probate |
Three synthetic parcels. Invented addresses, invented attributes, no real owner names, no real parcel IDs. Edit any attribute or any weight and the scores update live. Press Run scoring to stamp a new receipt run. Press Reset to restore the original parcels, weights, and recipe.
Every signal in every documented family is derived from parcel attributes by one of these rules. Nothing is hidden and nothing is a black box.
| Signal | Rule (0 to 10) | Source attribute |
|---|---|---|
| Tax delinquency | min(10, tax years delinquent x 3) | Tax years delinquent |
| Tax owed burden | min(10, round(tax owed / assessed value x 100)) | Tax owed, assessed value |
| Probate open | 10 if a probate case is filed, else 0 | Probate case filed |
| Heirs found | min(10, heirs identified x 2) | Heirs identified |
| Heir contact | 10 if an heir contact is on file, else 0 | Heir contact on file |
| Lien count | min(10, lien count x 2) | Lien count |
| Lien burden | min(10, round(lien total / assessed value x 100)) | Lien total, assessed value |
| Code count | min(10, code violations) | Code violations |
| Code age | min(10, round(oldest violation age in months / 6)) | Oldest violation age |
| Absentee | 10 if the owner is out of state, else 0 | Owner out of state |
| Vacancy | 10 if vacant, else 0 | Vacant |
| Estate held | 10 if held by an estate, else 0 | Held by an estate |
| Deceased owner | 10 if the owner is deceased, else 0 | Owner deceased |
Every run produces a receipt: recipe, version, run id, timestamp, the weights used, and per-parcel signal values, weights, and scores. In the real kernel the receipt also carries provenance and the governance decision. This demo receipt carries the demo’s inputs only.
{}