{ "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-25T20:55:19.974986+00:00", "record_id": "VXI-EXT-PROCUREMENT-MODBUS-ILLEGAL-VALUE-01-v1", "record_kind": "external_reference", "title": "MODBUS illegal data value boundary", "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 MODBUS Illegal Data Value establish whether a submitted register value is acceptable to the application?", "near_questions": [ "Does MODBUS exception 03 validate an engineering operating range?", "Can a structurally valid register value still be unsuitable?", "What kind of invalid query does Illegal Data Value describe?", "Does MODBUS assess the meaning of a value submitted for storage?" ], "supported_claims": [ { "claim": "MODBUS exception 03 reports a value in the query data field that is not allowed, such as an incorrectly structured request. The specification explicitly distinguishes this from an application judging whether a value submitted for storage is meaningful or acceptable. Protocol acceptance is not validation of a process range, calibration or engineering limit.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "Reword measured register value to value submitted for storage: that is the exact source contrast. The protocol cannot establish physical thresholds, device safety, measurement validity or a safe corrective action.", "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 exception 03 reports a value in the query data field that is not allowed, such as an incorrectly structured request. The specification explicitly distinguishes this from an application judging whether a value submitted for storage is meaningful or acceptable. Protocol acceptance is not validation of a process range, calibration or engineering limit.", "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-ILLEGAL-VALUE-01-v1", "candidate_record_sha256": "9bab502b072233abc80f65aef4ab3a4e21af33d54f601d0bb0c3abc863fd1abe", "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 exception 03 reports a value in the query data field that is not allowed, such as an incorrectly structured request. The specification explicitly distinguishes this from an application judging whether a value submitted for storage is meaningful or acceptable. Protocol acceptance is not validation of a process range, calibration or engineering limit.", "required_buyer_context": "Function and request structure; Register/application semantics; Independent allowed-range or calibration 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-25", "claim_to_check": "Does MODBUS Illegal Data Value establish whether a submitted register value is acceptable to the application?", "documented_statement": { "status": "documented", "statement": "MODBUS exception 03 reports a value in the query data field that is not allowed, such as an incorrectly structured request. The specification explicitly distinguishes this from an application judging whether a value submitted for storage is meaningful or acceptable. Protocol acceptance is not validation of a process range, calibration or engineering limit.", "source_ids": [ "modbus-1-1b3" ] }, "review_inference": { "status": "review_inference", "statement": "Separate request-format rejection from the physical meaning of register values. This is a documentation-review judgment, not an observed deployment outcome.", "source_ids": [ "modbus-1-1b3" ] }, "buyer_evidence_required": [ "Function and request structure", "Register/application semantics", "Independent allowed-range or calibration evidence" ], "review_condition": { "status": "varexis_review_policy", "statement": "Refuse buyer-specific assurance from documentation alone. Reword measured register value to value submitted for storage: that is the exact source contrast. The protocol cannot establish physical thresholds, device safety, measurement validity or a safe corrective action." }, "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": "Separate request-format rejection from the physical meaning of register values.", "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 7, exception code 03 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": "Separate request-format rejection from the physical meaning of register values.", "refusal_conditions": [ "Refuse buyer-specific assurance from documentation alone. Reword measured register value to value submitted for storage: that is the exact source contrast. The protocol cannot establish physical thresholds, device safety, measurement validity or a safe corrective action." ] }, "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": "Separate request-format rejection from the physical meaning of register values.", "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-illegal-value", "machine_readable_record": "/varexis-index/records/modbus-illegal-value.json" }