{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T23:11:13.073Z",
  "record_id": "VXI-EXT-PROCUREMENT-DSSE-PAYLOAD-TYPE-SCHEMA-BINDING-01-v1",
  "record_kind": "external_reference",
  "title": "DSSE authenticated payload interpretation",
  "system": "DSSE v1.0.2",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a valid DSSE signature permit an application to interpret its payload under any JSON schema?",
  "near_questions": [
    "Does DSSE sign its payloadType as well as the payload?",
    "Can a DSSE verifier accept an unsupported payload type if the signature is valid?",
    "Why is generic application/json discouraged for DSSE evidence?",
    "Which schema should interpret authenticated DSSE bytes?"
  ],
  "supported_claims": [
    {
      "claim": "DSSE 1.0.2 signs both the payload bytes and the payload-type string through its pre-authentication encoding. The type is intended to identify encoding and meaning, with application-specific types recommended over generic application/json. Verification must reject unsupported types and parsing failures. A valid signature therefore does not justify substituting another schema or ignoring the authenticated type.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Schema correctness, claimed facts and intended business authority were not verified.",
    "No verified business outcome, complete event capture, deployment certification or authority to act.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "DSSE 1.0.2 signs both the payload bytes and the payload-type string through its pre-authentication encoding. The type is intended to identify encoding and meaning, with application-specific types recommended over generic application/json. Verification must reject unsupported types and parsing failures. A valid signature therefore does not justify substituting another schema or ignoring the authenticated type.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "DSSE v1.0.2 — protocol",
    "source_url": "https://raw.githubusercontent.com/secure-systems-lab/dsse/b531b787bb3e5f0c3e1c19cee84da1c5d569b061/protocol.md",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-DSSE-PAYLOAD-TYPE-SCHEMA-BINDING-01-v1",
    "candidate_record_sha256": "077e4719c7c5b85aa64994dbabf4809ccbe032d8881e3b0150284a7e13f54388",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "DSSE 1.0.2 signs both the payload bytes and the payload-type string through its pre-authentication encoding. The type is intended to identify encoding and meaning, with application-specific types recommended over generic application/json. Verification must reject unsupported types and parsing failures. A valid signature therefore does not justify substituting another schema or ignoring the authenticated type.",
    "required_buyer_context": "Exact authenticated payload type; Supported schema and parser version; Signature and parsing results for the retained bytes. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-24",
    "claim_to_check": "Does a valid DSSE signature permit an application to interpret its payload under any JSON schema?",
    "documented_statement": {
      "status": "documented",
      "statement": "DSSE 1.0.2 signs both the payload bytes and the payload-type string through its pre-authentication encoding. The type is intended to identify encoding and meaning, with application-specific types recommended over generic application/json. Verification must reject unsupported types and parsing failures. A valid signature therefore does not justify substituting another schema or ignoring the authenticated type.",
      "source_ids": [
        "dsse-protocol"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Bind accepted evidence meaning to the authenticated application-specific type. This is a review judgment, not an observed execution or deployment result.",
      "source_ids": [
        "dsse-protocol"
      ]
    },
    "buyer_evidence_required": [
      "Exact authenticated payload type",
      "Supported schema and parser version",
      "Signature and parsing results for the retained bytes"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse interpretation under an unsupported or substituted payload schema."
    },
    "unknowns": "Schema correctness, claimed facts and intended business authority were not verified.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Schema correctness, claimed facts and intended business authority were not verified."
    },
    "evidence_sources": [
      {
        "source_id": "dsse-protocol",
        "url": "https://raw.githubusercontent.com/secure-systems-lab/dsse/b531b787bb3e5f0c3e1c19cee84da1c5d569b061/protocol.md",
        "final_url": "https://raw.githubusercontent.com/secure-systems-lab/dsse/b531b787bb3e5f0c3e1c19cee84da1c5d569b061/protocol.md",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:53:31.659Z",
        "sha256": "6c0d965475162230f9f461acf634b4d4b409eab1a1839d31a9c24c76b3676253",
        "bytes": 6638,
        "title": "DSSE v1.0.2 — protocol",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Original bounded paraphrase; source bodies are captured privately and not redistributed. Repository Apache-2.0 licence reviewed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Signature Definition: KEYID; verification protocol",
          "PAYLOAD_TYPE; signature definition; verification rejection",
          "Verification protocol; envelope security considerations"
        ],
        "version_context": "DSSE protocol/envelope v1.0.2 (2024-05-10), pinned revision; pinned secure-systems-lab/dsse revision b531b787bb3e5f0c3e1c19cee84da1c5d569b061. Source documentation is not independent evidence of buyer deployment behaviour."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Bind accepted evidence meaning to the authenticated application-specific type.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome."
    },
    "buyer_relevance": "Bind accepted evidence meaning to the authenticated application-specific type.",
    "refusal_conditions": [
      "Refuse interpretation under an unsupported or substituted payload schema."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "audit",
    "classification_label": "Audit, Provenance & Evidence Accountability",
    "topic_id": "audit",
    "buyer_intent": "Bind accepted evidence meaning to the authenticated application-specific type.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#dsse-payload-type-schema-binding",
  "machine_readable_record": "/varexis-index/records/dsse-payload-type-schema-binding.json"
}