frankekn

Cheap-model adversarial verification pass for the end of every implementation phase and before any merge. Framing beats model tier — a low-effort model with the right question finds real bugs the expensive authoring model missed.

Eight falsifiable rules for prompting CLI coding agents and review lanes, each derived from an observed failing-form vs working-form pair. Use when composing any prompt for a coding agent or reviewer fanout.

Orchestrate CLI coding agents (codex, grok, aider, etc.) so agents write ALL implementation code while the orchestrator plans, reviews diffs, runs tests, and commits. Use for any implementation task in a multi-agent setup.

Discipline for algorithm and ranking changes — hand-designed signals are usually wrong in direction, not just magnitude. Build an offline backtest first; the backtest script becomes the behavior spec; numeric gates decide mergeability.

The laws that keep plausible-but-broken AI-generated code away from main, derived from a real 104-PR bulk-merge disaster. Apply to every merge, every "done" claim, and every batch operation.

Treat memory files, summaries, handoff docs, and other agents' reports as unverified claims. Inheritance tells you where to look; only the current checkout tells you what's true. Apply whenever acting on knowledge you did not derive this session.

Use before costly implementation to obtain independent, falsifiable PROCEED / STOP / PIVOT advice on the same decision surface. In Signoff mode, fill the generated COUNCIL.json and let ./signoff lock validate quorum, shared claims, hashes, and conflict closure.

Use after executable verification for independent read-only review of one sealed patch against one locked contract. In Signoff mode, fill review-*.json and JUDGMENT.json; ./signoff roast enforces role separation, complete criterion coverage, finding accounting, and evidence-based conflict closure.

Use for engineering work that must autonomously write a specification, obtain independent Council pressure, implement one bounded slice, prove it with executable receipts, obtain independent Roast review, and continue without goal drift or AI slop. The ./signoff state machine is authoritative.

Scaffold a new module for open-omarchy-macos. Creates modules/<name>/ skeleton, wires the installer entry, adds doctor checks, extends the smoke test, and updates the README keybindings table. Use when the user says "add a module" or "scaffold module <name>".

Verify a freshly installed (or updated) open-omarchy-macos setup by chaining status, doctor, and smoke-keybindings. Use after running ./scripts/install.sh or when the user asks "is everything wired up?", "verify install", or "is my setup healthy?".

George Hotz–inspired radical-simplicity rules for coding. Load when refactoring, simplifying, or reviewing code; when a change is growing a new layer / abstraction / config flag / adapter; when a function is sprouting many parameters; or when you're about to assert code "works" without looking. Complexity is the enemy — remove before you add. Unofficial; distilled from George Hotz's public statements.