Generation is cheap. Verification is the factory.
A dark software factory succeeds when it makes output cheap to verify, not when it makes more output.
A dark software factory succeeds when it makes output cheap to verify, not when it makes more output.
The industry swung from treating token spend as a badge of honor to treating it as a liability in about a year. Both eras managed the same wrong number.
Selection evals answer which model, prompt, or harness to use. Acceptance evals answer whether this system ships. They want opposite tooling, and conflating them is why eval suites rot.
Writing a post about graph engineering forced the glossary to define graphs. Defining them produced a working one. Six hours later it replaced the search box. Receipts included.
Graph engineering is a useful way to expose control, state, knowledge, and improvement relationships, but only when we stop treating every graph as the same thing.
The hard part of agentic infrastructure is not the model loop. It is resumability, budget control, idempotent side effects, and auditable state, and Laravel shipped that layer years before anyone needed it for agents.
The end-of-session summary is the least useful artifact your harness produces. Replace it with a fixed interrogation, scripted rather than remembered.
Tool allowlists and OAuth scopes secure the verb. The exposure is the noun: which rows, which columns, which tenant. Your ORM already knows how to enforce that, and almost nobody is using it.
Where the term came from, what it means, and which claims about autonomous software production have evidence behind them.