Eligibility, identifier enrichment, validation, submission to ARM/TR, and the break management loop
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
Primary Reporting Path
• Trades and reference data feed eligibility and enrichment left to right
• Every report is validated locally before it reaches the venue
• Labels name data assets, not generic API verbs
Identifier Enrichment
• LEI, UPI, UTI, and ISIN are attached from external reference sources
• Each value records its provenance as future audit evidence
• Stale or lapsed identifiers are the top cause of rejections
Break Management Loop
• Venue NACKs and reconciliation breaks flow into a tracked workflow
• Remediation carries a correction or cancel action, never a naive resend
• Root causes feed back upstream to enrichment and eligibility
Data-flow 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