docs(spec): resolve MEDIUM-severity normative clarifications (F1/F5/F15)#201
Merged
Conversation
Addresses three MEDIUM-severity findings from the C2 internal consistency audit (docs/audits/mcp-protocol-internal-consistency-2026-05-15.md): - F1: Overview now acknowledges inter-society as MCP's primary use case, aligning with §1.1's "load-bearing" and §7's "primary" framing - F5: §7.6 clarifies that §7.7.7 error codes refine the generic web4_cross_society_exchange_invalid code for the rate-negotiation sub-domain, with §7.6 as fallback when §7.7 is not in force - F15: §7.3 now specifies violation outcome handling — non-positive deltas, Policy-Entity-signed, Archivist-persisted — distinguishing it from §7.6 transport/protocol failures Co-Authored-By: Claude Opus 4.6 <[email protected]>
This was referenced May 17, 2026
Owner
Author
|
APPROVED: Resolves 3 MEDIUM internal-consistency findings (F1/F5/F15), continuing the #200 remediation stream. F1: Overview now acknowledges cross-society as MCP's primary use case, ending the contradiction with §1.1's 'load-bearing' and §7's 'primary' framing. F15: §7.3 specifies the |
dp-web4
added a commit
that referenced
this pull request
May 17, 2026
F14 (cross-doc section-number claims): verified all 6 references from mcp-protocol.md → inter-society-protocol.md. All correct, including bidirectional consistency of §9 future-work resolution status. No stale references found — resolved by verification. F16 (two trust-discount models in §9.1 vs §9.2): annotated §9.2 as (informative) with society-configurable parameters. §9.1 is the canonical metering formula; §9.2's high_trust_discount: 0.8 is the endpoint value at maximum trust (T3 avg = 1.0). Remaining LOW findings (F9/F10/F13) deliberately deferred to avoid merge conflicts with PRs #200/#201 that edit overlapping regions. Co-authored-by: Claude Opus 4.6 <[email protected]>
dp-web4
added a commit
that referenced
this pull request
May 18, 2026
…ipline; §7.7 promotion gate formalized Eight commits since 2026-05-17 reviewed. All are audit-remediation clean-up of two specs already on the watch list (presence-protocol + mcp-protocol §7.7); none introduce new protocol surface or warrant integration today. - C5 presence-protocol internal-consistency audit (#204) → G1 casing-authority + G3 localized staleness (#206) → G2 discipline honesty (#207). Spec now internally consistent at v1 — but consistency is the *condition* for integration, not the trigger. DEFER continues pending Hestia/Hardbound registry-published release. - mcp-protocol C2 audit remediation HIGH F2/F3/F4/F12 (#200) + MEDIUM F1/F5/F15 (#201) + LOW F14/F16 (#203). §7.7 conformance status disambiguated per-subsection; atp_settlement gains referent slot forward-compatible with §7.7.3 acceptance payload. - §7.7 promotion-tracking memo (Sprint 54 C3, #202) formalizes the integration gate: 3 hard prerequisites (one now met), 5 open design questions, 2-implementations + interop + error-catalogue evidence criteria. Pending Updates row refined to cite the memo directly rather than re-derive gate logic per maintenance pass. Live whitepaper sections verified clean of canonical-term drift (only archive files retain historical expansions, intentionally preserved per 2026-04-29 cleanup). Build artifacts remain aligned with 2026-05-16 source state (5ccbe46); no rebuild needed. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
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
1 participant
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.
Summary
Addresses three MEDIUM-severity findings from the C2 internal consistency audit (
docs/audits/mcp-protocol-internal-consistency-2026-05-15.md), continuing the remediation stream started by PR #200 (which resolved the HIGH-severity cluster).web4_cross_society_exchange_invalidcode and §7.7.7's domain-specific rate negotiation codesviolationoutcome handling — non-positive deltas, Policy-Entity-signed, Archivist-persisted — distinguishing it from §7.6 transport failuresTest plan
🤖 Generated with Claude Code