lol yes, agents ran the mechanics. I set the bars before any run and audited the keys. And the "why" behind the project is literally in the repo's .ai/why/ where you grep it if you would like.
The repo's .ai/why/ does not contain the "why" behind the project. It provides a list of dozens of small decisions the agent presumably made as part of implementation; none of them explain what a "why-pack" is, or describe their underlying structure and principles, or detail the thought process behind the decision that "why-packs" are the best strategy to achieve the project's goals.
I would encourage you to treat AI outputs with substantially more skepticism than you're giving them.
Comments
lol yes, agents ran the mechanics. I set the bars before any run and audited the keys. And the "why" behind the project is literally in the repo's .ai/why/ where you grep it if you would like.
The repo's .ai/why/ does not contain the "why" behind the project. It provides a list of dozens of small decisions the agent presumably made as part of implementation; none of them explain what a "why-pack" is, or describe their underlying structure and principles, or detail the thought process behind the decision that "why-packs" are the best strategy to achieve the project's goals.
I would encourage you to treat AI outputs with substantially more skepticism than you're giving them.