Skip to content

docs(spec): resolve HIGH-severity §7.4↔§7.7 internal consistency (F2/F3/F4/F12)#200

Merged
dp-web4 merged 1 commit into
mainfrom
worker/web4-20260516-060003
May 17, 2026
Merged

docs(spec): resolve HIGH-severity §7.4↔§7.7 internal consistency (F2/F3/F4/F12)#200
dp-web4 merged 1 commit into
mainfrom
worker/web4-20260516-060003

Conversation

@dp-web4
Copy link
Copy Markdown
Owner

@dp-web4 dp-web4 commented May 16, 2026

Summary

Resolves 4 of the 5 HIGH-severity findings from the mcp-protocol.md internal-consistency audit (PR #192). These defects made it impossible for a conformant implementation to satisfy §7.4 without depending on the explicitly non-dependable §7.7 WIP section.

  • F2: atp_settlement.exchange_rate MUST depended on non-dependable §7.7 → replaced with conditional MUST on block presence + interim conformance note gating internal structure stability on §7.7 finalization
  • F3: §7.4 example used scalar bilateral model ({denominator, rate}) that §7.7.1 explicitly rejects → replaced with referent-grounded schema (dual amounts + referent object)
  • F4: atp_settlement had no referent slot → now carries caller_currency, responder_currency, caller_amount, responder_amount, referent, and exchange_agreement_ref — forward-compatible with §7.7.3 acceptance payload
  • F12: §7.7 subsection conformance status undeterminable → added per-subsection markers distinguishing Normative (§7.7.1, §7.7.4), Normative-draft (§7.7.2, §7.7.3, §7.7.7), and Informative (§7.7.5, §7.7.6)

F8 was already resolved by operator commit 2e1e8b11 (§7.4↔§4.1 wire-field redefinition). This PR continues that spec-fix stream.

Scope discipline

  • 1 file modified (web4-standard/core-spec/mcp-protocol.md)
  • 0 new files
  • No SDK code changes, no test changes, no version bump
  • Pure spec refinement — resolves internal contradictions for implementers

Test plan

  • Verify §7.4 example JSON is well-formed and consistent with §7.7.3 acceptance schema
  • Verify §7.4 normative text no longer contains unconditional MUST on §7.7-dependent fields
  • Verify §7.7 subsection status markers are complete (all 7 subsections classified)
  • Verify §7.7 intro paragraph references updated §7.4 schema correctly

🤖 Generated with Claude Code

…F3/F4/F12)

Addresses 4 HIGH findings from the mcp-protocol.md internal-consistency audit
(merged as PR #192, docs/audits/mcp-protocol-internal-consistency-2026-05-15.md):

F2: §7.4 MUST for exchange_rate depended on non-dependable §7.7. Replaced with
    conditional MUST on atp_settlement presence + interim conformance note.
F3: §7.4 example used scalar bilateral model §7.7.1 explicitly rejects. Replaced
    with referent-grounded schema (dual amounts + referent + agreement ref).
F4: atp_settlement lacked referent slot. Now carries caller/responder currencies,
    amounts, referent object, and exchange_agreement_ref — forward-compatible with
    §7.7.3 acceptance payload.
F12: §7.7 conformance status undeterminable. Added per-subsection markers:
     §7.7.1/§7.7.4 Normative, §7.7.2/§7.7.3/§7.7.7 Normative-draft,
     §7.7.5/§7.7.6 Informative.

Continues the spec-fix stream from operator commit 2e1e8b1 (F8 resolution).

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@dp-web4
Copy link
Copy Markdown
Owner Author

dp-web4 commented May 17, 2026

APPROVED: Resolves 4 HIGH-severity internal-consistency defects (F2/F3/F4/F12) in mcp-protocol.md §7.4↔§7.7. Before this, a conformant implementation literally could not satisfy §7.4's atp_settlement.exchange_rate MUST without depending on §7.7, which the spec explicitly marks non-dependable WIP — a genuine spec contradiction blocking implementers. The fix is well-scoped: F2 converts the unconditional MUST to a conditional MUST-on-presence with an interim conformance note gating internal structure on §7.7 finalization; F3 replaces the scalar bilateral example (which §7.7.1 rejects) with the referent-grounded schema; F4 gives atp_settlement a referent slot forward-compatible with §7.7.3; F12 adds per-subsection conformance markers (Normative / Normative-draft / Informative). +27 -6, 1 file, pure spec refinement, diff matches description, no drift. This is the base of the remediation stream (#201/#203 build on it) so it merges first.

@dp-web4 dp-web4 merged commit 854df2c into main May 17, 2026
@dp-web4 dp-web4 deleted the worker/web4-20260516-060003 branch May 17, 2026 20:11
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 17, 2026
Captures what must be true to promote §7.7 (Referent-Grounded Exchange
Rate Negotiation) from v0.1.0-draft to v0.1.0-normative:

- 3 hard prerequisites (PR #200 merge, F11 signing authority, F8 verify)
- 5 open design questions requiring operator decisions
- Implementation evidence criteria (2 implementations, interop, errors)
- Actionable gate-checklist for promotion decision

The memo identifies the "two implementations" requirement as the real
long-pole and recommends following the presence-protocol discipline
pattern (spec + schemas + conformance vectors as atomic unit).

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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant