Governed MCP retrieval and release-flow guide

Synthetic worked example

Acknowledge a digest-bound evidence delivery

What must a delivery receipt bind before acknowledgement?

The receipt joins execution, request, projection, release, record revision, canonical path, and substantial publication into one independently checkable identity.

Starting inputs

A licensed evidence projection

An eligible substantial page

Exact release and revision digests

A private delivery channel

Ordered execution

Work the example

  1. 1

    Bind the execution and projection digests.

  2. 2

    Match release target to the substantial-page revision.

  3. 3

    Require complete claim coverage and zero unsupported paragraphs.

  4. 4

    Compute the delivery-receipt digest.

  5. 5

    Acknowledge that exact receipt once.

Expected outputs

  • A private machine-delivery receipt
  • acknowledgementRequired set true
  • A replay-safe acknowledgement identity

Verification checks

  • Receipt reconstruction is byte-identical.
  • The receipt says entitlementChangesEvidenceQuality false.
  • Acknowledgement cannot target a substituted digest.

Fail closed

Refusal conditions

  • The page names another revision.
  • Delivery is unavailable.
  • An acknowledgement is accepted before delivery.

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-substantial-mcp-receipt/0.1",
  "input": {
    "execution": "bound",
    "release": "exact-active",
    "publication": "eligible-exact-revision"
  },
  "expected": {
    "deliveryState": "private-machine-delivery",
    "acknowledgementRequired": true,
    "entitlementChangesEvidenceQuality": false
  },
  "artifactSha256": "sha256:97d629225eba355a439b1c18072157d988a86007cdd0fb423c08fc1aaaafaeba"
}