From 37f0030f36819483684cc0912b121d0cd857d366 Mon Sep 17 00:00:00 2001 From: Codex Assistant Date: Thu, 27 Aug 2026 23:20:45 -0400 Subject: [PATCH] fix(mcp-res): publish v0.2 Pages landing copy --- docs/standards/mcp-res/README.md | 29 ++++++------ docs/standards/mcp-res/index.html | 74 ++++++++++++++++++------------- 2 files changed, 57 insertions(+), 46 deletions(-) diff --git a/docs/standards/mcp-res/README.md b/docs/standards/mcp-res/README.md index 4486900..c803617 100644 --- a/docs/standards/mcp-res/README.md +++ b/docs/standards/mcp-res/README.md @@ -2,22 +2,23 @@ MCP-RES is a project-defined, vendor-neutral, open reliability-evidence standard for MCP ecosystem participants. ResiliReplay is its initial reference implementation. It is not the MCP specification, an official certification program, or an endorsement by the MCP project. -Draft v0.2.0 is now a prerelease candidate after five sequential review themes. Its [candidate tree](v0.2.0/) includes false-green-resistant evidence semantics, authenticity, a Python validator, deterministic migration, official-conformance attachment, protocol/transport/authorization/operational profiles, a public field corpus, registry, and governance controls. It is not stable or official MCP status; the published v0.1 tree and claims remain unchanged. +Draft v0.2.0 is published as a prerelease after five sequential review themes. Its [version tree](v0.2.0/) includes false-green-resistant evidence semantics, authenticity, a Python validator, deterministic migration, official-conformance attachment, protocol/transport/authorization/operational profiles, a public field corpus, registry, and governance controls. It is not stable or official MCP status; the published v0.1 tree and claims remain unchanged. -The current publication is **Draft v0.1.0**. It defines a small implementation-neutral core, versioned profiles, strict JSON Schema 2020-12 records, valid and invalid vectors, and a black-box validator. “Normative” in this tree means normative only for this project-defined draft. +The current publication is **Draft v0.2.0 prerelease 1**. “Normative” in this tree means normative only for this project-defined draft. -Draft v0.2.0 is under sequential review and is not yet a published release. Its [development tree](v0.2.0/) currently contains merged PR 1 evidence semantics plus the PR 2 authenticity/validation/migration work, [research ledger](v0.2.0/RESEARCH.md), and [master gap ledger](v0.2.0/GAP_LEDGER.md). The published v0.1 tree and its claims remain unchanged. - -- [Draft specification](v0.1.0/MCP_RES.md) -- [Conformance requirements](v0.1.0/CONFORMANCE.md) -- [Schemas](v0.1.0/schemas/) -- [Profiles](v0.1.0/profiles/) -- [Black-box conformance kit](v0.1.0/conformance-kit/) -- [Research and source-status ledger](v0.1.0/RESEARCH.md) -- [Adversarial self-review](v0.1.0/ADVERSARIAL_REVIEW.md) +- [Draft v0.2 specification](v0.2.0/MCP_RES.md) +- [v0.2 schemas](v0.2.0/schemas/) +- [Profile registry](v0.2.0/PROFILE_REGISTRY.json) +- [Black-box conformance kit](v0.2.0/conformance-kit/) +- [Implementer kit](v0.2.0/IMPLEMENTER_KIT.md) +- [Research and source-status ledger](v0.2.0/RESEARCH.md) +- [Master gap ledger](v0.2.0/GAP_LEDGER.md) +- [Migration from v0.1](v0.2.0/MIGRATION.md) +- [Draft prerelease](https://github.com/aliengineering-byte/resilireplay/releases/tag/mcp-res-v0.2.0-draft.1) +- [RFC Discussion](https://github.com/aliengineering-byte/resilireplay/discussions/49) - [Governance](GOVERNANCE.md) - [Status and 1.0 criteria](STATUS.md) -- [Five-minute example](v0.1.0/FIVE_MINUTES.md) -- [v0.2 implementer kit](v0.2.0/IMPLEMENTER_KIT.md) -No central certification authority exists in v0.1. A conformance result is reproducible, profile-specific evidence—not a claim that the subject is secure, always available, or approved by MCP maintainers. +Historical Draft v0.1.0 remains available through its immutable [specification](v0.1.0/MCP_RES.md), [schemas](v0.1.0/schemas/), [profiles](v0.1.0/profiles/), [conformance kit](v0.1.0/conformance-kit/), and [tag](https://github.com/aliengineering-byte/resilireplay/releases/tag/mcp-res-v0.1.0-draft.1). + +No central certification authority exists. A conformance result is reproducible, profile-specific evidence—not a claim that the subject is secure, always available, or approved by MCP maintainers. diff --git a/docs/standards/mcp-res/index.html b/docs/standards/mcp-res/index.html index d36ff00..2cc5ea1 100644 --- a/docs/standards/mcp-res/index.html +++ b/docs/standards/mcp-res/index.html @@ -3,7 +3,7 @@ - MCP-RES Draft v0.1.0 — reliability evidence for MCP + MCP-RES Draft v0.2.0 — reliability evidence for MCP - + - +
-

Project draft · v0.1.0 · executable

+

Project draft · v0.2.0 · prerelease

Reliability claims.
Bound to evidence.

MCP-RES defines a portable way to show the exact subject, clean control, deterministic - fault, bounded recovery, expected failure, privacy boundary, integrity, and cleanup - behind an MCP reliability claim. + fault, reason-bound negative control, observation coverage, bounded recovery, + authenticity boundary, and cleanup behind an MCP reliability claim.

Validate in five minutes - Read the draft + Read the v0.2 draft + Get the prerelease
@@ -122,9 +127,9 @@

Any MCP ecosystem participant.

Initial profiles

    -
  • server-tool-call/v1 — normative within this project draft
    • -
  • client-config-source/v1 — provisional
    • -
  • agent-tool-recovery/v1 — provisional
    • +
  • 8 provisional protocol, async, transport, OAuth, and operational profiles
    • +
  • 4 experimental identity-extension profiles
    • +
  • Every profile binds schema/vector digests and lifecycle status

A subject is never simply “MCP-RES compliant.” Every result names a profile/version, @@ -140,12 +145,12 @@

Validate safe bundled evidence.

pnpm install --frozen-lockfile
-node docs/standards/mcp-res/v0.1.0/conformance-kit/validate.mjs docs/standards/mcp-res/v0.1.0/examples/hand-authored-valid.json
+node docs/standards/mcp-res/v0.2.0/conformance-kit/validate.mjs docs/standards/mcp-res/v0.2.0/test-vectors/valid/reason-bound-negative.json
 pnpm mcp-res:validate
- Exact output → - Vector catalog → + Implementer guide → + Vector catalog →
@@ -160,17 +165,17 @@

Schemas, vectors, bundle. Nothing private.

- Bundle schemaClosed portable recordEvidence schemaObservation-bound portable record - Vector hashesExact published bytes - Independent validatorNo ResiliReplay package importPython validatorNo JavaScript or ResiliReplay import - Field evidenceTwo pinned local stdio subjectsField evidenceFour pinned local subject artifacts
@@ -183,8 +188,8 @@

Why ResiliReplay is only first.

ResiliReplay maps completed runs through a boundary exporter. The standard schemas and black-box validator require none of its campaign, trace, agent, or reporter internals. A - second implementation should be able to produce the same portable records from its own - engine. + Python validator uses only public specification inputs. It is a second implementation, + but same-project authorship means it is not external independence.

Testing a public package does not make that package an adopter.

@@ -205,13 +210,18 @@

Evidence before stability.

Governance Draft status - Source ledger + Source ledger + RFC Discussion