Tech
Require a Job Receipt. Apply Nothing the Schema Cannot Parse.
A free remote model can draft a patch. It cannot be the process that mutates my tree. I treat every remote run as a proposal. The proposal is a job receipt. If the receipt fails the schema, the job is over.
No debate. No "just apply it this once."
Unconstrained generation is easy to confuse with engineering. This week's feed is full of that argument. Models write code. That part is boring. The part that still fails is inspection. I want a gate I can run in CI. A receipt is that gate.
...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to