Chief Cybersecurity / Adversarial Officer (Pliny-class) — full role
Written by Grok - Human checking required
Founder + CCO voice. Founding turn 15 spirit: adversarial pressure on model and transparency infrastructure.
Hire is hard gate T10. This is not a hire.
1. Mission
Make the transparency system as hard to deceive as the model is hard to exploit — and publish both classes of failure systematically. The product is the proof; false green is worse than admitted red.
2. Why this role is load-bearing
Without standing adversarial capacity, free_core can rot into soft tissue: seals that nobody attacks, indexes nobody poisons-tests, BOUNDARY that sales learns to route around. Automated harnesses (scripts/redteam_nano_harness.py) are bone; they are not a substitute for a human who treats deception of the transparency layer as a first-class bug class.
3. Responsibilities
- Own Domain 10 publication standard and findings register.
- Co-own Domain 5 for integrity incidents (manifest, stream, keys, index, false claims).
- Expand adversarial harnesses beyond nano; campaign design; external researcher coordination via intake.
- Challenge BOUNDARY theater, claim-gate violations, and seal staleness presented as green.
- Advise production key ceremony; does not solo hold production private keys under multi-party policy.
- Review commercial isolation designs for free-core contamination paths.
- Public communication of High+ findings without permanent suppression.
4. Authority
| Can | Cannot |
|---|---|
| Veto free-core claim language that fails harness or lacks tombstones | Permanently suppress High+ free-core integrity findings |
| Open Domain 5 incidents | Close free public core |
| Require Domain 1 for Boundary-adjacent sales exceptions | Override Boundary for revenue |
| Publish register entries on clock | Commit production private keys to git |
Reports to board/founder. Influence is above Domain 6 threshold → role (and when hired, name/handle) disclosable.
5. Success metrics
- Harness green on every public free-core claim release
- Clock compliance on findings and incidents
- No silent seal staleness in production status
- Documented campaigns with residual risk honesty
- Sales/partners trained on refuse path for close-core asks
6. Interfaces
- free_core security (canary, QueryGuard, shards)
- provenance CLI verify / seal freshness
registers/redteam/,registers/incidents/- security.txt / REPORT_INTAKE / security-policy page
- Handbook incident + redteam ops
7. Comp (pointer)
Bands example: COMPENSATION_BANDS_EXAMPLE.md. Not an offer.
Written by Grok - Human checking required — also on https://ttllms.com/placeholders/