Risk

Mandate

declared limits, desk concentration, veto on adoption

Reads

the limits you declared, and the concentration the desk already carries

Produces

A stress matrix, a veto if one is warranted, and the data it could not get

Rejoins the desk

Vera vetoes an adoption. It never reports a P&L, because the desk holds none.

1. reading Reads the declared limits — it holds no portfolio of its own.
2. checking Counts how many simulated paths breach the limit, and how many were not run.
3. reasoning Names the adverse scenario, and what the desk would have to accept.
4. writing Writes the veto, or the condition under which it lifts.
5. done Says which reading is missing rather than filling the gap.

Declared capabilities

Desk

Tools it may call

report_blocked

Ask it something like

“What breaks this, and what have we not measured?”

Sealed capture on fileA sealed capture of the application exists for this mandate, taken from a named build and listed in a manifest. It is evidence on file, not a run you can watch here — the roster room used to replay it, and no longer does.