Canonical shape
Every case carries the same envelope:
The
subject shape varies with the case type:
- transaction
- kyc
- kyb
Lifecycle of a case
1
Open
Posted to the workflow endpoint or fanned-out from a stream. Validated
against the workflow’s input schema.
2
Enrich
Data Source and Custom API nodes attach vendor responses to the case
context.
3
Evaluate
Rule, Decision Table, AI and Scorecard nodes consume the enriched context
and emit a verdict.
4
Route
Split nodes send the case down the appropriate branch — auto-approve, manual
review, block, regulator report.
5
Decide
Terminal Output node writes the decision. Analyst may override from the
queue within the audit retention window.
Idempotency
Frayme can receive anidempotencyKey as the idempotency key. A second post with the same key returns the previously committed decision rather than re-running the graph.