⇩ Markdown

considering dark software factories→dark software factory -- key media→blog post - OpenAI harness engineering 2026-02→review - Open AI harness blog post - 2026-02-22→validation script

validation script

A validation script can do automatic enforcement of various rules in the repository.

Backlinks

custom linting rule

One type of validation script

see in context
review - Open AI harness blog post - 2026-02-22
- I was unclear on what "enforceability" meant. I now think it means being able to run the gamut of validation scripts that are applied at every SDLC building block
  - These validation scripts run as continuous background checks
  - Could be similar to behavioral guardrails?
- They put a lot of effort into automating their code review, including it basically having its own ralph wiggum loop.
- It's not just no human -- coding, no human -- code review, and no human -- app verification. Within things like coding, it's about not needing to give any feedback. You shouldn't have to tell it "hey, you forgot a unit test... please add and TDD". That's far too involved, even if you aren't directly writing the code. Instead you need to try force that into the automated process. This feels like Kent Beck thought about what he did and distilled principles and practices into the Extreme Programming book, but these guys are doing it for agents, instead
- The onboarding a new teammate lens to agent context engineering. A Moc framing
see in context
We enforce this mechanically. Dedicated linters and CI jobs validate that the knowledge base is up to date, cross-linked, and structured correctly. A recurring “doc-gardening” agent scans for stale or obsolete documentation that does not reflect the real code behavior and opens fix-up pull requests.
...
Basically validation scripts... some of them are custom linting rules. specialized agent -- doc-gardening

see in context