graphsub.com / wiki / trading-control-graph
Trading Control Graph
A trading control graph maps positions, books, curves, scenarios, limits, approvals, and outputs for replayable risk and P&L workflows.
Definition
A trading control graph connects trades, books, portfolios, curves, limits, scenarios, model versions, approvals, and downstream outputs.
Why it matters
Financial systems need precise invalidation and replay. When a trade, curve, or model changes, only affected outputs should recompute.
GraphSub capsule
GraphSub packages trading control workflows into a capsule for risk technology, front-office platform teams, and audit-aware operations.
Code example
Dependency blast-radius querycypher
MATCH (s:Source {id: 'SOFR:2026-07-03'})
-[:FEEDS]->(m:Model)
-[:PRODUCES]->(o:Output)
WHERE o.status <> 'replayed'
RETURN
o.id AS output,
m.version AS model,
shortestPath((s)-[*..4]->(o)) AS proof_path
ORDER BY o.priority DESCFind downstream outputs that need replay after a source changes.
FAQ
- What does it replace?
- It complements existing risk systems by adding dependency graphing, replay, lineage, and proof outputs.
- Why graph-based?
- Financial outputs are dependency-heavy. Graphs naturally represent trades, curves, scenarios, owners, and affected reports.