RAIFFAProduct guide

Product overview

PUBLIC DEMO FLOW · TEST_ONLY · AUTHORITY NONEThe public GET response returns precomputed authority requirement checks · no real login, organizational authority, or external execution

Check the authority a request requires.

RAIFFA supports the decision without making it. It lays options side by side with their assumptions and keeps a record of who approved what, on what basis.

FIXED BLOCKED CASE

Block a request with missing authority requirements.

Check identity, session, and policy binding in a server-issued test request, then stop before evaluation when the binding is missing.
PUBLIC DEMO FLOW

REQUEST / FIXTURE

DecisionCaseRef
opaque / presentserver-issued descriptor
Policy profile
owner-held / pinned
Actor-session binding
MISSING

Block a request with missing authority requirements.

Input

REQUEST / FIXTURE

DecisionCaseRef
opaque / presentserver-issued descriptor
Policy profile
owner-held / pinned
Actor-session binding
MISSING
Verify

INTEGRITY / EXACT BINDING

Candidate integrity
PINNED
Owner policy plan
VERIFIED
Exact mapping
NOT FOUND
Result

FAIL CLOSED / RECEIPT

Status
BLOCKED_CONTRACT
Authorization
false
External effects
0No dispatch, release, or write
01

Check the authority requirements for a request

RAIFFA checks the human approval and authority basis for a request. Evidence or decision conditions alone do not create authority.

02

Separate request, approval, and execution

  1. 01
    Fix the requested action

    Identify subject, purpose, scope, expected impact, and stopping conditions.

  2. 02
    Verify authority and prerequisites

    Confirm role, validity period, limits, and required prior review.

  3. 03
    Record the human response

    Approval, rejection, hold, or request for more evidence must be explicit.

  4. 04
    Keep any future execution separate

    The current local validation does not transmit actions. If an operational connection is later provided under separate terms and verification, retain the authority-check record and actual execution outcome as separate events.

03

An authority record must precede action

A button state or job title is not sufficient authority. Request, approval, execution, and outcome remain separate events, each bound to a policy basis and validity period.

  • Requester, approver, and actual execution actor
  • Authority derived from a role, policy, or executed agreement
  • Permitted subject, purpose, action scope, and impact limit
  • Approval start, expiry, conditions, and revocation state
  • Execution outcome, failure state, and follow-up evidence coordinates
04

Record a blocking reason when requirements are not met

RAIFFA stops the request when authority or a safe execution path cannot be verified. It records the reason and the conditions required for another review.

  • No valid approver or governing role
  • Expired, revoked, or materially changed approval
  • Requested scope no longer matches approved scope
  • No permitted execution path or accountable actor
  • Execution outcome or audit evidence cannot be verified
05

The public execution checks authority requirements only

RAIFFA validates authority requirements and blocking behavior with fixed synthetic data in the public GET flow and local tests. It does not provide organizational authority, external execution, or autonomous execution rights.