00What this is, and what it is not
This page is a browser simulation and orchestrator demo. It classifies a mission, proposes a run plan across the 18 live module sites, and simulates the run step by step with a reasoning trace, tool-call cards, and hash-chained receipts. Nothing here touches live data, county records, or any real deal.
offer_authorized: false. No offer is made without Jeramie. Sample missions use synthetic data, labeled synthetic. No prices, comps, or source claims are invented here; any number on this page is either typed in by you or labeled synthetic.What this is not: not a CRM, not a data source, not a valuation, not an appraisal, not legal or title advice, and not a live agent fleet. The 18 modules are separate live sites; this hub deep-links to each one and hands the mission off to it.
Try-it walkthrough
Step 1 of 5: Enter an address or parcel in Section 01, pick a deal type and a goal.
01Mission intake
Describe the mission. Fields marked required feed the completeness meter and the router. Nothing leaves the browser.
Completeness
0 of 3 required fields complete.
02Agent router
The router classifies the mission and proposes a run plan. Lead gen is the first lane in every run plan: Lead Gen, then Inventory / Audit, then Underwriting engines, then the DeedSonar forensic dossier. The plan is a proposal; the run simulator executes it.
No mission routed yet. Fill in Section 01 and press "Route this mission", or load a sample mission below.
Sample missions (all synthetic data)
Three end-to-end samples. Each loads the intake and proposes its run plan. Sample 1 starts at lead gen.
03Run simulator
Executes the routed plan step by step in-page. Each step writes to the live run log, shows a reasoning trace and a tool-call card, and issues a hash-chained receipt. SHA-256 via Web Crypto when available; FNV-1a fallback otherwise (jsdom and older contexts use the fallback, which this page states plainly). Deep-link each step to its module site.
Live run log
Agent reasoning trace
No trace yet.
Tool-call cards and receipts
No tool calls yet. Receipts chain: each receipt hash includes the previous receipt hash.
Verdict
No verdict yet.
04Module registry: all 18 modules
Every module is a separate live site. Descriptions below are taken from each module's own title and headings. Click through to run the module itself; this hub only orchestrates the handoff.
| # | Module | What it does | Link |
|---|
05How it works / what this is not
How it works
- Intake captures address or parcel, deal type, and goal. Nothing leaves the browser.
- The router classifies the deal type, maps it to the matching underwriting engines, and orders the lanes: Lead Gen first, then Inventory / Audit, then Underwriting, then the DeedSonar forensic dossier.
- The run simulator executes the plan one step at a time. Each step logs, traces its reasoning, records a tool call, and issues a hash-chained receipt. A step cannot start until the previous receipt exists.
- Each step deep-links to its module site, where the real work for that lane happens.
- The run ends in a verdict. The verdict is HOLD with offer_authorized false unless Jeramie authorizes an offer. This console cannot authorize one.
What this is not
- Not live data. No county pull, no live Supabase read, no live lead list.
- Not a valuation, appraisal, comp, or price opinion. Numbers are either typed in by you or labeled synthetic.
- Not legal, title, or probate advice. Distressed-title missions stop at a counsel gate.
- Not an offer engine. No offer is generated, sent, or authorized here.
- Not the modules. The 18 module sites are separate; if a module link is down, this hub still simulates the handoff but says so in the log.
Honest gaps and limits
- Browser simulation only. The run is scripted in-page; no agent actually calls the module sites, and no data passes between them.
- Receipt hashing uses SHA-256 via Web Crypto in a real browser. In jsdom and other contexts without crypto.subtle, the FNV-1a fallback runs instead; receipts made under the fallback are labeled as such and are not SHA-256 receipts.
- Layout was not eyeballed in a real browser for this build; DOM tests cover behavior, not visual layout.
- Sample missions are synthetic. The Berrien tax-lien sample uses invented parcel identifiers and invented figures, labeled synthetic on the page.
- The router is a fixed classification table, not a model. New deal types need a table entry, not a prompt.
- Share links carry the mission in the URL hash. Anyone with the link sees the mission text; do not put sensitive data in it.