Skip to main content -
Separate Your Build Model From Your Review Model: Codex as Adversarial Reviewer
-
A hash-chained manifest makes archive changes visible
-
Let AI suggest before you save
-
Manus pushed back on six of seven archive decisions
-
Don't Publish Into a Void: Baking Revenue Attribution Into the Schema on Day One
-
If Your AI Workflow Only Exists in Comments, You Have Exhaust
-
Your Committed Output Is a Free Golden Test
-
Why Publication-Time Redaction Is Not a Privacy Program
-
Reverse-Engineering Claude Code's Session JSONL (So You Can Mine Your Own Transcripts)
-
All Seven Reviewers Passed. The Writing Was Worse. Here's What Went Wrong.
-
The Most Restricted Tool in My AI Pipeline Is the One That Writes the Output
-
Reworking a vector-retrieval scoring formula: stop letting raw similarity be 100% of the base
-
AI Mutations Aren't Optimistic-UI Candidates: Make the 'Analyzing' State Honest
-
MOCK_INFERENCE=1: ship every LLM feature with an env-var kill switch on day one