{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-09T18:04:24.907Z",
  "record_id": "VXI-EXT-OTEL-SEMCONV-02-v1",
  "record_kind": "external_reference",
  "title": "OpenTelemetry: Telemetry shape across upgrades",
  "system": "OpenTelemetry",
  "evidence_family": "telemetry_compatibility",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can I assume telemetry names and attributes stay unchanged after an instrumentation upgrade?",
  "near_questions": [
    "Can an OpenTelemetry upgrade rename my metrics?",
    "What does unstable instrumentation allow to change?",
    "Does a Schema URL guarantee telemetry compatibility?",
    "Are new attributes allowed in stable telemetry?",
    "What should I check before updating an observability library?",
    "Can semantic conventions alone keep dashboards working?",
    "How does instrumentation stability differ from common naming?",
    "Should telemetry review retain the producer version?",
    "Can I rely on schema transformations for telemetry stability?",
    "What can break a saved metric query after an upgrade?",
    "Does a stable label eliminate the need for alert regression checks?",
    "What should a telemetry compatibility record include?"
  ],
  "supported_claims": [
    {
      "claim": "The OpenTelemetry Telemetry Stability page, currently marked Development, distinguishes unstable from stable instrumentation. Unstable producers offer no telemetry-shape guarantees; additive telemetry is allowed for both classes. The page also retains a moratorium on relying on schema transformations for stability. Check the producer label, version and emitted fields before updating dashboards or alert rules; a Schema URL alone does not demonstrate compatibility.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "unchanged telemetry across arbitrary upgrades",
    "automatic schema conversion support",
    "working dashboards or alert rules without validation"
  ],
  "public_summary": "The OpenTelemetry Telemetry Stability page, currently marked Development, distinguishes unstable from stable instrumentation. Unstable producers offer no telemetry-shape guarantees; additive telemetry is allowed for both classes. The page also retains a moratorium on relying on schema transformations for stability. Check the producer label, version and emitted fields before updating dashboards or alert rules; a Schema URL alone does not demonstrate compatibility.",
  "related_record_ids": [
    "VXI-EXT-MS-SK-ORCH-01-v1",
    "VXI-EXT-MS-AF-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "OpenTelemetry: Telemetry Stability",
    "source_url": "https://opentelemetry.io/docs/specs/otel/telemetry-stability/",
    "checked_on": "2026-10-09",
    "candidate_record_id": "VXI-EXT-OTEL-SEMCONV-02-v1",
    "candidate_record_sha256": "dd46e9fc4dd50181d0e9e735df02f4e2553792022cf2e89018b9dc46e6054d15",
    "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 OpenTelemetry Telemetry Stability page, currently marked Development, distinguishes unstable from stable instrumentation. Unstable producers offer no telemetry-shape guarantees; additive telemetry is allowed for both classes. The page also retains a moratorium on relying on schema transformations for stability. Check the producer label, version and emitted fields before updating dashboards or alert rules; a Schema URL alone does not demonstrate compatibility.",
    "required_buyer_context": "Instrumentation producer and version, stability label, relevant convention version, emitted fields, schema support and downstream query tests. The cited guidance is marked Development.",
    "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.",
  "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#otel-telemetry-stability-contract",
  "machine_readable_record": "/varexis-index/records/otel-telemetry-stability-contract.json"
}
