Diagnostic allocation audit limits
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.
This records observations supporting the existing open namespace decision in
DIAGNOSTIC_NAMESPACE_PROPOSAL.md.
No production gate, diagnostic code, allocation, or normative source changed.
The current audit exits zero with five metadata interval overlaps and seven
entries outside its single Lean range field. The six controls in
tools/proposals/probe_diagnostic_allocations.py (repository access required)
reproduce an ordinary metadata match, exact duplicate rejection, an authored
delegation, an authored secondary allocation, an uncompared ownership conflict,
and an owner absent from the central table. The table comparison prints review
candidates and does not infer normative allocation violations from catalog
placement.
The proposed registry schema compiles to proposed-registry.desc. Compilation
checks only protobuf syntax and descriptor generation. It does not adopt the
registry, authorize an allocation, or establish a public contract.
evidence.textproto uses
proto/validation_evidence.proto (repository access required)
to bind the source commit, relevant source bytes, terminal command exits,
logs, and generated descriptor. Its expected zero exits reproduce observations;
they are not allocation conformance passes. The previous
release report (repository access required)
already blocks normative release on unresolved diagnostic ownership.