Parcel briefs that nametheir sources.
Parcel screening briefs built on public steward data, with provenance recorded at load time — live in a Hocking County pilot, built on statewide-Ohio architecture.
For brokers who need to defend a number, land-bank directors who need to triage a backlog, and probate attorneys who need a single page their client can read.
Steward sources
- FEMA NFHL
- USGS 3DEP
- USDA SSURGO
- ODNR
- County GIS
Screening reference only — not a flood determination, wetland jurisdictional study, insurance quote, or suitability opinion for any specific use.
Provenance chain
parcel #159535 · Hocking, OH · sample
In the pilot, overlay readings trace to these three rows — the steward who owns the data, the ingest run that loaded it, and the sha256 of the source artefact where the run recorded one. No override path, no manual fill-in.
Coverage
88 counties.
Six shown.
One pattern that scales.
Strata88 is named for Ohio's 88 counties. Today it runs an active pilot in Hocking with partial, lab-grade implementation in Athens, Franklin, Lake, Meigs, and Ross. Every county is added through the same catalog and county-manifest steps.
Why these counties?
Hocking is the founding rural pilot where the catalog originated, and where the ODNR-adjacent steward sources (oil & gas wells, soil-class, NFHL floodway) matter most. Franklin is the urban-density stress test — most steward sources, highest parcel volume, hardest naming-collision cases. Athens, Lake, Meigs, and Ross are lab counties too, each loaded from its own county GIS parcel service.
- Hocking
- Logan
- Active pilot
- Athens
- Athens
- Lab county (partial)
- Franklin
- Columbus
- Lab county (partial)
- Lake
- Painesville
- Lab county (partial)
- Meigs
- Pomeroy
- Lab county (partial)
- Ross
- Chillicothe
- Lab county (partial)
Boundaries · Ohio DOT (ODOT) county boundaries · all 88 counties shown
What you actually get
A token-gated brief, rendered server-side.
The brief links the stewards it holds a pointer for. The link is revocable and the audit log records every fetch.
Parcel brief · Pilot
Parcel159535
Hocking County, Ohio
Last refreshed
Wed 2026-05-27 · 14:23 EDT
Regulatory Floodway intersect (FEMA NFHL)
Part of the SFHA where NFIP rules bar building or fill unless an engineering study shows no rise in flood levels or FEMA first approves a conditional map revision. Confirm via FIRM and floodplain administrator.
Steward: fema_nfhl
Screening summary
- hit
Modeled flood zone (SFHA)
FEMA NFHL overlap heuristic — not LOMA or insurance rating.
- hit
Stream / flowline intersect
Large-scale NHD flowline geometry intersects parcel.
- clear
Wetland polygon overlap (NWI)
NWI mapping — field verification may differ.
- clear
Land listed in PAD-US (overlap)
PAD-US overlap — not fee title or easement legal status alone.
What we checked
| steward | run | refreshed | artefact sha256 |
|---|---|---|---|
| FEMA NFHL | #100 | 2026-05-27 | 2b91…c4af |
| USGS NHD | #47 | 2026-05-26 | 6d04…91ce |
| ODNR oil/gas wells | #75 | 2026-05-27 | f1b2…8a73 |
| ODOT mapped roads | #32 | 2026-05-24 | a78d…4e15 |
algorithm:diligence_diff_notifier_v1· Screening reference only — not a flood determination, wetland jurisdictional study, insurance quote, or suitability opinion for any specific use.
Illustrative render of a Hocking County demo parcel. In the pilot, every applied overlay reading is stamped with the ingest run that loaded it.
Who it's for
Built for three concrete jobs.
Strata88 is opinionated about who it's for. Pick the role closest to yours — the rest of the page is the proof.
A steward-attributed parcel brief you can hand a buyer in two minutes.
One token-gated link — the screening summary, the steward-attributed overlay table, and a printable record. Your client opens it on their phone: no signup, no account, no marketing follow-up.
Question a flood, wetland or stream reading later and it resolves to its named steward and the ingest run that loaded it.
Request a sample brief
Triage the Tier 2 backlog without paying a consultant.
A free batch script ranks your held inventory against the same screening overlays Strata88 uses internally — flood, wetland, slope, soil-suitability. Runs on your own machines; no upload, no PII required.
Get the Tier 2 triage script
Probate attorneysHand heirs a single page that explains what they inherited.
The brief summarises the screening flags and steward provenance for an inherited parcel in a pilot county. You keep the attorney–client relationship; Strata88 is the screening reference your closing letter cites.
Request a sample heir's brief
What it produces
Three artifacts a broker canactually hand over.
One sample deal, rendered three ways — a print-ready one-pager, an offline vector map, and a Google Earth layer.
- Clear
- Review
- Flag
01 · Print-ready page
Deal one-pager
The offline map composed with the offering screening — selling points, what's worth a closer look, and a six-tract table — into one print-ready page.
BULU Scene map
A pure, offline vector map — deterministic, no live tiles. Its traffic-light palette matches the Google Earth export and the brief, down to the pixel.
Export to Google Earth
A deterministic KMZ — traffic-light status, 3D extrusion, and a branded balloon — that opens straight in Google Earth.
Cedar Hollow — a six-tract demo over real Hocking County parcel outlines. Deal name, grouping, and screening are illustrative — screening-grade, not a survey or title opinion.
Architecture
Three architectural choices behind every brief.
Without them you have one more parcel viewer. With them you have something a buyer or a regulator can trace back to its public sources.
No implied legal clearance
Nothing on a brief is legal clearance, and no source we load is marked cleared for commercial use. The platform refuses to lie on your behalf.
Steward-attributed, stamped at load
Every applied overlay reading in the Hocking pilot is stamped with the ingest run that loaded it, and every brief links the stewards it holds a pointer for (FEMA NFHL, ODNR, USGS). No hand-waving, no "trust us" boxes.
Auditable from MCP tool to source row
Strata88 wrote its own MCP audit conformance standard. Every agent-facing tool emits a v2 envelope: the sources it lists, three separate dates, and an explicit 'not measured' where a date is unknown, so a caller can check an answer against the agency it cites.
On every Land Card
Brokers interrogate the brief.
The bot only answers from the tool chain.
Six fixed playbooks call the same MCP tools that produced the brief itself — no free-form chat, no hallucinated stewards, no answers the audit log can't reproduce.
Pick a playbook
- Explain screening flags
- What wasn't checked?
- Explain soils
- Explain terrain
- Where did this data come from?
- Full screening brief
Each playbook runs a fixed MCP tool order. Same JSON the Land Card uses — no parallel truth, no second story.
Broker asks
"Where did each of these screening flags come from? I need to be able to cite this to my buyer."
Land Bot · provenance_receipts
3 tools · 412msFive of the screening layers on this parcel resolve to the following stewards and ingest runs.
| column | steward | run | refreshed |
|---|---|---|---|
| nfhl_overlay_ingest_run_id | fema_nfhl | #3458 | 2026-08-30 |
| nhd_overlay_ingest_run_id | usgs_nhd | #790 | 2026-06-07 |
| nwi_overlay_ingest_run_id | usfws_nwi_wetlands | #1563 | 2026-07-12 |
| mapunit_ingest_run_id | nrcs_ssurgo_gssurgo | #710 | 2026-06-06 |
| padus_overlay_ingest_run_id | usgs_padus | #511 | 2026-05-31 |
Tool chain: parcel_provenance_chain_tool· 5 rows shown · screening reference only — not a flood determination, wetland jurisdictional study, insurance quote, or suitability opinion for any specific use.
What it refuses to answer
- "Is this parcel a good investment?" — no commercial outcome promises.
- "You're flood-free." — no binary determinations; flags + escalation only.
- "Can I build a cabin here?" — lists relevant flags, defers to zoning / surveyor / Corps.
Illustrative render of the in-product Land Bot panel. Playbook names match shipped LB0–LB3 playbooks in the BULU repo; sample values are representative, not live. Reference: LAND_BOT_PANEL_IMPLEMENTATION_PLAN.md.
Engineering
The discipline IS the product.
Strata88 is a one-person operation today. The architecture choices, test coverage, and stewardship metadata are the substitute for having a team to enforce them.
- 1,440
- test functions, green on every PR
- 407
- Python modules in the active app
- 56k
- lines of Python
- 58
- Alembic migrations
- 48
- MCP tools (+ 8 prompts, 13 resources)
- 0
- TODO / FIXME markers in active code
Stack
- FastAPI
- PostgreSQL · PostGIS · pgvector
- Celery · Redis
- Alembic
- Jinja2 · WeasyPrint (PDF)
- KML/KMZ · SVG (BULU Scene)
- MCP (Model Context Protocol)
- Astro · Tailwind · React
- Cloudflare Pages
Source
Disciplines that show up in every brief
- Strict type discipline
- ruff + mypy strict across every source file. The full test suite is gated in CI on every PR; nothing merges red. Refactors are mechanical because the types and tests catch them.
- Catalog stewardship metadata
- Every data source carries a YAML manifest with steward class, data plane, commercial gate, and rotation cadence. CI fails if the manifest drifts from the catalog. No silent dataset additions.
- Lifecycle-tiered documentation
- ADR-governed (10 ADRs, incl. ADR 0009 'BULU Scene' presentation plane) docs grouped by lifecycle (active, runbook, archived) and tier (core, ops, archive). The active-docs TOC is auto-generated from front matter and CI-checked for drift.
- MCP audit conformance standard
- Strata88 wrote its own MCP audit envelope standard (now v2) and a conformance harness that checks every agent-facing tool, so each answer carries the sources it lists, its dates and what it did not measure.