{
  "schema": "varexis-index-free-publication-preview/1",
  "catalogue_version": "pub-9-tranche-59-v1",
  "route_id": "agentic_reviewed_http_digest_content_representation_scope",
  "record_id": "VXI-EXT-PROCUREMENT-HTTP-DIGEST-CONTENT-REPRESENTATION-SCOPE-01-v1",
  "question": "Does a Repr-Digest on an HTTP range or HEAD response prove that all representation bytes were delivered?",
  "answer": "RFC 9530 defines Content-Digest over actual message content and Repr-Digest over the entire selected representation. HTTP methods and ranges can make those scopes differ, including partial responses and HEAD. A representation digest therefore does not establish that the complete representation was delivered in this message; inventory the bytes and semantics actually received.",
  "records": [
    {
      "record_id": "VXI-EXT-PROCUREMENT-HTTP-DIGEST-CONTENT-REPRESENTATION-SCOPE-01-v1",
      "url": "/varexis-index/records/http-digest-content-representation-scope.json",
      "content_sha256": "fc725a9aba02b9b83d56d3bb8e5efadae5ebe7d3b897a7c8e9dec9af2b3e6878",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-10-25T20:55:19.974986+00:00",
        "record_id": "VXI-EXT-PROCUREMENT-HTTP-DIGEST-CONTENT-REPRESENTATION-SCOPE-01-v1",
        "record_kind": "external_reference",
        "title": "HTTP content and representation digest scope",
        "system": "IETF RFC 9530",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Does a Repr-Digest on an HTTP range or HEAD response prove that all representation bytes were delivered?",
        "near_questions": [
          "Can a partial HTTP response carry a digest of the full representation?",
          "Do Content-Digest and Repr-Digest always hash the same bytes?",
          "Does a HEAD representation digest prove body delivery?",
          "Which digest scope should a downloaded range be checked against?"
        ],
        "supported_claims": [
          {
            "claim": "RFC 9530 defines Content-Digest over actual message content and Repr-Digest over the entire selected representation. HTTP methods and ranges can make those scopes differ, including partial responses and HEAD. A representation digest therefore does not establish that the complete representation was delivered in this message; inventory the bytes and semantics actually received.",
            "reliance": "DOCUMENTED_CAPABILITY_ONLY"
          }
        ],
        "not_demonstrated_claims": [
          "Content and selected representation are distinct byte scopes; digest presence does not prove full content was delivered.",
          "Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.",
          "No expanded capabilities or licences for existing INDEX executables."
        ],
        "public_summary": "RFC 9530 defines Content-Digest over actual message content and Repr-Digest over the entire selected representation. HTTP methods and ranges can make those scopes differ, including partial responses and HEAD. A representation digest therefore does not establish that the complete representation was delivered in this message; inventory the bytes and semantics actually received.",
        "related_record_ids": [],
        "source_review": {
          "source_type": "official_external_documentation",
          "source_title": "IETF RFC 9530",
          "source_url": "https://www.rfc-editor.org/rfc/rfc9530.txt",
          "checked_on": "2026-10-25",
          "candidate_record_id": "VXI-EXT-PROCUREMENT-HTTP-DIGEST-CONTENT-REPRESENTATION-SCOPE-01-v1",
          "candidate_record_sha256": "8c7094fac6c370d9588f50a3c491962c90349b07dd1060a5a16e8e79d68d3b5b",
          "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": "RFC 9530 defines Content-Digest over actual message content and Repr-Digest over the entire selected representation. HTTP methods and ranges can make those scopes differ, including partial responses and HEAD. A representation digest therefore does not establish that the complete representation was delivered in this message; inventory the bytes and semantics actually received.",
          "required_buyer_context": "HTTP method, status and range; Selected representation metadata; Actual content bytes and digest type. 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-25",
          "claim_to_check": "Does a Repr-Digest on an HTTP range or HEAD response prove that all representation bytes were delivered?",
          "documented_statement": {
            "status": "documented",
            "statement": "RFC 9530 defines Content-Digest over actual message content and Repr-Digest over the entire selected representation. HTTP methods and ranges can make those scopes differ, including partial responses and HEAD. A representation digest therefore does not establish that the complete representation was delivered in this message; inventory the bytes and semantics actually received.",
            "source_ids": [
              "rfc9530"
            ]
          },
          "review_inference": {
            "status": "review_inference",
            "statement": "Select Content-Digest versus Repr-Digest for a partial or HEAD evidence response. This is a documentation-review judgment, not an observed deployment outcome.",
            "source_ids": [
              "rfc9530"
            ]
          },
          "buyer_evidence_required": [
            "HTTP method, status and range",
            "Selected representation metadata",
            "Actual content bytes and digest type"
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Refuse buyer-specific assurance from documentation alone. Content and selected representation are distinct byte scopes; digest presence does not prove full content was delivered."
          },
          "unknowns": "The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.",
          "unknown_finding": {
            "status": "unknown",
            "statement": "The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected."
          },
          "evidence_sources": [
            {
              "source_id": "rfc9530",
              "url": "https://www.rfc-editor.org/rfc/rfc9530.txt",
              "final_url": "https://www.rfc-editor.org/rfc/rfc9530.txt",
              "status": 200,
              "captured_at_utc": "2026-10-25T20:26:12.731Z",
              "sha256": "544dbb7d9afceafa8c9931d9924ca6cff2b4807274166d7ed2483342ef2cdd6a",
              "bytes": 67152,
              "title": "IETF RFC 9530",
              "hash_basis": "SHA-256 of unmodified HTTP response body bytes",
              "rights_review": "Original factual paraphrase of the cited IETF RFC; IETF Trust and contributor rights remain applicable. No RFC text, code component or modified standard is redistributed.",
              "checked_on": "2026-10-25",
              "capture_status": 200,
              "claim_review_completed": true,
              "reviewed_sections": [
                "2",
                "3",
                "3.1",
                "4"
              ],
              "version_context": "Fixed IETF RFC 9530 publication; later applicable updates and actual implementation conformance require separate review."
            }
          ],
          "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": "Select Content-Digest versus Repr-Digest for a partial or HEAD evidence response.",
            "free": "Complete review, practical questions, sources 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 2; 3 in IETF RFC 9530 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval."
          },
          "buyer_relevance": "Select Content-Digest versus Repr-Digest for a partial or HEAD evidence response.",
          "refusal_conditions": [
            "Refuse buyer-specific assurance from documentation alone. Content and selected representation are distinct byte scopes; digest presence does not prove full content was delivered."
          ]
        },
        "niche": {
          "niche_id": "enterprise-ai-data-custody-exit-assurance",
          "label": "Enterprise AI Data Custody & Exit Assurance",
          "classification_id": "custody",
          "classification_label": "AI Data Custody, Retention & Exit Assurance",
          "topic_id": "custody",
          "buyer_intent": "Select Content-Digest versus Repr-Digest for a partial or HEAD evidence response.",
          "comparison_role": "matched_custody_addition"
        },
        "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#http-digest-content-representation-scope",
        "machine_readable_record": "/varexis-index/records/http-digest-content-representation-scope.json"
      }
    }
  ],
  "access": {
    "mode": "exact_http_only",
    "payment_required": false,
    "purchase_url": null,
    "mcp_preview_available": false,
    "paid_saved_retrieval_available": false,
    "natural_language_search_qualified": false
  },
  "boundary": "Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.",
  "content_sha256": "a0b8bae88ef87edf984f77bf79d659ea9255c06f93c43abb42a0497f5befe4b6"
}