{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T23:11:13.073Z",
  "record_id": "VXI-EXT-PROCUREMENT-DSSE-VERIFIED-BYTES-APPLICATION-HANDOFF-01-v1",
  "record_kind": "external_reference",
  "title": "DSSE verified bytes and application use",
  "system": "DSSE v1.0.2",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a DSSE verifier reparse the original envelope after verification to obtain the application payload?",
  "near_questions": [
    "Must a DSSE application use the same bytes that passed signature verification?",
    "Why must a DSSE envelope not be reparsed after verification?",
    "Can a signature over one decoded payload authenticate a later parse?",
    "What evidence binds verified DSSE bytes to application processing?"
  ],
  "supported_claims": [
    {
      "claim": "DSSE 1.0.2 requires the exact payload bytes verified to be the bytes passed to the application layer and explicitly forbids reparsing the envelope afterwards to retrieve the payload. A signature result over one decoded value cannot justify acting on another value obtained by a later parse. Evidence handoff therefore needs a stable binding between verification output and application input.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "No application implementation or parser differential was tested.",
    "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 requires the exact payload bytes verified to be the bytes passed to the application layer and explicitly forbids reparsing the envelope afterwards to retrieve the payload. A signature result over one decoded value cannot justify acting on another value obtained by a later parse. Evidence handoff therefore needs a stable binding between verification output and application input.",
  "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-VERIFIED-BYTES-APPLICATION-HANDOFF-01-v1",
    "candidate_record_sha256": "099ee32d0ccf2f53799119454904ea2ec5fcfe1d6d8e83ecceebba77c77071ed",
    "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 requires the exact payload bytes verified to be the bytes passed to the application layer and explicitly forbids reparsing the envelope afterwards to retrieve the payload. A signature result over one decoded value cannot justify acting on another value obtained by a later parse. Evidence handoff therefore needs a stable binding between verification output and application input.",
    "required_buyer_context": "Decoded payload bytes retained at verification; Signature result and supported payload type; Application input binding and parsing path. 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": "Can a DSSE verifier reparse the original envelope after verification to obtain the application payload?",
    "documented_statement": {
      "status": "documented",
      "statement": "DSSE 1.0.2 requires the exact payload bytes verified to be the bytes passed to the application layer and explicitly forbids reparsing the envelope afterwards to retrieve the payload. A signature result over one decoded value cannot justify acting on another value obtained by a later parse. Evidence handoff therefore needs a stable binding between verification output and application input.",
      "source_ids": [
        "dsse-protocol",
        "dsse-envelope"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Preserve the verified payload through the application handoff. This is a review judgment, not an observed execution or deployment result.",
      "source_ids": [
        "dsse-protocol",
        "dsse-envelope"
      ]
    },
    "buyer_evidence_required": [
      "Decoded payload bytes retained at verification",
      "Signature result and supported payload type",
      "Application input binding and parsing path"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse authenticated-payload claims when the application consumes a separately reparsed value."
    },
    "unknowns": "No application implementation or parser differential was tested.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No application implementation or parser differential was tested."
    },
    "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."
      },
      {
        "source_id": "dsse-envelope",
        "url": "https://raw.githubusercontent.com/secure-systems-lab/dsse/b531b787bb3e5f0c3e1c19cee84da1c5d569b061/envelope.md",
        "final_url": "https://raw.githubusercontent.com/secure-systems-lab/dsse/b531b787bb3e5f0c3e1c19cee84da1c5d569b061/envelope.md",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:53:31.862Z",
        "sha256": "3a8e7370671354cf3d3417c818a44dcda02cbc57dce6f4b6a75a84c41c483074",
        "bytes": 2632,
        "title": "DSSE v1.0.2 — envelope",
        "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": [
          "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": "Preserve the verified payload through the application handoff.",
      "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": "Preserve the verified payload through the application handoff.",
    "refusal_conditions": [
      "Refuse authenticated-payload claims when the application consumes a separately reparsed value."
    ]
  },
  "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": "Preserve the verified payload through the application handoff.",
    "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-verified-bytes-application-handoff",
  "machine_readable_record": "/varexis-index/records/dsse-verified-bytes-application-handoff.json"
}