Which artifact is actually the design
When several artifacts describe one screen, only the highest-fidelity one is read by codegen. Editing a lower tier looks like a change and reaches nothing.
ai
46 posts
The running app and the spec disagree, and only one is documented
Hand-editing generated source creates a divergence from the spec that nothing reports and the next regeneration silently erases. The fix belongs upstream.
Print the list before you touch anything
A batch ceiling refuses work without telling you how much exists. Enumerating first turns an unknown amount of work into a finite list you can decide about.
The orchestrator that wrote the code itself
When the coordinator writes a layer instead of dispatching its generator, the conventions the generator carries are gone and the output still compiles.
Editing the generated thing is how the spec stops meaning anything
A change implemented directly in source skips the spec, so every report downstream is computed without it. The feature works and nothing can see it.
Every generated file should say what made it
A generated artifact carries no record of how it was made once the process ends. A provenance sidecar makes which-path-produced-this answerable by grep.
It returned an identifier and produced nothing
An exhausted quota returned a success with a session id and no artifact, and the message pointed at the prompt. The misdirection cost more than the outage.
Three hundred and three of three hundred and four
A mandatory generation step had produced its fallback on 303 of 304 artifacts, for weeks, because the flag that selected the real path crashed on any real file.
The audit was green, specific, and about the wrong artifact
An audit passed on 113 pages while the source directory held 145, because it inspected a stale build. A correct check on the wrong artifact reports confidently.
Never attempted, and the summary said complete
A missing trailing newline dropped the last entry from a loop. Nothing failed, the summary matched what ran, and one item was never attempted.
A warning is not a refusal, and the driver could not tell
A driver keyed on the word ok halted a batch of 49 at item 19, because the check reported a warning rather than a failure. Gate on the blocking count.
Name the fault, and rule out the wrong fix
An error that describes the request sends you to change the request. A good message names the real condition and closes off the plausible wrong repair.