Concepts
Current state
Current state is what the public record says now: lifecycle, tier, binding, freshness and evidence state. It is read live at the moment of reliance and never cached as truth.
Live in production and publicly readable, with no account and no key. Measured read-only on 2026-10-10.
Accountability Chain:Current state
State moves, so read it when it matters
A record that was active this morning can be suspended this afternoon. The Resolver serves every record with no-store and expects relying parties to re-resolve before high-risk action. A cached copy is an observation from the past, never current state.
{
"state": {
"lifecycle_state": "ACTIVE",
"parent_tier": "VERIFIED",
"verification_state": "PARENT_TIER_VERIFIED",
"abuse_state": "NONE",
"profile_state": "PROFILE_COMPLETE",
"reliance_level": "PARENT_IDENTITY_ONLY"
},
"machine_policy": {
"recommended_machine_action": "ALLOW_PARENT_IDENTITY_VISIBILITY_ONLY",
"high_risk_action": "FAIL_CLOSED_UNLESS_LIVE_BINDING_AND_EVIDENCE_AVAILABLE",
"fail_closed_states": ["REVOKED", "SUSPENDED", "DEGRADED", "MISMATCH",
"PROOF_UNAVAILABLE", "PUBLIC_PROJECTION_UNAVAILABLE", "ACTIVE_ABUSE_FLAGGED", "UNKNOWN"]
}
}The state axes
The public projection (contract 2.1.0) separates state into independent axes, each with its own reason codes, so one problem never hides inside another.
| Axis | States |
|---|---|
subject_state | ISSUED, ACTIVE, DEGRADED, SUSPENDED, REVOKED, SUPERSEDED, NOT_PUBLISHED, UNAVAILABLE |
freshness_state | FRESH, STALE, EXPIRED, NO_OBSERVATION, UNDETERMINABLE |
enrolment_state | ENROLLED, NOT_ENROLLED, PENDING_ENROLMENT |
publication_state | PUBLISHED, NOT_PUBLISHED, WITHHELD_BY_POLICY |
entitlement_state | ACTIVE, LAPSED, QUOTA_EXHAUSTED, ADD_ON_ENDED, UNAVAILABLE, NOT_APPLICABLE |
verification_service_state | AVAILABLE, UNAVAILABLE, DEGRADED |
receipt_verification_state | VERIFIED, RECORDED, VERIFICATION_UNAVAILABLE, FAILED, NOT_APPLICABLE |
The record names its own limits
resolver_v2.reliance.can_rely_on lists what a record supports, and do_not_infer lists what it must not be read as establishing. Both are binding on the reader. For this site’s operator today, a reader can rely on record existence, active parent state, current parent tier and public visibility, and must not infer domain, API, repository or asset control, agent authority, insurance, regulatory approval, safety, compliance or live operational monitoring.
Related
This page is explanation, not authority. Current state is only ever the live Resolver record. Live facts on this page were measured read-only on 2026-10-10.