Skip to content
Locus Locus Docs

Accuracy and boundaries

This page owns the public boundary for Locus answers. Locus helps people and agents understand local-government context around a property; it does not make the decision for them.

What goes in an answer

  • Property and place context: taxes, permits, zoning, flood, environmental records, local policy, development activity, projects, dates, and source availability.
  • Facts to verify, questions to ask, and bounded scenarios tied to records.
  • Coverage limits: what Locus can support for a place, what is missing, and where to check next.
  • Source details when available: source name, official URL or locator, fetched time, record id, and caveats.

What stays out

  • Scores, rankings, predictions, valuations, or safe/unsafe labels.
  • Tenant, employment, lending, insurance, background-check, or eligibility recommendations.
  • Named-person dossiers, mugshots, exact victim or suspect addresses, scraped personal profiles, or unnecessary owner names.
  • Legal advice or claims that a user must or should take a legal action.

Personal data and sensitive records

The subject is the place and its property context, not a person. Locus strips or avoids unnecessary names and person-level details. Incident and enforcement records are reports at a point in time; they are not proof of what happened, a conviction, or a statement about a person.

Absence is not evidence. If a source returns no matching records, that means no matching records were returned by that source under the current query. It does not prove nothing exists.

Why the answer is checkable

A Locus answer is built from structured tool results. A model may write prose around those results, but it is not allowed to invent facts, citations, or conclusions. When the record is thin, the answer should say so and point to the next source to verify.

Payment and coverage

Coverage is checked before paid outputs. Thin or unsupported coverage returns a free diagnostic instead of a surprise charge. Paid calls show the price before they return a result.

For the internal canonical policy, see the repository’s docs/SAFETY_AND_POLICY.md.