{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T23:47:34.928Z",
  "record_id": "VXI-EXT-PROCUREMENT-SPARKPLUG-SECURITY-GUIDANCE-CONFORMANCE-01-v1",
  "record_kind": "external_reference",
  "title": "Sparkplug conformance and command authority",
  "system": "Eclipse Sparkplug 3.0.0",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does Sparkplug protocol conformance prove that command-topic permissions are correctly secured?",
  "near_questions": [
    "Does Sparkplug certification establish command-topic authorization?",
    "Which Sparkplug security guidance is non-normative?",
    "What broker evidence is needed for Sparkplug command permissions?",
    "Can a conformant Sparkplug connection still have overbroad topic access?"
  ],
  "supported_claims": [
    {
      "claim": "Sparkplug 3.0.0 presents its security chapter as non-normative guidance, discussing MQTT client identity, credentials and topic access control. These considerations do not make protocol conformance an independent permission audit. A buyer must inspect the actual broker and application authorization policies for publishing and subscribing to command topics.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Actual broker permissions and command enforcement were not assessed.",
    "No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Sparkplug 3.0.0 presents its security chapter as non-normative guidance, discussing MQTT client identity, credentials and topic access control. These considerations do not make protocol conformance an independent permission audit. A buyer must inspect the actual broker and application authorization policies for publishing and subscribing to command topics.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Sparkplug 3.0.0 release — Sparkplug_7_Security",
    "source_url": "https://raw.githubusercontent.com/eclipse-sparkplug/sparkplug/8b76877131203e88eaa9f5415e6a55f1a8470d74/specification/src/main/asciidoc/chapters/Sparkplug_7_Security.adoc",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SPARKPLUG-SECURITY-GUIDANCE-CONFORMANCE-01-v1",
    "candidate_record_sha256": "ba9ce6d7e0ef1d2ef6efefdbdb2b456a272121880e62067b86e21c4332cb27a4",
    "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": "Sparkplug 3.0.0 presents its security chapter as non-normative guidance, discussing MQTT client identity, credentials and topic access control. These considerations do not make protocol conformance an independent permission audit. A buyer must inspect the actual broker and application authorization policies for publishing and subscribing to command topics.",
    "required_buyer_context": "Broker topic access policy; Authenticated principal-to-client mapping; Intended NCMD and DCMD publishers. 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 Sparkplug protocol conformance prove that command-topic permissions are correctly secured?",
    "documented_statement": {
      "status": "documented",
      "statement": "Sparkplug 3.0.0 presents its security chapter as non-normative guidance, discussing MQTT client identity, credentials and topic access control. These considerations do not make protocol conformance an independent permission audit. A buyer must inspect the actual broker and application authorization policies for publishing and subscribing to command topics.",
      "source_ids": [
        "sparkplug-7"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Review command authority separately from protocol conformance. This is a review judgment, not a measured deployment result.",
      "source_ids": [
        "sparkplug-7"
      ]
    },
    "buyer_evidence_required": [
      "Broker topic access policy",
      "Authenticated principal-to-client mapping",
      "Intended NCMD and DCMD publishers"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse command-security approval based only on Sparkplug conformance."
    },
    "unknowns": "Actual broker permissions and command enforcement were not assessed.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Actual broker permissions and command enforcement were not assessed."
    },
    "evidence_sources": [
      {
        "source_id": "sparkplug-7",
        "url": "https://raw.githubusercontent.com/eclipse-sparkplug/sparkplug/8b76877131203e88eaa9f5415e6a55f1a8470d74/specification/src/main/asciidoc/chapters/Sparkplug_7_Security.adoc",
        "final_url": "https://raw.githubusercontent.com/eclipse-sparkplug/sparkplug/8b76877131203e88eaa9f5415e6a55f1a8470d74/specification/src/main/asciidoc/chapters/Sparkplug_7_Security.adoc",
        "status": 200,
        "captured_at_utc": "2026-10-24T23:24:16.985Z",
        "sha256": "8ca0ef2aced8f7c2b5ab9d3229eba6aeece3df5320a720a47bd8e144854e7957",
        "bytes": 5257,
        "title": "Sparkplug 3.0.0 release — Sparkplug_7_Security",
        "hash_basis": "SHA-256 of unmodified HTTP response body bytes",
        "rights_review": "Original bounded paraphrase; source bodies are captured privately and not redistributed. Eclipse repository EPL-2.0 licence reviewed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Non-normative security chapter; access control lists"
        ],
        "version_context": "Sparkplug 3.0.0 release; pinned repository revision 8b76877131203e88eaa9f5415e6a55f1a8470d74. Documentation is not 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": "Review command authority separately from protocol conformance.",
      "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 specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome."
    },
    "buyer_relevance": "Review command authority separately from protocol conformance.",
    "refusal_conditions": [
      "Refuse command-security approval based only on Sparkplug conformance."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Review command authority separately from protocol conformance.",
    "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#sparkplug-security-guidance-conformance",
  "machine_readable_record": "/varexis-index/records/sparkplug-security-guidance-conformance.json"
}