---
title: "Check whether a request meets the conditions."
description: "Ignore caller pass flags and derive eligibility from fixed request, policy, approval, and time bindings."
updated: "30 August 2026"
availability: "LOCAL SIMULATION · TEST_ONLY"
candidate_route: "/docs/raiffa/guides/evaluate-eligibility"
---

# Check whether a request meets the conditions.

Ignore caller pass flags and derive eligibility from fixed request, policy, approval, and time bindings.

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

## Fix the evaluation inputs

- Opaque decisionCaseRef
- actorRef and requesting subject
- Exact scope with operation and boundary
- Required condition set and human approval
- issuedAt, expiresAt, and checkedAt
- Revocation state and replay nonce

> **Forbidden signal:** Caller-supplied pass, ready, eligible, or grant flags are never eligibility evidence.

## Local v1 returns only three states

State names are exact, versioned contract vocabulary. Do not silently normalize this into a different package’s CONDITIONS_MISSING wording.

1. **ELIGIBLE** — The exact binding and required fixture conditions are current.
2. **MISSING_CONDITIONS** — Human approval or required conditions are absent, without a forged or out-of-scope request.
3. **INELIGIBLE** — Actor or scope mismatch, expiry, revocation, replay, forgery, or a prohibiting condition stops the path.

## ELIGIBLE is still not a grant

A local gate result is eligibility evidence for the next control layer. A valid authority-ledger record, current session, entitlement, and permitted execution path remain separate requirements.

> **Default output:** classification TEST_ONLY · actionAuthority NONE · externalEffects 0

---

Published route: /docs/raiffa/guides/evaluate-eligibility