{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T23:11:13.073Z",
  "record_id": "VXI-EXT-PROCUREMENT-CLOUDEVENTS-SPECVERSION-PAYLOAD-SCHEMA-01-v1",
  "record_kind": "external_reference",
  "title": "CloudEvents envelope version versus data schema",
  "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 CloudEvents specversion 1.0 identify the exact payload schema or specification patch version?",
  "near_questions": [
    "Does CloudEvents 1.0 mean its payload uses one fixed schema?",
    "How can CloudEvents 1.0.2 still serialize specversion as 1.0?",
    "What changes when a CloudEvents dataschema becomes incompatible?",
    "Which evidence pins a CloudEvents payload contract?"
  ],
  "supported_claims": [
    {
      "claim": "CloudEvents 1.0.2 requires specversion to be 1.0, retaining only major and minor numbers across specification patch changes. The separate optional dataschema URI identifies the payload schema, and incompatible schema changes should use a different URI. The envelope version therefore cannot establish a particular payload contract or the exact specification patch used by an implementation.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Producer schema conformance and implementation patch level were not assessed.",
    "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": "CloudEvents 1.0.2 requires specversion to be 1.0, retaining only major and minor numbers across specification patch changes. The separate optional dataschema URI identifies the payload schema, and incompatible schema changes should use a different URI. The envelope version therefore cannot establish a particular payload contract or the exact specification patch used by an implementation.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "CloudEvents v1.0.2 — spec",
    "source_url": "https://raw.githubusercontent.com/cloudevents/spec/fc1f6f31f5f011a72183f1bcea20c987cb683ade/cloudevents/spec.md",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-CLOUDEVENTS-SPECVERSION-PAYLOAD-SCHEMA-01-v1",
    "candidate_record_sha256": "23e6a8f5026ff6eedac21494d79ac2001a50ecd936956ebe21f0a4939ea9c8ac",
    "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": "CloudEvents 1.0.2 requires specversion to be 1.0, retaining only major and minor numbers across specification patch changes. The separate optional dataschema URI identifies the payload schema, and incompatible schema changes should use a different URI. The envelope version therefore cannot establish a particular payload contract or the exact specification patch used by an implementation.",
    "required_buyer_context": "Declared specversion and implementation version; Payload schema identifier and retained schema revision; Producer compatibility and validation evidence. 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 CloudEvents specversion 1.0 identify the exact payload schema or specification patch version?",
    "documented_statement": {
      "status": "documented",
      "statement": "CloudEvents 1.0.2 requires specversion to be 1.0, retaining only major and minor numbers across specification patch changes. The separate optional dataschema URI identifies the payload schema, and incompatible schema changes should use a different URI. The envelope version therefore cannot establish a particular payload contract or the exact specification patch used by an implementation.",
      "source_ids": [
        "ce-spec"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Pin payload interpretation separately from envelope compatibility. This is a review judgment, not an observed execution or deployment result.",
      "source_ids": [
        "ce-spec"
      ]
    },
    "buyer_evidence_required": [
      "Declared specversion and implementation version",
      "Payload schema identifier and retained schema revision",
      "Producer compatibility and validation evidence"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse exact payload-schema or patch-version attribution from specversion alone."
    },
    "unknowns": "Producer schema conformance and implementation patch level were not assessed.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Producer schema conformance and implementation patch level were not assessed."
    },
    "evidence_sources": [
      {
        "source_id": "ce-spec",
        "url": "https://raw.githubusercontent.com/cloudevents/spec/fc1f6f31f5f011a72183f1bcea20c987cb683ade/cloudevents/spec.md",
        "final_url": "https://raw.githubusercontent.com/cloudevents/spec/fc1f6f31f5f011a72183f1bcea20c987cb683ade/cloudevents/spec.md",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:53:28.460Z",
        "sha256": "e327435c858d19fd171e4ab9781a01fc22dfa949d23c4220976529ebd16a1aa3",
        "bytes": 25542,
        "title": "CloudEvents v1.0.2 — spec",
        "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": [
          "Terminology: event; required id and source",
          "Source and producer terminology; required source",
          "Optional time",
          "specversion; dataschema",
          "Event Data optionality; JSON Handling of data"
        ],
        "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": "Pin payload interpretation separately from envelope compatibility.",
      "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": "Pin payload interpretation separately from envelope compatibility.",
    "refusal_conditions": [
      "Refuse exact payload-schema or patch-version attribution from specversion alone."
    ]
  },
  "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": "Pin payload interpretation separately from envelope compatibility.",
    "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-specversion-payload-schema",
  "machine_readable_record": "/varexis-index/records/cloudevents-specversion-payload-schema.json"
}