{ "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-25T20:55:19.974986+00:00", "record_id": "VXI-EXT-PROCUREMENT-MODBUS-DEVICE-IDENTIFICATION-PAGES-01-v1", "record_kind": "external_reference", "title": "MODBUS device-identification response continuation", "system": "MODBUS Application Protocol V1.1b3", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Does one MODBUS Read Device Identification response necessarily contain the complete identity object set?", "near_questions": [ "Can MODBUS device identification require several responses?", "Which field identifies the next device-identification object?", "Does individual-object mode return the whole MODBUS identity set?", "Does a complete identity listing authenticate physical equipment?" ], "supported_claims": [ { "claim": "MODBUS Read Device Identification uses More Follows and Next Object Id to continue stream access across multiple transactions when the response does not fit one message. Access modes 01 through 03 have different scope from individual-object mode 04. One successful response is not automatically a complete identity inventory, nor authenticated proof of a physical device.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "Scope completeness to the requested access mode and supported conformity level. Codes01-03 stream; code04 returns an individual object and More Follows is00. Do not claim authenticated physical device identity or all optional identity attributes.", "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": "MODBUS Read Device Identification uses More Follows and Next Object Id to continue stream access across multiple transactions when the response does not fit one message. Access modes 01 through 03 have different scope from individual-object mode 04. One successful response is not automatically a complete identity inventory, nor authenticated proof of a physical device.", "related_record_ids": [], "source_review": { "source_type": "official_external_documentation", "source_title": "MODBUS Application Protocol V1.1b3", "source_url": "https://www.modbus.org/file/secure/modbusprotocolspecification.pdf", "checked_on": "2026-10-25", "candidate_record_id": "VXI-EXT-PROCUREMENT-MODBUS-DEVICE-IDENTIFICATION-PAGES-01-v1", "candidate_record_sha256": "b8aa0cbc3b22deec28d1bdd7d9471b9f14651e0eb74292d990034116e9d35436", "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": "MODBUS Read Device Identification uses More Follows and Next Object Id to continue stream access across multiple transactions when the response does not fit one message. Access modes 01 through 03 have different scope from individual-object mode 04. One successful response is not automatically a complete identity inventory, nor authenticated proof of a physical device.", "required_buyer_context": "Read Device ID access mode; More Follows and Next Object Id; Collected object set and independent physical identity. 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 one MODBUS Read Device Identification response necessarily contain the complete identity object set?", "documented_statement": { "status": "documented", "statement": "MODBUS Read Device Identification uses More Follows and Next Object Id to continue stream access across multiple transactions when the response does not fit one message. Access modes 01 through 03 have different scope from individual-object mode 04. One successful response is not automatically a complete identity inventory, nor authenticated proof of a physical device.", "source_ids": [ "modbus-1-1b3" ] }, "review_inference": { "status": "review_inference", "statement": "Reassemble device-identification continuation responses before asserting completeness. This is a documentation-review judgment, not an observed deployment outcome.", "source_ids": [ "modbus-1-1b3" ] }, "buyer_evidence_required": [ "Read Device ID access mode", "More Follows and Next Object Id", "Collected object set and independent physical identity" ], "review_condition": { "status": "varexis_review_policy", "statement": "Refuse buyer-specific assurance from documentation alone. Scope completeness to the requested access mode and supported conformity level. Codes01-03 stream; code04 returns an individual object and More Follows is00. Do not claim authenticated physical device identity or all optional identity attributes." }, "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": "modbus-1-1b3", "url": "https://www.modbus.org/file/secure/modbusprotocolspecification.pdf", "final_url": "https://www.modbus.org/file/secure/modbusprotocolspecification.pdf", "status": 200, "captured_at_utc": "2026-10-25T20:04:29.497Z", "sha256": "f80d0d7132fd035104c3f21b01026470e3310ca3d8d493d9a9737d0d32ad2eb1", "bytes": 932519, "title": "MODBUS Application Protocol V1.1b3", "hash_basis": "SHA-256 of unmodified HTTP response body bytes", "rights_review": "Original factual paraphrase and citation only. Modbus Organization retains rights in its specification. The captured PDF, figures and tables remain private; no standard or implementation code is redistributed.", "checked_on": "2026-10-25", "capture_status": 200, "claim_review_completed": true, "reviewed_sections": [ "Section 7, exception code 05", "Section 7, exception code 06", "Section 7, exception code 03", "Section 6.21", "Section 6.17" ], "version_context": "MODBUS Application Protocol V1.1b3, dated April 26 2012; device function support and physical behavior unverified." } ], "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": "Reassemble device-identification continuation responses before asserting completeness.", "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 Section 6.21 in MODBUS Application Protocol V1.1b3 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval." }, "buyer_relevance": "Reassemble device-identification continuation responses before asserting completeness.", "refusal_conditions": [ "Refuse buyer-specific assurance from documentation alone. Scope completeness to the requested access mode and supported conformity level. Codes01-03 stream; code04 returns an individual object and More Follows is00. Do not claim authenticated physical device identity or all optional identity attributes." ] }, "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": "Reassemble device-identification continuation responses before asserting completeness.", "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#modbus-device-identification-pages", "machine_readable_record": "/varexis-index/records/modbus-device-identification-pages.json" }