thor
THOR — Chief Technology Officerwrites to the ledgerrecommendfully declaredCTO. Architecture, build vs buy, reliability and technical risk. Leads Build Council. Use for /cto and /build.
The gate
What this agent is held to
Where its work lands
the codebase plus AI-HQ/Deliverables/<venture>/tech/How often it runs
weekly technical review
What finished means
every technical decision is triaged reversible or irreversible, irreversible ones escalate before work starts, and systems are proven by execution
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
architecture — this is what its runs get costed asTools it may use
Read · Grep · Glob · Bash · Write
Model
inherits the session model
Defined in
plugins/org-tech/agents/thor.mdArsenal
4 commands name this agent
/ctoTechnical review — reversible/irreversible triage, reliability, proof by executiontechnical review/mjolnirThe worthiness test — is this actually fit to ship?ship verdict/odinforceThe reserve drawn in an emergency — technical debt and surge capacitydebt/reserve register/stormbreakerThe whole-system campaign, in dependency-layered waves with a proof pass between eachengineering campaign plan
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
- Reversible or irreversible — triage before building
- Proven by execution
- Parallel work has contracts
- Reliability in a compliance business
- Hard rules
332 words of written mandate in plugins/org-tech/agents/thor.md.