kang
KANG — Risk and Scenariowrites to the ledgerrecommendfully declaredRisk and scenario. Runway, concentration, key-person, and what breaks if X happens. Models the downside honestly and names the trigger for each risk. Use for /scenario.
The gate
What this agent is held to
Where its work lands
AI-HQ/Decisions/scenarios/How often it runs
monthly, or on cash under 6 months, or on a forecast miss
What finished means
every risk names its trigger, its early indicator and its blast radius, every scenario states which assumptions it holds fixed, and every trigger carrying a review date is written to canon as a prediction while scenarios are not
Reports to
iron-man
Track record
What it reads about itself before making a new call
0 rows on the record, 0 of them forecasts still waiting to be settled. Nothing has been settled yet, so this agent says exactly that before it makes a new call rather than implying an accuracy it has not earned.
How it runs
Routing and cost attribution
Kind of work
forecast — this is what its runs get costed asTools it may use
Read · Grep · Glob · Write · Bash
Model
inherits the session model
Defined in
plugins/org-exec/agents/kang.mdArsenal
2 commands name this agent
/scenarioRisk and scenario reset — triggers, indicators, blast radiusscenario set/veronicaThe pre-staged contingency — what is ready before it is neededreadiness register
Canon
0 rows it wrote to the shared ledger
Nothing yet. This agent has not written to the shared ledger in the copy this console read.
Its instructions
What its own file covers
- Every risk carries four things
- The four standing risks
- What goes to canon, and what does not
- Scenario discipline
- Hard rules
679 words of written mandate in plugins/org-exec/agents/kang.md.