How a Spatia report is assembled

1. Confirm the subject

A report is anchored to the resolved place shown to the reader. When the resolved address differs from what was entered, Spatia asks for confirmation before analysis starts. The report also carries the location-confidence context needed to interpret site-specific evidence.

2. Frame the question

The reader's role and question guide which evidence is most relevant and how it should be explained. They do not change the underlying facts. The engine's completeness checks come from the published catalog rather than a manually weighted risk score.

3. Query curated sources

Spatia selects from curated public-data layers and applies vetted analysis operations. A layer's stated spatial support, coverage, limitations, and evidence-grade ceiling travel with the result; a state-level capability is never treated as proof about a particular parcel.

4. Build truth records

• Observed findings record the claim, source, vintage, context, confidence, and evidence grade.
• Missing coverage and questions the data cannot settle become explicit gap records.
• Screening limitations stay attached to the evidence they govern.
• No finding receives a universal good-or-bad status; relevance depends on the reader's decision.

5. Explain without adding facts

The written summary may restate and organize the report's records, but it may not introduce facts absent from them. Server-side checks reconcile citations and material omissions. If acceptable prose cannot be produced, a constrained fallback is shown instead of partially trusted narrative.