governance-engineering-101
Not every rule an agent reads deserves the same force, and pretending otherwise breaks governance in one of two directions: either everything is "guidance" and quietly ignored, or everything is "law" and the system cannot evolve. In episode one we made quality an exit code. This
governance-engineering-101
Every post on this blog has to pass a blocking CI check before it can ship, exactly like code. Five gates run over every artifact: sensitivity, anti-slop, faceless-voice, no-overclaim, and conversion mechanics. A post with a bloated title, an uncited number, or a missing call-to-action fails the build, and no
governance-engineering-101
The field names its practice in rungs, and each rung names the artifact you engineer: the prompt, then the context window, then the harness, then the loop. Four serious fleet designs are running in public right now, and comparing them dimension by dimension shows the same two cells empty everywhere:
governance-engineering-101
There is a ladder the field climbs when it names its own practice. Prompt engineering: write better instructions. Context engineering: Tobi Lütke's term from June 2025, amplified by Andrej Karpathy: fill the context window with the right things. Harness engineering: Mitchell Hashimoto's coinage from February 2026: