Governed MCP retrieval and release-flow guide

Synthetic worked example

Refuse stale releases and substituted selectors

What stops a licensed request from returning a different record?

Selector, request digest, active release, and execution reservation remain bound; changing any one creates a conflict rather than a convenient fallback.

Starting inputs

An original selector

Its request digest

An idempotency key

A stale or substituted retry

Ordered execution

Work the example

  1. 1

    Canonicalize the original tool arguments.

  2. 2

    Bind the request digest to the reservation.

  3. 3

    Resolve the selector against active releases.

  4. 4

    Compare every retry with the original material request.

  5. 5

    Refuse substitution, staleness, or withdrawal.

Expected outputs

  • A selector-conflict refusal
  • No replacement record
  • No quota charge for rejected substitution

Verification checks

  • Exactly one selector is accepted.
  • A material retry changes request identity.
  • No evidence bytes are returned on refusal.

Fail closed

Refusal conditions

  • A path silently falls back to another release.
  • A stale target is returned because quota remains.
  • A changed request reuses the prior execution.

Digest-bound public fixture

Check the expected state

This fixture contains synthetic operational fields only. Its digest establishes fixture integrity, not scientific truth or a completed commercial transaction.

{
  "artifactKind": "licensed-delivery",
  "schemaVersion": "maha-licensed-evidence/1.0",
  "input": {
    "originalSelector": "release-A",
    "retrySelector": "release-B",
    "sameIdempotencyKey": true
  },
  "expected": {
    "outcome": "idempotency-conflict",
    "deliveredRecord": null
  },
  "artifactSha256": "sha256:d41b6568a751e50c0c26e2910db5951db912a218476c61c99b1dd085baf2c079"
}