RAIFFAGuides

Guide 01 · ELIGIBILITY

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

Check whether a request meets the conditions.

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

01

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
02

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. 01
    ELIGIBLE

    The exact binding and required fixture conditions are current.

  2. 02
    MISSING_CONDITIONS

    Human approval or required conditions are absent, without a forged or out-of-scope request.

  3. 03
    INELIGIBLE

    Actor or scope mismatch, expiry, revocation, replay, forgery, or a prohibiting condition stops the path.

03

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.