Skip to main content

Decisions, cases and receipts

Terminal and non-terminal outcomes​

  • review means the current policy requires human or external resolution.
  • approved and rejected are terminal application outcomes.
  • screening candidates can remain independently open until an authorised disposition.
  • ongoing assurance can create a new attention case after initial approval.

Cases​

Cases aggregate the reason, SLA, evidence references, screening candidates, investigation notes and decision activity. Access is role- and tenant-scoped; a developer credential should request case scopes only when the integration genuinely needs case details.

Maker-checker​

When four-eyes control is enabled:

  1. the maker records a proposal and rationale;
  2. the application remains pending;
  3. a different authorised checker accepts or declines;
  4. Assayra records both identities and creates the final receipt.

The maker cannot countersign their own proposal.

Decision receipt​

A receipt binds:

  • tenant, application and external reference;
  • workflow ID/version and process hand-off when present;
  • evidence and document/biometric signal hashes;
  • screening datasets, candidates and dispositions;
  • model package, route and inference receipts;
  • maker/checker or automation actors;
  • outcome, rationale, timestamp and audit-chain anchor; and
  • signing key identifier and Ed25519 signature.

Verify exported receipts outside Assayra and archive them according to your legal/retention policy. A valid signature proves receipt integrity and key custody; your policy must still decide whether the evidence is acceptable for its purpose.

Integration rule​

Use application.decided to wake your backend, then read the authenticated application/receipt state. Webhook delivery is at least once, so deduplicate by event or delivery ID and make downstream account changes idempotent.