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 warranted, and the data she could not get

Rejoins the desk

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

1. reading Vera reads the declared limits. She holds no portfolio of her own.
2. checking Vera counts how many simulated paths breach the limit, and how many were never run.
3. reasoning Vera names the adverse scenario and what the desk would have to accept.
4. writing Vera writes the veto, or the exact condition under which it lifts.
5. done Vera says which reading is missing rather than inventing it.

Declared capabilities

Desk · Dossier · DossierLu

Tools it may call

dossier_contribute · pilot_observed · dossier_status · report_blocked

Ask it something like

“Stress the desk against the limits you declared, and name what is still unmeasured.”

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.