fix(spec): resolve 5 autonomous-actionable C30 findings in errors.md#269
Merged
Conversation
C30 remediation turn (audit PR #268). Applies the 5 AUTONOMOUS findings plus the opportunistic I1 banner, all inside core-spec/errors.md: - A-M1: align worked-example titles to the §2 normative taxonomy (§1 "Binding Failed"→"Binding Already Exists"; §3.1 "Unauthorized"→ "Authorization Denied") and make the §3.1 example a coherent *denied* (not scope) case via its detail. Kept code/status W4_ERR_AUTHZ_DENIED/401 to preserve consistency with the pinned conformance vector + SDK test (BC#5 sweep finding — audit option (b) over option (a)). - A-M2: restate `type` as OPTIONAL (default about:blank) per RFC 9457 §3.1 (matches SDK .get default); label `code` a Web4 extension member (RFC 9457 §3.2); state Web4 deliberately mandates `status`/`title`. - A-M3: note `status` is HTTP-modelled but transport-agnostic (CBOR/QUIC, BLE GATT, CAN per core-protocol §5.1). - A-L1: note `instance` path segments are illustrative, no normative registry. - B-M1 §1 rescope: errors.md = the *core protocol* error taxonomy; SAL/ACP/metering/MCP subsystem specs extend it (autonomous half only; centralize-vs-distribute architecture deferred as DESIGN-Q). - I1: add Version/Status/Last-Updated banner. DESIGN-Q (B-H1 registry canonicity, B-M1 architecture, B-M3 W4IDp form) and CROSS-TRACK (B-M2 web4:// SSOT, metering name reconcile, I2) deferred. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Owner
Author
|
APPROVED: C30 remediation of core-spec/errors.md, 1 file (+18/−10), no drift. Aligns the worked-example titles to the §2 normative taxonomy (Binding Already Exists, Authorization Denied), correctly relaxes |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
C30 Remediation —
core-spec/errors.mdREMEDIATION turn (by alternation) for the C30 audit (PR #268, MERGED). Applies the 5 AUTONOMOUS-actionable findings plus the opportunistic I1 banner, all inside
web4-standard/core-spec/errors.md. 1 file changed, +18/−10. No design decisions taken; no other files touched.Findings applied
titles to the §2 normative taxonomy (§1 "Binding Failed"→"Binding Already Exists"; §3.1 "Unauthorized"→"Authorization Denied") and make §3.1 a coherent denied (not scope) case via itsdetailtype→ OPTIONAL (defaultabout:blank, RFC 9457 §3.1, matches SDK);codelabelled a Web4 extension member (§3.2); Web4 deliberately mandatesstatus/titlestatusis HTTP-modelled but transport-agnostic (CBOR/QUIC, BLE GATT, CAN per core-protocol §5.1)instancepath segments are illustrative; no normative path registryKey discipline note (BC#5 corpus sweep)
The mandated pre-finalization sweep found the conformance vector
test-vectors/errors/error-taxonomy.json(authz_denied_with_detail, labelled "spec §3.1 example") andtest_errors.pypin the §3.1 example toW4_ERR_AUTHZ_DENIED/401/"Authorization Denied". The audit's A-M1 option (a) (switch toAUTHZ_SCOPE/403) would have broken that vector + required a coordinated SDK edit (out of bounds). Took the audit's equally-sanctioned option (b) instead — fix title + make thedetaila genuine capability-denial, preserving code/status. Net effect: improves spec↔vector consistency. All four examples now match their §2 taxonomy titles.Deferred (per audit routing)
web4://SSOT mirroring in data-formats; metering parallel-name reconcile; I2 QUICK_REFERENCE type-URI. NEW:web4-handshake.md:218carries the same "Unauthorized" title mismatch (recorded for handshake re-audit).🤖 Generated with Claude Code