The idea is that the core dev team is the one with the AI harness. If someone contributes an idea they can just feed it to their AI to implement it and it probably costs 10 minutes of human time, because they trust that their harness will be able to implement the feature competently.
So, because the implementation effort is so low, the only aspect that matters if the quality of the idea. It's way easier to screen human written text than a bunch of code in a PR. If you just give them code, they would not know if you made it with a competent harness. If you gave them a AI written design they would have a lot more to read through to decide whether it's slop. If you just give them an idea it's a lot easier to determine whether it's high quality.
I'd prefer if you explain what it is you are building in the form of human-written text.
I personally would probably have the readme generated based on that directory as the primary document, probably with another `readme_generation_rules.md` in the ADRs directory, and I would be pretty ruthless about disallowing all the slop-adjacent wording.
I’d think that trying to play whack-a-mole with slop like that would result in a lengthy prompt, as well as being brittle to future changes.
If you want the prompt to be the source of truth, you’re probably going to have to accept prose that feels like AI, at least until you can regenerate with some future smarter model.
0: https://github.com/pjlsergeant/byre?tab=contributing-ov-file