Deciding fault takes a record outside the agent's failure domain. ThetaCog writes one: a receipt showing whether the instruction or the work left the lane, read from the commit against the spec declared before the run, with zero models in the loop. Free to run (MIT); patent pending (US Patent App. 19/637,714).
Skill Claude CodeCodex
Run one steer file round after round from Claude Code, in any repo the ThetaCog extension is installed in — a round, then a settle (reap, unload local models, rest until the machine is calm), under a dollar budget projected before every round — through the installed doors only (npx thetacog-mcp ). Triggers…
Skill Claude CodeCodex
Run ThetaCog's attractor loop from Claude Code, away from home — the sensors, the map, both arms — through the installed extension's own doors (npx thetacog-mcp ), never a thetadrivencoach-only command. Splits a multi-job ask into numbered rows before running any of them, plans only unless told to go, and refuses to…
Skill Claude CodeCodex
Go through every board sheet with /steer and keep them reasonable, consistent and aimed at the most aggressive outcome the record supports: pull every sheet, run the consistency checklist, turn each break, gap, comment and trailing aim into a /steer row, rewrite the sheets cell by cell, and report. Triggers: '/tend'…
Skill Claude CodeCodex
Fill in or refine the ten standing answers (the deployer's readiness check, in insurance the proposal form) from this repo's own code and record, and save them into .thetacog/deployer-playbook.json — the same file the ThetaCog sidebar's 📝 boxes and /backup/warranty save to. Triggers - '/standing-answers', 'fill in…
Skill Claude CodeCodex
The project sheets — one sheet per project (Project · GTM, Project · Code) that prints how the steer is doing: what is done over what is next, every row a spec row with its guard, its files, its tags and its Merkle leaf, a comment and a ✓/✗ cell on each, ticked rows moved into DONE · LOG by program. Steer writes them…
Skill Claude CodeCodex
Shows the default way to run a multi-job ask: one Claude Code session, one spec, every job a row, worked through /steer one row at a time with npx thetacog-mcp doors only. Running several sessions at once is an appendix, marked optional. Triggers: '/allocate', 'allocate this work', 'how do I split this up', 'should I…
Skill Claude CodeCodex
The ThetaCog board — the 2-D surface beside the panels: read the sheet, answer a row, file a report, pull the operator's answers and comments back onto their rows, refresh the sheets in Drive. Every command here exists and is guarded. Triggers: 'pull the sheets', 'pull down the drive sheets', 'pull the board'…
Skill Claude CodeCodex
Check this ThetaCog install and write the handoff: runtime, the IntentGuard addon, the walk binary for this platform, the demo run twice for the same digest, the MCP server's tool list, and whether every coding agent here (Claude Code, Cursor, Gemini) has the /steer skill. Writes .thetacog/doctor/handoff.md, ready to…
Skill Claude CodeCodex
The operator's licence desk from the Claude Code CLI: grant licence credits after a meeting, mint a claim link, move a grant to someone's personal email, revoke it, issue or revoke a licence key on the tape, list the keyring, see every claim link's status, and read the licence funnel and the paid funnel (who bought…
Skill Claude CodeCodex
Manage your ThetaCog licence from the Claude Code CLI, the same doors the extension's 🔑 pills open: connect this machine and buy credits (login and payment happen on thetadriven.com), paste a licence key, see which licence this machine holds, sign a commit under it, back up the tape for countersigning, and…
Skill Claude CodeCodex
The anti-slop pass on one file, run wherever /steer runs. A reader model reports where its comprehension breaks, a deterministic slop detector (no model in it) scores hedges, filler and narrator-voice lines, and each cold sentence gets rewrite candidates ranked by slop removed and readability gained. Dry-run by…
Skill Claude CodeCodex needs its repo
After signing into Google once, write the Asks sheet (every ask of this steer run, then every ask the extension has ever carried, one row per ask in the Steer · Compiled layout: plain head, verbatim span, guard, state, commit and Merkle leaf) and, on ask, the Spec · Tree sheet (the spec's Merkle tree, root first).…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: