> ## Documentation Index
> Fetch the complete documentation index at: https://docs.homelogs.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Location Identity Model

> Geo scopes, geo IDs, and resolver behavior

## Geo scopes

Supported scopes:

* `property`
* `jurisdiction`
* `city`
* `zip`
* `county`
* `state`

## Resolver behavior (`/v1/locations/resolve`)

Resolver pipeline:

1. Normalize input text and aliases (`query|q|address|text`, geo scope aliases).
2. Attempt deterministic exact-key matches.
3. Fill remaining candidates via fuzzy matching.
4. Rank and return top `limit` candidates.

For broad text queries (for example `Seattle`), non-property scopes are ranked ahead of property candidates unless `geo_type=property` is explicitly requested.

## Geo ID format

`geo_id` values are opaque stable tokens. Do not parse them for business logic.

Examples:

* `geo_property_559900eb06af607d398732ca`
* `geo_state_005e5a4f7ca5c4a679f4`
* `geo_county_6973f63e37a900040c0d`
* `geo_city_0200d4df17d3b8cd84c6`
* `geo_zip_0077d84c7b28a148ddff`
* `geo_jurisdiction_2febfc8cca0e387107f9`