zeekayandHanzo Dev
7a9dcac628
An audit read the code and found the proposal that specifies it. Go reaches
all 122 capability proposals and 64 of the 121 other Standards Track ones;
Rust has 35, mostly the operator and the CLI; C++ has three, because the
complete original C++ in the estate is a ZAP handler, a bot nothing specifies,
and authored kernels inside forked CUDA and Metal crates.
| | shipped | partial | none | not assessed |
| Go | 146 | 33 | 1 | 80 |
| C++ | 1 | 2 | 0 | 257 |
| Rust | 10 | 25 | 1 | 224 |
The large "not assessed" columns are the point rather than a gap. The model and
training specs are Python, the frontend and design-system proposals are
TypeScript, and recording `none` against those would read as a search that
came up empty when the honest statement is that the runtime was never the
question. Governance, Meta and Process are not graded at all.
Six proposals are Final with nothing found in Go and are left unwritten rather
than demoted: 0065, 0089, 0098, 0103, 0521 and 0902. HIP-0521 answers itself,
its own section reading "Not yet implemented". Three of the others name a
canonical Go file in consensus/protocol/auth that nobody wrote, in a package
where the four neighbouring proposals' files all exist with tests beside them.
Co-authored-by: Hanzo Dev <[email protected]>
Implementation audit
Where each proposal's implementation-go, implementation-cpp and
implementation-rust came from. One row per verdict:
<language>:<number> <shipped|partial|none> <evidence>
The evidence is a path and line, or a symbol, that a reader can check. A verdict without its reasoning is a claim nobody can re-derive.
The audit read the code and looked for the proposal that specifies it, rather
than reading the corpus and guessing. An absent key means that runtime was
never the language for this proposal — the model and training specs are
Python, the frontend and docs HIPs are TypeScript, and saying none about
those would read as "we looked for Rust and found none" when the honest
statement is that Rust was never the question.
Held back
A proposal whose status is Final while the audit found nothing implementing
it in Go is a contradiction: Final is defined as the thing existing in the
code, and lint-hips.py FM011 refuses the pair. Those values were NOT
written, because resolving one means deciding whether the proposal is really
Final or whether the search missed the code. Six here: HIP-0065, 0089, 0098,
0103, 0521 and 0902. HIP-0521 settles itself — its own section 136 reads "Not
yet implemented."