When the LP asks “when did you know,” the record already answers.
Platform architecture explains how evidence becomes pressure, pressure becomes a typed decision, the downside is tested, a path is chosen, and output is generated without rebuilding context. One spine. Three engines. One inspectable record.
The system spine, in five moves.
1. Pressure
Evidence becomes a pressure signal tied to a specific investment.
Covenant stress, KPI drift, refinance-window compression, operator variance. Pressure enters the queue with provenance — which document, which signal, which date — not as a dashboard threshold crossed in isolation.
2. Typed decision
A committee call, not a watchlist flag.
Pressure routes into a typed decision: monitor, stabilize, intervene, hold, or exit. Each type carries its own required evidence, approval basis, and materiality threshold. That is what lets the system later surface a broken decision rather than just a moved metric.
3. Fail-first test
The downside is tested before the path is chosen.
The scenario engine runs the specific shock against the position — power, rates, refinance window, sector channel — and returns break order, headroom loss, and downside intensity. Not a generic stress. A shock pack tied to this deal's transmission path.
4. Chosen path
The intervention is ranked, selected, approved, and logged.
Available stabilizers are ranked by time bought and capital required. The committee approves the path against the fail-first test. Approval is bound to the scenario and the memo it was approved on — not a Slack thread.
5. Governed output
IC memo, board deck, lender pack — generated from the live record.
Output inherits the chain. No rebuild from static files. No drift between the approval context and the artifact the committee reads next quarter. The output is replayable against the same record it came from.
Three engines, one record.
Each engine owns one piece of the loop. The record is what keeps them connected — and what makes a decision inspectable six quarters later.
Preserves the full chain from pressure to action to outcome — and surfaces the moment the original call stopped holding. Not a log. A governed record.
Turns a macro or operating shock into sector sensitivity, company exposure, covenant stress, and ranked downside impact. The propagation path, not just the scenario label.
Keeps evidence, assumptions, decisions, and outputs linked over time. The chain stays queryable across ownership changes, committee turnover, and quarterly rebuild cycles.
Four inspections the record has to support.
How pressure became a decision
The full provenance — signal, scenario, approval.
Inspectable without reconstructing from emails or files. This is the first question LPs, lenders, and incoming leadership ask. The record has to answer it directly.
What assumptions changed
Before a path was chosen, what shifted?
Assumption movement is logged against the original approval. Not just what the numbers are today — what the basis was, where it shifted, and whether the shift was material to the call.
Which interventions were approved and executed
Approval basis, execution history, outcome.
The system preserves which stabilizer was selected, which was rejected, who approved, and what actually happened next. The gap between approved path and executed path is itself a governance signal.
Governed outputs from the operating record
IC memos, board decks, lender packs — from the same context.
Output does not drift from approval context. The same record that holds the decision produces the artifact the committee reads next quarter.
The architecture behind the architecture.
- Platform featuresDecision Ledger, Investment Memory, Scenario Engine, Governance, Investment Decision Replay — the five features this architecture supports.
- See the propagation engine liveThe Hormuz page shows the same engine turning one macro shock into deal break clocks, fund collisions, and a forced portfolio sequence.
- The decision integrity gap48 sources, 14 vendors, and the missing 7th layer this architecture was built to occupy.
See the architecture running on a real deal.
The three engines are easy to describe. Seeing them run on one of your positions is the test. Bring us a deal — we'll show you the record the architecture produces.