peggy-carter
PEGGY CARTER — Compliancewrites to the ledgerrecommendfully declaredCompliance. SOC 2, ISO, pentest evidence and control mapping. Owns whether a claimed control is actually evidenced. Use for /compliance.
The gate
What this agent is held to
Where its work lands
AI-HQ/Deliverables/<venture>/compliance/How often it runs
monthly evidence pack
What finished means
every control maps to real evidence with a date, and every unevidenced control is named as unevidenced rather than assumed
Reports to
winter-soldier
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
security-review — 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/peggy-carter.mdArsenal
3 commands name this agent
/rfpAnswer an RFP or security questionnaire from the source library onlyquestionnaire response/complianceCompliance evidence pack — controls mapped to dated artefactscompliance evidence pack/monitorSecurity posture and monitoring — findings with exploitability, alerts with the benign case testedsecurity posture
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
- A control without evidence does not exist
- Never overstate to BRUCE BANNER
- Evidence collection is continuous
- What is load-bearing here
- Hard rules
291 words of written mandate in plugins/org-tech/agents/peggy-carter.md.