What Strata88 is. What it isn’t. What you must do anyway.

1 · Pilot scope is limited

Strata88 runs against an active pilot in Hocking County, Ohio, with partial implementation in three lab counties (Athens, Vinton, and Franklin). The remaining 84 Ohio counties have not been probed or ingested. The presence of a county name, an outline on the map, or a schema reference in our repo is not a claim of data coverage or commercial clearance. If you submit a parcel from a county outside the pilot scope, expect a polite decline.

2 · Outputs are screening-grade

Everything Strata88 produces — the parcel briefs, the JSON land-context objects, the Land Card preview, the Land Bot panel, and any narrative summary — is intended for triage, screening, and research support only. Under no circumstances do these outputs constitute a regulatory determination, a certified survey, a title opinion, a flood-zone certification, an environmental clearance, a zoning ruling, or investment advice. If a decision turns on one of those, you need a licensed professional, not a brief.

3 · Professional substitution is mandatory

Strata88 is not a substitute for professional expertise. Before any binding physical, financial, or legal decision about real property, land use, or development, you must consult the appropriate professional — typically one or more of:

• licensed land surveyors,
• real estate attorneys,
• professional engineers,
• local zoning officials,
• local floodplain administrators, and
• the U.S. Army Corps of Engineers (for wetlands and waters-of-the-U.S. boundaries).

A Strata88 brief is a starting point for that conversation, not a replacement for it.

4 · Third-party data carries third-party terms

Strata88 aggregates data from public stewards including OGRIP, county auditors, FEMA, USFWS, NRCS, USGS, USDA, ODOT, ODNR, the U.S. Census Bureau, OpenAddresses, OpenStreetMap, Microsoft Buildings, and Open-Meteo. Public accessibility for individual lookup is not a redistribution license. If you intend to reuse, host, or resell data sourced through a Strata88 brief, you must independently verify and comply with the licensing and attribution terms of each upstream steward. We track those terms internally; we will not advise you on yours.

5 · AI agent output is an unverified draft

Any narrative, summary, or decision support generated by the Land Bot, by our Model Context Protocol (MCP) server, or by any external Large Language Model reading our JSON should be treated as an unverified draft until a human with the relevant expertise has checked it. Our agents are explicitly designed to refuse common binary determinations — “you can build here,” “this won’t flood,” “this is a good investment” — and to escalate to a human instead. If you ever see Strata88 produce one of those determinations, treat it as a defect and tell us.

6 · Liability and code licensing

To the extent permitted by applicable law, the maintainer and contributors disclaim all liability for any direct, indirect, or consequential damages resulting from decisions made in reliance on this site, the briefs, or the data outputs. This page governs the data, processing pipelines, and outputs of the project. The licensing of the underlying software source code is governed independently by the repository’s LICENSE file.