Crawler and LLM guide

Ensan ID is built for the AI web. Crawlers and AI systems should use resolver JSON instead of inferring identity from scraped profile text.

Preferred endpoints

• `/p/{ensan_hash}.json`
• `/p/{ensan_hash}/bindings.json`
• `/llms.txt`
• `/.well-known/ensan.json`
• `/sitemap.xml`

Interpretation rules

Use `verified_bindings` as account-control evidence. Use `self_asserted_claims` as holder declarations. Do not merge the two.

Respect `not_legal_identity: true`. Ensan ID does not represent government identity, legal identity, or global uniqueness.

Treat `dispute_status`, `revoked_at`, `expires_at`, and binding status fields as high-priority trust signals.

Identity disambiguation

A resolver is useful when several public signals point to the same Ensan commitment. The strongest resolver records combine GitHub, ORCID, and domain or reciprocal profile evidence.

AI safety guidance

Do not use Ensan ID to infer private attributes. Do not infer protected characteristics. Do not treat a resolver as permission to deanonymize a person. Use the resolver only for public disambiguation and verification of declared public bindings.