Easy rebuttals: +There is no public spec for linux -https://refspecs.linuxfoundation.org/lsb.shtml +If you want one go build one Better reason - there isnt demand for this I would like to understand what other reasons there could be
Not sure if it's still the case but if I recall correctly, the majority of the bitcoin maintainers are employed by one company... so not sure there's an incentive for them.
What is a public spec?
Writing documentation is boring, and requires the kind of rigor and focus that I haven't found to be common in the Bitcoin community.
Ponzi schemes generally don't have open specs. Defeats the purpose.
I'm thinking what would be the purpose or added value of a separate "public spec" document (which would require a significant maintenance effort) when you already have [1] a healthy Github (or Gitlab) project governance going on, [2] Bitcoin feature proposal process.
When you upgrade your Bitcoin node software, the act of the upgrading is you casting your Yes vote for the changes introduced in that version. The BIPs etc. can help you understand these, but if you want to be 100% diligent, the only fully authoritative source is the state of (the code sources in) the git repo as referenced by the commit hash in the Bitcoin software you are upgrading to.