Design backward from a money metric through constraints, modeling, assurance, and live guardrails
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
Design Backward
• Start from a dollar-denominated business metric
• Encode regulation and explainability as constraints first
• Choose the model last, to fit the constraints
Why Finance Differs
• Errors are immediate and quantifiable in money
• Regulators can demand a reason for every decision
• Distributions shift and adversaries probe on purpose
Live Assurance
• A blocking gate pairs backtests with explanations
• Monitoring tracks drift and realized dollar impact
• Regime shift triggers an owned retrain-or-halt response
Workflow 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