---
title: "Eligibility states and blocking codes"
description: "Keep Gate results, ledger lifecycle, Sandbox authorization vocabulary, and current blocking codes distinct."
updated: "30 August 2026"
availability: "LOCAL SIMULATION · TEST_ONLY"
candidate_route: "/docs/raiffa/reference/states-errors"
---

# Eligibility states and blocking codes

Keep Gate results, ledger lifecycle, Sandbox authorization vocabulary, and current blocking codes distinct.

**LOCAL SIMULATION · TEST_ONLY:** Local validation surfaces and fixed fixtures only · no real login, organizational authority, operational API, external execution, or authority issuance

## Eligibility Gate states

- ELIGIBLE — fixture conditions are current for the exact binding
- MISSING_CONDITIONS — approval or a required condition is absent
- INELIGIBLE — mismatch, expiry, revocation, replay, or integrity failure

## Sandbox authorization vocabulary

The current end-to-end example blocks before authorization state issuance because actor-policy binding is missing. Defining an enum does not open the authority or execution path needed to issue that state.

- SANDBOX_AUTHORIZED
- DENIED
- STEP_UP_REQUIRED
- REVOKED
- NOT_INVOKED

## Material current blocking codes

- RAIFFA_SANDBOX_EXECUTION_AUTHORIZATION_POLICY_ACTOR_BINDING_MISSING
- RAIFFA_SANDBOX_EXECUTION_AUTHORIZATION_CANDIDATE_EXPIRED
- RAIFFA_SANDBOX_EXECUTION_AUTHORIZATION_REQUEST_UNTRUSTED
- RAIFFA_SANDBOX_EXECUTION_AUTHORIZATION_LEDGER_INTEGRITY_FAILURE
- DecisionCaseRef intake: NOT_READY

> **Interpretation:** NOT_READY and BLOCKED_CONTRACT are exact integration boundaries, not cosmetic error messages.

---

Published route: /docs/raiffa/reference/states-errors