## 5. The stance

None of this is suspicion of models. I use them all day, this essay is openly model-assisted, and the compiler would be years further away without them. The rule is about which layer a model's words may land in on their own authority, and the answer is none, and the answer does not soften as the models improve. A better proposer is a better proposer. The disposition still belongs to something it does not control, or the evidence layer stops being one, and everything downstream inherits the difference without being told.

The rule does not exempt its author either, which is where it bites. Elsewhere in the same toolchain a preregistered confirmatory run is under way as I write, and I am not going to tell you how it is going, because no verdict has been computed yet, and the discipline that refuses a model's self-report refuses mine too. When there is a result it will arrive with its receipts, or it will not arrive.

What I am against is quieter than the loud fears. It is disposition migrating to the proposer, one convenience at a time, until the record is a transcript of what the most fluent party said about itself. Every mechanism in this essay is a way of keeping the no alive somewhere the proposer cannot reach it. The four words are just that, compressed. Models propose. Oracles dispose. And somebody who is neither should be able to check both, which is why the receipts are public.

## Process note

This essay was drafted with model assistance at my direction and edited and signed by me, as its own rule requires me to disclose. The technical claims describe public work, principally the compiler at [github.com/HarperZ9/buildlang](https://github.com/HarperZ9/buildlang); the demonstration in section 4 lives on an in-review branch, as the essay says. Where a sentence reaches past what the record supports, it is argument, and it should read as argument or it is a defect.