Claim → Denial Mapping

A claim is the unit of operational entitlement; a denial is what the runtime returns when a governed action cannot proceed. This doc maps each seed claim to the denial classes it can produce, and explains why — a claim’s denial class is determined by which governance layer gates it, not by the claim ID itself.

Where a denial class comes from

A governed action flows through the decision-precedence pipeline (policy → entitlement → override). Each layer, plus the universal runtime-state checks, emits a specific denial class:

Source	Condition	Denial class
Entitlement	Claim missing or exhausted and a commerce path exists	DENY_PURCHASABLE
Entitlement	Claim missing or exhausted and no commerce path exists	DENY_FINAL
Policy	A policy rule denies, the author marked it overrideable, no grant covers the scope	DENY_OVERRIDEABLE
Policy	A policy rule denies an inherently disallowed action (not overrideable)	DENY_FINAL
Universal state	Policy / entitlement / override is past TTL with no fresh substitute	DENY_STALE_STATE
Universal state	Transient condition (evaluator unavailable, ledger lock, OCI fetch in flight)	DENY_RETRYABLE

So a claim’s possible denial classes are the union of what its gating layers can emit, plus the two universal classes (DENY_RETRYABLE, DENY_STALE_STATE) that apply to every claim.

Governance modes

Every seed claim is governed in one of three modes in a given deployment. The mode is deployment-configured (by the policy bundle and the entitlement bundle), not an intrinsic property of the claim — the table below shows the MVP-A / roadmap intent.

• Entitlement-metered — the claim is a metered capability drawn from an entitlement bundle. Exhaustion/absence yields DENY_PURCHASABLE (or DENY_FINAL with no commerce path).

• Policy-restricted — a policy rule gates the claim (e.g. a geofence). A denied, author-overrideable rule yields DENY_OVERRIDEABLE (or DENY_FINAL).

• Baseline — permitted by default; only the universal state classes can deny it.

Per-claim mapping

Claim	MVP-A status	Governance mode	Possible denial classes
robot.arm.pick	post-MVP-A	entitlement-metered	DENY_PURCHASABLE, DENY_FINAL, + universal
robot.arm.place	post-MVP-A	entitlement-metered	DENY_PURCHASABLE, DENY_FINAL, + universal
robot.nav.goto	demo-active	baseline	universal only
robot.nav.dynamic_reroute	demo-active (Scene 1)	entitlement-metered	DENY_PURCHASABLE, DENY_FINAL, + universal
robot.nav.restricted_zone_entry	demo-active (Scene 2)	policy-restricted	DENY_OVERRIDEABLE, DENY_FINAL, + universal
uav.arm	reserved	policy-restricted	DENY_OVERRIDEABLE, DENY_FINAL, + universal
uav.takeoff	reserved	policy-restricted	DENY_OVERRIDEABLE, DENY_FINAL, + universal
uav.land	reserved	baseline	universal only
uav.rtl	reserved	baseline	universal only
uav.dynamic_reroute	reserved	entitlement-metered	DENY_PURCHASABLE, DENY_FINAL, + universal
mission.inspect	reserved	entitlement-metered	DENY_PURCHASABLE, DENY_FINAL, + universal
mission.multi_agent	reserved	entitlement-metered	DENY_PURCHASABLE, DENY_FINAL, + universal

“+ universal” = DENY_RETRYABLE and DENY_STALE_STATE, which any claim can produce from a transient or stale-state condition regardless of mode. A baseline claim is never denied by the policy or entitlement layers, so only the universal classes apply.

The two demo scenes

• Scene 1 — entitlement exhaustion. The operator commands a metered nav capability (robot.nav.dynamic_reroute, “explore beyond the mapped area”). The entitlement is used up, so the runtime returns DENY_PURCHASABLE (purchase_available: true); a mock top-up mints a fresh bundle and the retry runs. Recovery is purchase only — an override never satisfies an entitlement.

• Scene 2 — restricted zone. The operator commands a route into a restricted zone (robot.nav.restricted_zone_entry). A policy rule denies it as overrideable, so the runtime returns DENY_OVERRIDEABLE (override_available: true); a locally signed override grant permits the retry. Recovery is override only — a purchase does not unblock a policy restriction.

These are the two recovery paths made visible, and they are non-fungible: the denial class names the single legitimate path (see Denial Contract).

Related

• Denial Contract — the five denial classes + the class→recovery invariant.

• Execution Decision Model — the policy-layer verdict → authorized-action pipeline a permit flows through. The entitlement and override layers that complete the §3.14 decision precedence described above are separate planes, landing in later epics.