{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T23:11:13.073Z",
  "record_id": "VXI-EXT-PROCUREMENT-CLOUDEVENTS-HTTP-MODE-CONTENT-TYPE-01-v1",
  "record_kind": "external_reference",
  "title": "CloudEvents HTTP envelope versus payload media type",
  "system": "CloudEvents v1.0.2",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an HTTP Content-Type header always describe only the CloudEvents event payload?",
  "near_questions": [
    "Does application/cloudevents+json describe the payload or the event envelope?",
    "Where are CloudEvents attributes in HTTP binary mode?",
    "How should an audit importer distinguish structured and binary CloudEvents?",
    "Can the HTTP media type differ from CloudEvents datacontenttype?"
  ],
  "supported_claims": [
    {
      "claim": "The 1.0.2 HTTP binding distinguishes binary, structured and batched modes. In binary mode, the HTTP body carries event data and Content-Type reflects datacontenttype, while other attributes use headers. Structured and batched modes place event metadata and data in the body using the event-format media type. Interpreting the header without the content mode can confuse envelope encoding with payload encoding.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "No actual transport message or decoder was inspected.",
    "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": "The 1.0.2 HTTP binding distinguishes binary, structured and batched modes. In binary mode, the HTTP body carries event data and Content-Type reflects datacontenttype, while other attributes use headers. Structured and batched modes place event metadata and data in the body using the event-format media type. Interpreting the header without the content mode can confuse envelope encoding with payload encoding.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "CloudEvents v1.0.2 — http-protocol-binding",
    "source_url": "https://raw.githubusercontent.com/cloudevents/spec/fc1f6f31f5f011a72183f1bcea20c987cb683ade/cloudevents/bindings/http-protocol-binding.md",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-CLOUDEVENTS-HTTP-MODE-CONTENT-TYPE-01-v1",
    "candidate_record_sha256": "70917ef996965ca19af4f4d3609b75158eeb8453022201981af5e5ac7d67dc5e",
    "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": "The 1.0.2 HTTP binding distinguishes binary, structured and batched modes. In binary mode, the HTTP body carries event data and Content-Type reflects datacontenttype, while other attributes use headers. Structured and batched modes place event metadata and data in the body using the event-format media type. Interpreting the header without the content mode can confuse envelope encoding with payload encoding.",
    "required_buyer_context": "HTTP headers and body; Detected content mode and supported event format; Payload datacontenttype and decoding result. 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 an HTTP Content-Type header always describe only the CloudEvents event payload?",
    "documented_statement": {
      "status": "documented",
      "statement": "The 1.0.2 HTTP binding distinguishes binary, structured and batched modes. In binary mode, the HTTP body carries event data and Content-Type reflects datacontenttype, while other attributes use headers. Structured and batched modes place event metadata and data in the body using the event-format media type. Interpreting the header without the content mode can confuse envelope encoding with payload encoding.",
      "source_ids": [
        "ce-http"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Decode and preserve event evidence according to its actual HTTP content mode. This is a review judgment, not an observed execution or deployment result.",
      "source_ids": [
        "ce-http"
      ]
    },
    "buyer_evidence_required": [
      "HTTP headers and body",
      "Detected content mode and supported event format",
      "Payload datacontenttype and decoding result"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse payload interpretation based on HTTP Content-Type without identifying the event mode."
    },
    "unknowns": "No actual transport message or decoder was inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No actual transport message or decoder was inspected."
    },
    "evidence_sources": [
      {
        "source_id": "ce-http",
        "url": "https://raw.githubusercontent.com/cloudevents/spec/fc1f6f31f5f011a72183f1bcea20c987cb683ade/cloudevents/bindings/http-protocol-binding.md",
        "final_url": "https://raw.githubusercontent.com/cloudevents/spec/fc1f6f31f5f011a72183f1bcea20c987cb683ade/cloudevents/bindings/http-protocol-binding.md",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:53:29.127Z",
        "sha256": "35b0bc7949dd95e1134867c0f3854d97f7d7f3adcfe7a9b378705489ccc65e83",
        "bytes": 19338,
        "title": "CloudEvents v1.0.2 — http-protocol-binding",
        "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": [
          "Content Modes; HTTP Message Mapping",
          "HTTP Message Mapping; Batched Content Mode"
        ],
        "version_context": "CloudEvents v1.0.2; extension status must be checked individually; pinned cloudevents/spec revision fc1f6f31f5f011a72183f1bcea20c987cb683ade. 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": "Decode and preserve event evidence according to its actual HTTP content mode.",
      "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": "Decode and preserve event evidence according to its actual HTTP content mode.",
    "refusal_conditions": [
      "Refuse payload interpretation based on HTTP Content-Type without identifying the event mode."
    ]
  },
  "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": "Decode and preserve event evidence according to its actual HTTP content mode.",
    "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#cloudevents-http-mode-content-type",
  "machine_readable_record": "/varexis-index/records/cloudevents-http-mode-content-type.json"
}