Mandate to collection to R-transaction reversals as explicit state
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Collection cycle
• Mandate (UMR + creditor ID) authorizes the pull
• Pre-notification precedes every collection
• FRST opens the series, RCUR repeats it
R-transactions
• Reject: before settlement, nothing moved
• Return: after settlement, funds clawed back
• Refund: debtor claim, up to 8 weeks (13 months if unauthorized)
Engineering rules
• Every transition is driven by a typed reason code
• Settled is provisional, not final
• Reversals post compensating ledger entries
Lifecycle diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • [/] views • P play story • T theme • E export