{
  "schemaVersion": "1",
  "scope": "product-capability-catalog",
  "productionAttestation": false,
  "solutions": [
    {
      "id": "connect",
      "number": "01",
      "name": "Connect",
      "title": "Make the interfaces agree.",
      "summary": "Inspect commerce documents and find structural issues before an integration goes further.",
      "audience": "Platforms & integration teams",
      "status": "Existing diagnostic tools",
      "available": "Structural protocol diagnostics and REST / MCP integration examples.",
      "boundary": "Diagnostics are not certification. End-to-end integration and version coverage require a scoped review.",
      "deliverable": "An integration inventory, reproducible findings and a prioritized remediation list.",
      "action": "Open protocol checker",
      "href": "https://code402.dev/protocols"
    },
    {
      "id": "control",
      "number": "02",
      "name": "Control",
      "title": "Make authority explicit.",
      "summary": "Understand who can request an action, which limits apply and where a decision is enforced.",
      "audience": "Automation & agent teams",
      "status": "Scoped integration review",
      "available": "Existing policy and receipt components provide a starting point for integration review.",
      "boundary": "The existing spending gate is advisory to its caller. It cannot stop a wallet or service that bypasses it.",
      "deliverable": "A map of the authorization boundary, policy requirements and bypass tests for your workflow.",
      "action": "Discuss your workflow",
      "href": "https://code402.dev/contact?interest=control"
    },
    {
      "id": "reconcile",
      "number": "03",
      "name": "Reconcile",
      "title": "Find where the records disagree.",
      "summary": "Compare order, payment and delivery records. See mismatches and missing evidence separately.",
      "audience": "Marketplaces & finance operations",
      "status": "Runnable demonstration",
      "available": "A deterministic comparison of supplied purchase records through a stateless JSON API, a local CLI and examples you can inspect.",
      "boundary": "The demonstration checks supplied data. It does not independently confirm settlement or delivery. Refund matching is not included.",
      "deliverable": "A bounded exception report with source references, missing evidence and explicit limitations.",
      "action": "Inspect an example",
      "href": "/workbench?scenario=recipient"
    },
    {
      "id": "evidence",
      "number": "04",
      "name": "Evidence",
      "title": "Keep the reason with the result.",
      "summary": "Inspect signed check results and preserve the context needed to understand them.",
      "audience": "Operations & technical reviewers",
      "status": "Existing receipt verification",
      "available": "Public receipt verification and signed results from supported checks.",
      "boundary": "A signature establishes integrity under its trust model, not the truth of the underlying business assertion. Managed AP2 evidence retrieval is a proposed integration.",
      "deliverable": "A verification result and an evidence inventory for a clearly defined transaction flow.",
      "action": "Verify a receipt",
      "href": "https://code402.dev/verify"
    }
  ],
  "protocols": [
    [
      "REST / files",
      "Existing business workflows"
    ],
    [
      "MCP",
      "Tools and data"
    ],
    [
      "A2A",
      "Agent tasks"
    ],
    [
      "UCP",
      "Commerce capabilities"
    ],
    [
      "AP2",
      "Purchase authority"
    ],
    [
      "x402",
      "HTTP payment flows"
    ]
  ],
  "suppliedRecordApi": {
    "method": "POST",
    "path": "/commerce/reconcile",
    "maxBodyBytes": 65536,
    "persistence": "none",
    "scope": "supplied-data-consistency-only"
  },
  "boundaries": [
    "No custody",
    "No universal protocol certification",
    "No independent delivery verification in the demo",
    "Public receipt verification remains free"
  ]
}