{ "title": "RCI Exact-Model Robot Stack Interface Evidence Audit", "version": "0.2.0", "schemaVersion": 1, "catalogVersion": "0.4.6", "released": "2026-08-10", "verifiedDate": "2026-08-10", "canonical": "https://robotcomponentindex.com/research/exact-model-robot-stack-interface-audit/", "rightsNotice": "RCI supplies original interface classification, boundaries and derived comparisons. Linked manufacturer documents and software retain their respective rights and licenses; this release does not redistribute or relicense them.", "interpretationBoundary": "A documented match means two cited specifications name a compatible interface layer. It does not prove exact-pair operation, sustained performance, timing accuracy, safety, regulatory compliance or whole-stack compatibility. Every observation in v0.2.0 remains untested by RCI.", "componentCount": 4, "pathCount": 5, "observationCount": 30, "sourceCount": 11, "documentedMatchCount": 2, "documentedConditionalCount": 8, "adapterRequiredCount": 5, "notDirectCount": 2, "unresolvedCount": 9, "notApplicableCount": 4, "independentlyTestedObservationCount": 0, "independentlyTestedPathCount": 0, "completeCompatibilityPathCount": 0, "componentIds": [ "cmp-realsense-d455", "cmp-seeed-recomputer-industrial-j4012", "cmp-livox-mid-360", "cmp-rrc2054-2" ], "sources": [ { "id": "realsense-d400-rev021", "title": "RealSense Camera D400 Series Product Family Datasheet", "url": "https://dev.realsenseai.com/download/42003/", "location": "Sections 3.7.5 and 4.2; tables 4-3, 4-5 and 7-9 for D455 USB transport, simultaneous streams and max-operating-mode power", "revision": "Revision 021 · October 2025 · document 337029-017" }, { "id": "realsense-librealsense-v2583", "title": "RealSense SDK 2.0 beta (v2.58.3)", "url": "https://github.com/realsenseai/librealsense/releases/tag/v2.58.3", "location": "Supported Platforms and Supported Cameras tables; D455 USB row", "revision": "v2.58.3 beta · published 2026-07-19 · commit dfd6aa9" }, { "id": "realsense-d400-firmware-table", "title": "D400 Series Firmware Releases", "url": "https://dev.realsenseai.com/docs/firmware-releases-d400/", "location": "Firmware 5.17.3.10 row", "revision": "Observed 2026-08-10 · row labels release 2.58.1 / SDK 2.58.1" }, { "id": "realsense-jetson-install", "title": "RealSense librealsense installation guide for NVIDIA Jetson devices", "url": "https://github.com/realsenseai/librealsense/blob/master/doc/installation_jetson.md", "location": "Jetson prerequisites, native and RSUSB backends, verified JetPack / L4T boundaries and device verification step", "revision": "master observed 2026-08-10" }, { "id": "livox-mid360-user-manual", "title": "Livox Mid-360 User Manual", "url": "https://terra-1-g.djicdn.com/851d20f7b9f64838a34cd02351370894/Livox/Livox_Mid-360_User_Manual_EN.pdf", "location": "Connectors; External Power Supply; Data Synchronization; Specifications", "revision": "Download page dated 2024-04-25" }, { "id": "livox-ros-driver2", "title": "Livox ROS Driver 2", "url": "https://github.com/Livox-SDK/livox_ros_driver2", "location": "Supported LiDAR list, MID360 configuration, ROS / ROS 2 build and launch instructions", "revision": "Official repository observed 2026-08-10" }, { "id": "seeed-j4012-getting-started", "title": "Getting Started with reComputer Industrial", "url": "https://wiki.seeedstudio.com/reComputer_Industrial_Getting_Started/", "location": "J4012 SKU row; networking, USB, power-input and JetPack tables", "revision": "Observed 2026-08-10" }, { "id": "seeed-j4012-interface-guide", "title": "reComputer Industrial J40 / J30 Hardware and Interfaces Usage", "url": "https://wiki.seeedstudio.com/reComputer_Industrial_J40_J30_Hardware_Interfaces_Usage/", "location": "Gigabit Ethernet connector topology and shared USB output-current limit", "revision": "Observed 2026-08-10" }, { "id": "rrc2054-2-datasheet", "title": "RRC2054-2 Product Data Sheet", "url": "https://www.rrc-ps.com/fileadmin/Dokumente/Data-Sheets/DS_RRC2054-2.pdf", "location": "Electrical parameters, contacts, safety functions and recommended accessories", "revision": "DS_RRC2054-2_J · released copy not subject to revision service" }, { "id": "rrc-smbus-cable", "title": "RRC SMBus Battery Cable", "url": "https://www.rrc-ps.com/en/power-management/battery-connectors/products/SMBus-Battery-Cable", "location": "Five-conductor pin and signal table; compatible RRC2054-2 product list", "revision": "Observed 2026-08-10" }, { "id": "rrc-pmm20", "title": "RRC-PMM20 Power Management Module", "url": "https://www.rrc-ps.com/en/power-management/power-management-modules/products/RRC-PMM20", "location": "RRC20xx battery compatibility, source selection and SMBus application interface", "revision": "Observed 2026-08-10" } ], "paths": [ { "id": "path-d455-to-j4012", "label": "RealSense D455 → Seeed reComputer Industrial J4012", "pathType": "device-to-host", "componentIds": [ "cmp-realsense-d455", "cmp-seeed-recomputer-industrial-j4012" ], "question": "Does the exact D455 camera have a documented data, power and software path to the exact J4012 host?", "strongestSupportedConclusion": "A standards-based USB 3 data path and a beta D455 software floor of firmware 5.17.3.10 with librealsense v2.58.3 are documented, but the official firmware table retains a different SDK association and the cable, shared-port current, exact J4012 image, timing behavior and concurrent workload still require pair-level validation.", "completeCompatibilityEvidence": false, "independentPairTest": false, "observations": [ { "id": "d455-j4012-connector", "layer": "mechanical-connector", "state": "adapter-required", "basis": "rci-derived", "statement": "D455 exposes a USB Type-C peripheral receptacle while J4012 exposes USB 3.2 Type-A host ports; a certified Type-A-to-Type-C SuperSpeed cable is required.", "boundary": "Matching connector shape is not enough: the cable must retain SuperSpeed pairs and satisfy the RealSense locking / interoperability guidance.", "requiredAction": "Select and record the exact certified cable part number, length and retention method.", "sourceIds": [ "realsense-d400-rev021", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "d455-j4012-power", "layer": "electrical-power", "state": "documented-conditional", "basis": "rci-derived", "statement": "RealSense publishes 3.46147 W total camera power at its stated max operating mode; Seeed publishes a 2.1 A maximum shared output-current limit for the stacked USB pair. At 5 V, 3.46147 W is approximately 0.69 A.", "boundary": "This is a document comparison, not a measurement. It does not cover cable loss, enumeration transients, projector behavior, another load on the shared pair or J4012 supply derating.", "requiredAction": "Use a dedicated host port, measure VBUS at the camera and log current during enumeration and the intended simultaneous stream mode.", "sourceIds": [ "realsense-d400-rev021", "seeed-j4012-interface-guide" ], "independentlyTested": false }, { "id": "d455-j4012-data", "layer": "data-transport", "state": "documented-match", "basis": "manufacturer-datasheet", "statement": "D455 is a USB 3.1 Gen 1 peripheral and J4012 publishes three USB 3.2 Gen 1 host ports; the transport generations share the 5 Gbit/s SuperSpeed data rate.", "boundary": "RealSense warns that shared hubs and concurrent devices consume the same bandwidth, so the match does not prove sustained application throughput.", "requiredAction": "Enumerate as SuperSpeed and record dropped frames while streaming the exact depth, RGB and IMU modes.", "sourceIds": [ "realsense-d400-rev021", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "d455-j4012-timing", "layer": "timing-synchronization", "state": "unresolved", "basis": "not-published", "statement": "The selected sources do not publish an end-to-end D455-to-J4012 timestamp-error or latency bound.", "boundary": "D455 frame sync and host timestamps are separate from a robot-wide clock domain; USB transport compatibility does not establish cross-sensor synchronization.", "requiredAction": "Measure device and host timestamp offsets and define the clock source used by the application.", "sourceIds": [ "realsense-d400-rev021" ], "independentlyTested": false }, { "id": "d455-j4012-software", "layer": "software-driver", "state": "documented-conditional", "basis": "official-software", "statement": "The RealSense SDK 2.0 beta v2.58.3 support table lists D455 USB with firmware 5.17.3.10 or later and SDK v2.58.3 or later, and lists JetPack 5.0.2, 6.0, 6.1, 6.2 and 7.0. Seeed separately publishes J4012 images across JetPack 5 and 6 branches.", "boundary": "The official D400 firmware table associates firmware 5.17.3.10 with SDK 2.58.1, while the v2.58.3 release table sets v2.58.3 as the D455 SDK floor. RCI preserves that source-level difference. The Jetson guide validates named NVIDIA board families and versions, not an exact J4012 carrier image, kernel patch, USB workload or long-run D455 result.", "requiredAction": "Freeze J4012 SKU, image, JetPack / L4T, kernel, librealsense and D455 firmware versions, then publish enumeration, stream, frame-loss and restart results.", "sourceIds": [ "realsense-librealsense-v2583", "realsense-d400-firmware-table", "realsense-jetson-install", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "d455-j4012-validation", "layer": "system-validation", "state": "unresolved", "basis": "not-published", "statement": "No exact J4012 + D455 independent pair test was selected in this audit.", "boundary": "Manufacturer documentation establishes a plausible integration route, not delivered performance or production reliability.", "requiredAction": "Publish raw enumeration, current, bandwidth, frame-loss, temperature and timestamp results for the exact pair.", "sourceIds": [ "realsense-d400-rev021", "realsense-jetson-install", "seeed-j4012-getting-started" ], "independentlyTested": false } ] }, { "id": "path-mid360-to-j4012", "label": "Livox MID-360 → Seeed reComputer Industrial J4012", "pathType": "device-to-host", "componentIds": [ "cmp-livox-mid-360", "cmp-seeed-recomputer-industrial-j4012" ], "question": "Does the exact MID-360 LiDAR have a documented Ethernet, timing and software path to the exact J4012 host?", "strongestSupportedConclusion": "A 100BASE-TX-to-Gigabit-Ethernet data route and official ROS driver exist, but MID-360 requires separate DC power and exact J4012 timing, driver and concurrent-load behavior remain unvalidated.", "completeCompatibilityEvidence": false, "independentPairTest": false, "observations": [ { "id": "mid360-j4012-connector", "layer": "mechanical-connector", "state": "adapter-required", "basis": "manufacturer-datasheet", "statement": "MID-360 combines power, Ethernet and function signals on a 12-pin M12 A-coded connector. The separately sold Livox 1-to-3 splitter exposes an RJ45 data lead and separate power / function leads for a computer connection.", "boundary": "The splitter is described for testing and temporary use; a production harness must preserve shielding, pinout, ingress protection and strain relief.", "requiredAction": "Freeze the exact splitter or production-harness part number and verify continuity, shielding and retention.", "sourceIds": [ "livox-mid360-user-manual", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "mid360-j4012-power", "layer": "electrical-power", "state": "not-direct", "basis": "manufacturer-datasheet", "statement": "MID-360 requires 9–27 VDC through its M12 power pins and reaches 18 W startup power under the stated temperature condition. J4012 Ethernet does not constitute a documented MID-360 power source.", "boundary": "J4012 LAN1 is a PoE PSE port, but MID-360 is not documented as an IEEE 802.3af powered device; the Livox splitter separates Ethernet and DC power.", "requiredAction": "Use the non-PSE data port or a reviewed network topology and provide a separately fused 9–27 V branch sized for startup and cold self-heating.", "sourceIds": [ "livox-mid360-user-manual", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "mid360-j4012-data", "layer": "data-transport", "state": "documented-match", "basis": "manufacturer-datasheet", "statement": "MID-360 publishes 100BASE-TX Ethernet / UDP transport and J4012 publishes 10/100/1000 Ethernet on its host ports.", "boundary": "Link-layer compatibility does not configure the static IP, subnet, packet format, receive buffers or application throughput.", "requiredAction": "Use a dedicated host port, assign a non-conflicting static subnet and log packet loss at the intended point-cloud mode.", "sourceIds": [ "livox-mid360-user-manual", "seeed-j4012-getting-started", "seeed-j4012-interface-guide" ], "independentlyTested": false }, { "id": "mid360-j4012-timing", "layer": "timing-synchronization", "state": "documented-conditional", "basis": "rci-derived", "statement": "MID-360 supports IEEE 1588-2008 PTPv2 over UDP/IPv4 and GPS / PPS input, so a documented sensor-side synchronization route exists.", "boundary": "The selected J4012 sources do not state NIC hardware-timestamp capability, PTP profile conformance or an achieved synchronization error for this pair.", "requiredAction": "Choose PTP or GPS, record ptp4l / timestamp configuration, and measure sensor-to-host and sensor-to-camera clock offsets.", "sourceIds": [ "livox-mid360-user-manual", "seeed-j4012-interface-guide" ], "independentlyTested": false }, { "id": "mid360-j4012-software", "layer": "software-driver", "state": "documented-conditional", "basis": "official-software", "statement": "Livox publishes Livox ROS Driver 2 with MID360 configuration and ROS / ROS 2 support; J4012 publishes JetPack Linux image choices.", "boundary": "The sources do not publish an exact J4012 SKU × JetPack × ROS distribution × Livox driver release validation matrix.", "requiredAction": "Freeze Ubuntu, JetPack, ROS, Livox SDK / driver and MID-360 firmware versions and archive the build plus launch configuration.", "sourceIds": [ "livox-ros-driver2", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "mid360-j4012-validation", "layer": "system-validation", "state": "unresolved", "basis": "not-published", "statement": "No exact J4012 + MID-360 independent pair test was selected in this audit.", "boundary": "A link and driver path do not prove packet delivery, PTP accuracy, thermal stability or restart behavior.", "requiredAction": "Publish packet-loss, timestamp-offset, restart, temperature and power traces for the exact pair.", "sourceIds": [ "livox-mid360-user-manual", "livox-ros-driver2", "seeed-j4012-getting-started" ], "independentlyTested": false } ] }, { "id": "path-rrc2054-to-j4012", "label": "RRC2054-2 battery → Seeed reComputer Industrial J4012", "pathType": "power-source-to-load", "componentIds": [ "cmp-rrc2054-2", "cmp-seeed-recomputer-industrial-j4012" ], "question": "Can the exact RRC2054-2 pack be treated as a drop-in supply for the exact J4012 computer?", "strongestSupportedConclusion": "The published nominal and maximum-charge voltages lie inside the J4012 input range, but minimum loaded voltage, connector, power-management, system-current and telemetry integration evidence are incomplete; this is not a drop-in conclusion.", "completeCompatibilityEvidence": false, "independentPairTest": false, "observations": [ { "id": "rrc2054-j4012-connector", "layer": "mechanical-connector", "state": "adapter-required", "basis": "manufacturer-datasheet", "statement": "RRC2054-2 exposes five blade contacts (+, C, D, T, −); J4012 accepts power on a two-pin terminal block. A keyed mating connector, harness, protection and strain relief are required.", "boundary": "A bare two-wire adaptation would discard SMBus and temperature contacts and would not provide charge or source-management behavior.", "requiredAction": "Use an RRC mating connector or reviewed PMM design and publish the complete pinout, fuse and wire gauge.", "sourceIds": [ "rrc2054-2-datasheet", "rrc-smbus-cable", "rrc-pmm20", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "rrc2054-j4012-power", "layer": "electrical-power", "state": "documented-conditional", "basis": "rci-derived", "statement": "RRC2054-2 publishes 14.40 V nominal and 16.80 V maximum charge voltage; both lie inside J4012’s published 12–24 VDC input interval.", "boundary": "RRC does not publish the pack’s minimum loaded output or CUV trip voltage in the selected datasheet, and Seeed does not publish an exact whole-system current envelope. Voltage overlap at two points does not prove full-discharge operation.", "requiredAction": "Measure startup, maximum workload and low-state-of-charge brownout while recording pack voltage, current and J4012 reset behavior.", "sourceIds": [ "rrc2054-2-datasheet", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "rrc2054-j4012-data", "layer": "data-transport", "state": "not-direct", "basis": "rci-derived", "statement": "The battery publishes SMBus contacts, while the selected J4012 external-I/O description does not identify a directly compatible external SMBus battery port.", "boundary": "SMBus electrical levels, connector, pull-ups, command set and host driver must all match; the word SMBus alone is not an integration proof.", "requiredAction": "Use a documented RRC PMM / reader or design and validate an explicit SMBus bridge and dataset implementation.", "sourceIds": [ "rrc2054-2-datasheet", "rrc-smbus-cable", "rrc-pmm20", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "rrc2054-j4012-timing", "layer": "timing-synchronization", "state": "not-applicable", "basis": "not-applicable", "statement": "Cross-device clock synchronization is not an applicable compatibility layer for this power-source-to-load path.", "boundary": "Battery telemetry polling cadence belongs to the software / data path, not the robot sensor clock domain.", "requiredAction": "No action beyond documenting telemetry polling and freshness if SMBus is integrated.", "sourceIds": [], "independentlyTested": false }, { "id": "rrc2054-j4012-software", "layer": "software-driver", "state": "unresolved", "basis": "not-published", "statement": "No exact J4012 software integration for the RRC2054-2 SMBus dataset was found in the selected official sources.", "boundary": "Powering the computer without telemetry is distinct from integrating state of charge, alarms, temperature and shutdown behavior.", "requiredAction": "Publish the SMBus commands, host driver, alarm handling, state-of-charge policy and safe-shutdown thresholds.", "sourceIds": [ "rrc2054-2-datasheet", "rrc-pmm20", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "rrc2054-j4012-validation", "layer": "system-validation", "state": "unresolved", "basis": "not-published", "statement": "No exact RRC2054-2 + J4012 discharge, brownout, recharge or thermal test was selected in this audit.", "boundary": "The pack’s 10 A maximum discharge figure is not a workload-qualified continuous system-power result.", "requiredAction": "Run cold / warm startup, sustained load, low-state-of-charge, shutdown and recharge tests with raw traces.", "sourceIds": [ "rrc2054-2-datasheet", "seeed-j4012-getting-started" ], "independentlyTested": false } ] }, { "id": "path-rrc2054-to-mid360", "label": "RRC2054-2 battery → Livox MID-360", "pathType": "power-source-to-load", "componentIds": [ "cmp-rrc2054-2", "cmp-livox-mid-360" ], "question": "Can the exact RRC2054-2 pack power the exact MID-360 sensor?", "strongestSupportedConclusion": "Nominal and fully charged pack voltages lie inside MID-360’s 9–27 V input interval, and the standalone current comparison has margin, but the harness, low-voltage endpoint, shared loads and restart behavior remain unvalidated.", "completeCompatibilityEvidence": false, "independentPairTest": false, "observations": [ { "id": "rrc2054-mid360-connector", "layer": "mechanical-connector", "state": "adapter-required", "basis": "manufacturer-datasheet", "statement": "RRC2054-2 blade contacts do not directly mate with the MID-360 M12 power pins; a keyed, fused harness or power-distribution module is required.", "boundary": "Polarity, cable drop, shielding, ingress protection and grounding must be engineered; the Livox 1-to-3 splitter exposes bare DC leads only on the sensor side.", "requiredAction": "Document the battery mating connector, fuse, wire gauge, splitter / M12 part and grounding topology.", "sourceIds": [ "rrc2054-2-datasheet", "rrc-smbus-cable", "livox-mid360-user-manual" ], "independentlyTested": false }, { "id": "rrc2054-mid360-power", "layer": "electrical-power", "state": "documented-conditional", "basis": "rci-derived", "statement": "RRC2054-2 publishes 14.40 V nominal, 16.80 V maximum charge and 10.0 A maximum discharge; MID-360 accepts 9–27 V and publishes an 18 W startup peak. At 14.40 V, 18 W corresponds to approximately 1.25 A.", "boundary": "This comparison covers the sensor alone at nominal pack voltage. It does not establish the pack’s low-voltage endpoint, cable drop, cold-start variation, simultaneous J4012 load or repeated inrush behavior.", "requiredAction": "Measure voltage at the MID-360 during startup, cold self-heating and low state of charge with the intended shared system loads.", "sourceIds": [ "rrc2054-2-datasheet", "livox-mid360-user-manual" ], "independentlyTested": false }, { "id": "rrc2054-mid360-data", "layer": "data-transport", "state": "not-applicable", "basis": "not-applicable", "statement": "No data protocol is required for the battery-to-sensor power path itself.", "boundary": "Battery telemetry and LiDAR Ethernet remain separate buses.", "requiredAction": "Document them as separate interfaces in the system diagram.", "sourceIds": [], "independentlyTested": false }, { "id": "rrc2054-mid360-timing", "layer": "timing-synchronization", "state": "not-applicable", "basis": "not-applicable", "statement": "Clock synchronization is not an applicable compatibility layer for this power-source-to-load path.", "boundary": "Power stability can affect timestamps through resets, but it does not supply time synchronization.", "requiredAction": "Record reset events during power validation; validate PTP or GPS separately.", "sourceIds": [], "independentlyTested": false }, { "id": "rrc2054-mid360-software", "layer": "software-driver", "state": "not-applicable", "basis": "not-applicable", "statement": "No software driver is required merely to energize the MID-360 from a reviewed DC branch.", "boundary": "Battery telemetry, alarm handling and LiDAR drivers remain separate software concerns.", "requiredAction": "Treat power-control and sensor-driver validation as separate test cases.", "sourceIds": [], "independentlyTested": false }, { "id": "rrc2054-mid360-validation", "layer": "system-validation", "state": "unresolved", "basis": "not-published", "statement": "No exact RRC2054-2 + MID-360 power test was selected in this audit.", "boundary": "Published voltage and current envelopes are design inputs, not proof of startup, noise immunity or runtime.", "requiredAction": "Publish raw voltage / current traces, startup success, reset count and temperature for the exact pair.", "sourceIds": [ "rrc2054-2-datasheet", "livox-mid360-user-manual" ], "independentlyTested": false } ] }, { "id": "path-four-component-stack", "label": "D455 + MID-360 + J4012 + RRC2054-2 whole stack", "pathType": "whole-stack", "componentIds": [ "cmp-realsense-d455", "cmp-livox-mid-360", "cmp-seeed-recomputer-industrial-j4012", "cmp-rrc2054-2" ], "question": "Do the four exact products form a validated robot perception, compute and power stack?", "strongestSupportedConclusion": "The documents expose a plausible USB camera path, Ethernet LiDAR path and partial DC-voltage overlap, but no source validates the four products together. The stack remains an integration hypothesis until power, timing, software, bandwidth and thermal tests are published.", "completeCompatibilityEvidence": false, "independentPairTest": false, "observations": [ { "id": "stack-connector", "layer": "mechanical-connector", "state": "adapter-required", "basis": "rci-derived", "statement": "The stack requires at least a SuperSpeed Type-A-to-Type-C camera cable, a MID-360 M12 splitter or production harness, an RRC battery mating connector and a fused DC distribution path.", "boundary": "No one published harness or mechanical assembly binds all four products.", "requiredAction": "Create a revisioned interconnect drawing and BOM with every connector, cable, fuse and strain-relief part number.", "sourceIds": [ "realsense-d400-rev021", "livox-mid360-user-manual", "rrc2054-2-datasheet", "rrc-smbus-cable", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "stack-power", "layer": "electrical-power", "state": "unresolved", "basis": "not-published", "statement": "No complete four-product power budget, startup sequence, low-state-of-charge behavior or thermal derating curve is published.", "boundary": "Adding headline watts or maximum current values would mix test conditions and omit carrier, storage, USB, network, cable and conversion losses.", "requiredAction": "Instrument every branch through cold start, peak compute load, sensor startup, steady operation and low state of charge.", "sourceIds": [ "realsense-d400-rev021", "livox-mid360-user-manual", "rrc2054-2-datasheet", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "stack-data", "layer": "data-transport", "state": "documented-conditional", "basis": "rci-derived", "statement": "J4012 publishes enough distinct host interfaces for one USB 3 D455 route and one Ethernet MID-360 route.", "boundary": "Port count does not prove concurrent sensor bandwidth, receive-buffer behavior, CPU / GPU contention, storage throughput or absence of dropped data.", "requiredAction": "Run both sensors simultaneously at frozen modes and log USB speed, Ethernet packet loss, frame loss, CPU / GPU load and storage latency.", "sourceIds": [ "realsense-d400-rev021", "livox-mid360-user-manual", "seeed-j4012-interface-guide" ], "independentlyTested": false }, { "id": "stack-timing", "layer": "timing-synchronization", "state": "unresolved", "basis": "not-published", "statement": "No source defines a common clock, hardware trigger bridge or measured temporal offset between the D455 stream and MID-360 PTP / GPS timestamps on J4012.", "boundary": "Host receipt time is not equivalent to synchronized sensor exposure or acquisition time.", "requiredAction": "Define the master clock and measure offset, drift and jitter across both sensor timestamp domains.", "sourceIds": [ "realsense-d400-rev021", "livox-mid360-user-manual" ], "independentlyTested": false }, { "id": "stack-software", "layer": "software-driver", "state": "documented-conditional", "basis": "rci-derived", "statement": "Official RealSense and Livox repositories separately provide Jetson / ROS-capable software paths, RealSense publishes a beta D455 firmware / SDK floor, and Seeed publishes J4012 JetPack image choices.", "boundary": "Separate support statements—and the differing official RealSense associations for firmware 5.17.3.10—do not prove that one exact kernel, JetPack, ROS distribution and driver pair works together without patches or regressions.", "requiredAction": "Freeze a single image manifest and publish reproducible installation, launch, configuration and restart logs.", "sourceIds": [ "realsense-librealsense-v2583", "realsense-d400-firmware-table", "realsense-jetson-install", "livox-ros-driver2", "seeed-j4012-getting-started" ], "independentlyTested": false }, { "id": "stack-validation", "layer": "system-validation", "state": "unresolved", "basis": "not-published", "statement": "Zero complete four-product validation packages were found or produced for this release.", "boundary": "This audit is documentary interface evidence. It is not a bench test, integration endorsement or procurement recommendation.", "requiredAction": "Publish a complete package containing hardware BOM, wiring, software manifest, raw power and timing traces, packet / frame loss, thermal soak and restart results.", "sourceIds": [ "realsense-d400-rev021", "realsense-librealsense-v2583", "realsense-d400-firmware-table", "realsense-jetson-install", "livox-mid360-user-manual", "livox-ros-driver2", "seeed-j4012-getting-started", "seeed-j4012-interface-guide", "rrc2054-2-datasheet", "rrc-smbus-cable", "rrc-pmm20" ], "independentlyTested": false } ] } ], "observations": [ { "id": "d455-j4012-connector", "layer": "mechanical-connector", "state": "adapter-required", "basis": "rci-derived", "statement": "D455 exposes a USB Type-C peripheral receptacle while J4012 exposes USB 3.2 Type-A host ports; a certified Type-A-to-Type-C SuperSpeed cable is required.", "boundary": "Matching connector shape is not enough: the cable must retain SuperSpeed pairs and satisfy the RealSense locking / interoperability guidance.", "requiredAction": "Select and record the exact certified cable part number, length and retention method.", "sourceIds": [ "realsense-d400-rev021", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-d455-to-j4012", "pathLabel": "RealSense D455 → Seeed reComputer Industrial J4012" }, { "id": "d455-j4012-power", "layer": "electrical-power", "state": "documented-conditional", "basis": "rci-derived", "statement": "RealSense publishes 3.46147 W total camera power at its stated max operating mode; Seeed publishes a 2.1 A maximum shared output-current limit for the stacked USB pair. At 5 V, 3.46147 W is approximately 0.69 A.", "boundary": "This is a document comparison, not a measurement. It does not cover cable loss, enumeration transients, projector behavior, another load on the shared pair or J4012 supply derating.", "requiredAction": "Use a dedicated host port, measure VBUS at the camera and log current during enumeration and the intended simultaneous stream mode.", "sourceIds": [ "realsense-d400-rev021", "seeed-j4012-interface-guide" ], "independentlyTested": false, "pathId": "path-d455-to-j4012", "pathLabel": "RealSense D455 → Seeed reComputer Industrial J4012" }, { "id": "d455-j4012-data", "layer": "data-transport", "state": "documented-match", "basis": "manufacturer-datasheet", "statement": "D455 is a USB 3.1 Gen 1 peripheral and J4012 publishes three USB 3.2 Gen 1 host ports; the transport generations share the 5 Gbit/s SuperSpeed data rate.", "boundary": "RealSense warns that shared hubs and concurrent devices consume the same bandwidth, so the match does not prove sustained application throughput.", "requiredAction": "Enumerate as SuperSpeed and record dropped frames while streaming the exact depth, RGB and IMU modes.", "sourceIds": [ "realsense-d400-rev021", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-d455-to-j4012", "pathLabel": "RealSense D455 → Seeed reComputer Industrial J4012" }, { "id": "d455-j4012-timing", "layer": "timing-synchronization", "state": "unresolved", "basis": "not-published", "statement": "The selected sources do not publish an end-to-end D455-to-J4012 timestamp-error or latency bound.", "boundary": "D455 frame sync and host timestamps are separate from a robot-wide clock domain; USB transport compatibility does not establish cross-sensor synchronization.", "requiredAction": "Measure device and host timestamp offsets and define the clock source used by the application.", "sourceIds": [ "realsense-d400-rev021" ], "independentlyTested": false, "pathId": "path-d455-to-j4012", "pathLabel": "RealSense D455 → Seeed reComputer Industrial J4012" }, { "id": "d455-j4012-software", "layer": "software-driver", "state": "documented-conditional", "basis": "official-software", "statement": "The RealSense SDK 2.0 beta v2.58.3 support table lists D455 USB with firmware 5.17.3.10 or later and SDK v2.58.3 or later, and lists JetPack 5.0.2, 6.0, 6.1, 6.2 and 7.0. Seeed separately publishes J4012 images across JetPack 5 and 6 branches.", "boundary": "The official D400 firmware table associates firmware 5.17.3.10 with SDK 2.58.1, while the v2.58.3 release table sets v2.58.3 as the D455 SDK floor. RCI preserves that source-level difference. The Jetson guide validates named NVIDIA board families and versions, not an exact J4012 carrier image, kernel patch, USB workload or long-run D455 result.", "requiredAction": "Freeze J4012 SKU, image, JetPack / L4T, kernel, librealsense and D455 firmware versions, then publish enumeration, stream, frame-loss and restart results.", "sourceIds": [ "realsense-librealsense-v2583", "realsense-d400-firmware-table", "realsense-jetson-install", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-d455-to-j4012", "pathLabel": "RealSense D455 → Seeed reComputer Industrial J4012" }, { "id": "d455-j4012-validation", "layer": "system-validation", "state": "unresolved", "basis": "not-published", "statement": "No exact J4012 + D455 independent pair test was selected in this audit.", "boundary": "Manufacturer documentation establishes a plausible integration route, not delivered performance or production reliability.", "requiredAction": "Publish raw enumeration, current, bandwidth, frame-loss, temperature and timestamp results for the exact pair.", "sourceIds": [ "realsense-d400-rev021", "realsense-jetson-install", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-d455-to-j4012", "pathLabel": "RealSense D455 → Seeed reComputer Industrial J4012" }, { "id": "mid360-j4012-connector", "layer": "mechanical-connector", "state": "adapter-required", "basis": "manufacturer-datasheet", "statement": "MID-360 combines power, Ethernet and function signals on a 12-pin M12 A-coded connector. The separately sold Livox 1-to-3 splitter exposes an RJ45 data lead and separate power / function leads for a computer connection.", "boundary": "The splitter is described for testing and temporary use; a production harness must preserve shielding, pinout, ingress protection and strain relief.", "requiredAction": "Freeze the exact splitter or production-harness part number and verify continuity, shielding and retention.", "sourceIds": [ "livox-mid360-user-manual", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-mid360-to-j4012", "pathLabel": "Livox MID-360 → Seeed reComputer Industrial J4012" }, { "id": "mid360-j4012-power", "layer": "electrical-power", "state": "not-direct", "basis": "manufacturer-datasheet", "statement": "MID-360 requires 9–27 VDC through its M12 power pins and reaches 18 W startup power under the stated temperature condition. J4012 Ethernet does not constitute a documented MID-360 power source.", "boundary": "J4012 LAN1 is a PoE PSE port, but MID-360 is not documented as an IEEE 802.3af powered device; the Livox splitter separates Ethernet and DC power.", "requiredAction": "Use the non-PSE data port or a reviewed network topology and provide a separately fused 9–27 V branch sized for startup and cold self-heating.", "sourceIds": [ "livox-mid360-user-manual", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-mid360-to-j4012", "pathLabel": "Livox MID-360 → Seeed reComputer Industrial J4012" }, { "id": "mid360-j4012-data", "layer": "data-transport", "state": "documented-match", "basis": "manufacturer-datasheet", "statement": "MID-360 publishes 100BASE-TX Ethernet / UDP transport and J4012 publishes 10/100/1000 Ethernet on its host ports.", "boundary": "Link-layer compatibility does not configure the static IP, subnet, packet format, receive buffers or application throughput.", "requiredAction": "Use a dedicated host port, assign a non-conflicting static subnet and log packet loss at the intended point-cloud mode.", "sourceIds": [ "livox-mid360-user-manual", "seeed-j4012-getting-started", "seeed-j4012-interface-guide" ], "independentlyTested": false, "pathId": "path-mid360-to-j4012", "pathLabel": "Livox MID-360 → Seeed reComputer Industrial J4012" }, { "id": "mid360-j4012-timing", "layer": "timing-synchronization", "state": "documented-conditional", "basis": "rci-derived", "statement": "MID-360 supports IEEE 1588-2008 PTPv2 over UDP/IPv4 and GPS / PPS input, so a documented sensor-side synchronization route exists.", "boundary": "The selected J4012 sources do not state NIC hardware-timestamp capability, PTP profile conformance or an achieved synchronization error for this pair.", "requiredAction": "Choose PTP or GPS, record ptp4l / timestamp configuration, and measure sensor-to-host and sensor-to-camera clock offsets.", "sourceIds": [ "livox-mid360-user-manual", "seeed-j4012-interface-guide" ], "independentlyTested": false, "pathId": "path-mid360-to-j4012", "pathLabel": "Livox MID-360 → Seeed reComputer Industrial J4012" }, { "id": "mid360-j4012-software", "layer": "software-driver", "state": "documented-conditional", "basis": "official-software", "statement": "Livox publishes Livox ROS Driver 2 with MID360 configuration and ROS / ROS 2 support; J4012 publishes JetPack Linux image choices.", "boundary": "The sources do not publish an exact J4012 SKU × JetPack × ROS distribution × Livox driver release validation matrix.", "requiredAction": "Freeze Ubuntu, JetPack, ROS, Livox SDK / driver and MID-360 firmware versions and archive the build plus launch configuration.", "sourceIds": [ "livox-ros-driver2", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-mid360-to-j4012", "pathLabel": "Livox MID-360 → Seeed reComputer Industrial J4012" }, { "id": "mid360-j4012-validation", "layer": "system-validation", "state": "unresolved", "basis": "not-published", "statement": "No exact J4012 + MID-360 independent pair test was selected in this audit.", "boundary": "A link and driver path do not prove packet delivery, PTP accuracy, thermal stability or restart behavior.", "requiredAction": "Publish packet-loss, timestamp-offset, restart, temperature and power traces for the exact pair.", "sourceIds": [ "livox-mid360-user-manual", "livox-ros-driver2", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-mid360-to-j4012", "pathLabel": "Livox MID-360 → Seeed reComputer Industrial J4012" }, { "id": "rrc2054-j4012-connector", "layer": "mechanical-connector", "state": "adapter-required", "basis": "manufacturer-datasheet", "statement": "RRC2054-2 exposes five blade contacts (+, C, D, T, −); J4012 accepts power on a two-pin terminal block. A keyed mating connector, harness, protection and strain relief are required.", "boundary": "A bare two-wire adaptation would discard SMBus and temperature contacts and would not provide charge or source-management behavior.", "requiredAction": "Use an RRC mating connector or reviewed PMM design and publish the complete pinout, fuse and wire gauge.", "sourceIds": [ "rrc2054-2-datasheet", "rrc-smbus-cable", "rrc-pmm20", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-rrc2054-to-j4012", "pathLabel": "RRC2054-2 battery → Seeed reComputer Industrial J4012" }, { "id": "rrc2054-j4012-power", "layer": "electrical-power", "state": "documented-conditional", "basis": "rci-derived", "statement": "RRC2054-2 publishes 14.40 V nominal and 16.80 V maximum charge voltage; both lie inside J4012’s published 12–24 VDC input interval.", "boundary": "RRC does not publish the pack’s minimum loaded output or CUV trip voltage in the selected datasheet, and Seeed does not publish an exact whole-system current envelope. Voltage overlap at two points does not prove full-discharge operation.", "requiredAction": "Measure startup, maximum workload and low-state-of-charge brownout while recording pack voltage, current and J4012 reset behavior.", "sourceIds": [ "rrc2054-2-datasheet", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-rrc2054-to-j4012", "pathLabel": "RRC2054-2 battery → Seeed reComputer Industrial J4012" }, { "id": "rrc2054-j4012-data", "layer": "data-transport", "state": "not-direct", "basis": "rci-derived", "statement": "The battery publishes SMBus contacts, while the selected J4012 external-I/O description does not identify a directly compatible external SMBus battery port.", "boundary": "SMBus electrical levels, connector, pull-ups, command set and host driver must all match; the word SMBus alone is not an integration proof.", "requiredAction": "Use a documented RRC PMM / reader or design and validate an explicit SMBus bridge and dataset implementation.", "sourceIds": [ "rrc2054-2-datasheet", "rrc-smbus-cable", "rrc-pmm20", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-rrc2054-to-j4012", "pathLabel": "RRC2054-2 battery → Seeed reComputer Industrial J4012" }, { "id": "rrc2054-j4012-timing", "layer": "timing-synchronization", "state": "not-applicable", "basis": "not-applicable", "statement": "Cross-device clock synchronization is not an applicable compatibility layer for this power-source-to-load path.", "boundary": "Battery telemetry polling cadence belongs to the software / data path, not the robot sensor clock domain.", "requiredAction": "No action beyond documenting telemetry polling and freshness if SMBus is integrated.", "sourceIds": [], "independentlyTested": false, "pathId": "path-rrc2054-to-j4012", "pathLabel": "RRC2054-2 battery → Seeed reComputer Industrial J4012" }, { "id": "rrc2054-j4012-software", "layer": "software-driver", "state": "unresolved", "basis": "not-published", "statement": "No exact J4012 software integration for the RRC2054-2 SMBus dataset was found in the selected official sources.", "boundary": "Powering the computer without telemetry is distinct from integrating state of charge, alarms, temperature and shutdown behavior.", "requiredAction": "Publish the SMBus commands, host driver, alarm handling, state-of-charge policy and safe-shutdown thresholds.", "sourceIds": [ "rrc2054-2-datasheet", "rrc-pmm20", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-rrc2054-to-j4012", "pathLabel": "RRC2054-2 battery → Seeed reComputer Industrial J4012" }, { "id": "rrc2054-j4012-validation", "layer": "system-validation", "state": "unresolved", "basis": "not-published", "statement": "No exact RRC2054-2 + J4012 discharge, brownout, recharge or thermal test was selected in this audit.", "boundary": "The pack’s 10 A maximum discharge figure is not a workload-qualified continuous system-power result.", "requiredAction": "Run cold / warm startup, sustained load, low-state-of-charge, shutdown and recharge tests with raw traces.", "sourceIds": [ "rrc2054-2-datasheet", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-rrc2054-to-j4012", "pathLabel": "RRC2054-2 battery → Seeed reComputer Industrial J4012" }, { "id": "rrc2054-mid360-connector", "layer": "mechanical-connector", "state": "adapter-required", "basis": "manufacturer-datasheet", "statement": "RRC2054-2 blade contacts do not directly mate with the MID-360 M12 power pins; a keyed, fused harness or power-distribution module is required.", "boundary": "Polarity, cable drop, shielding, ingress protection and grounding must be engineered; the Livox 1-to-3 splitter exposes bare DC leads only on the sensor side.", "requiredAction": "Document the battery mating connector, fuse, wire gauge, splitter / M12 part and grounding topology.", "sourceIds": [ "rrc2054-2-datasheet", "rrc-smbus-cable", "livox-mid360-user-manual" ], "independentlyTested": false, "pathId": "path-rrc2054-to-mid360", "pathLabel": "RRC2054-2 battery → Livox MID-360" }, { "id": "rrc2054-mid360-power", "layer": "electrical-power", "state": "documented-conditional", "basis": "rci-derived", "statement": "RRC2054-2 publishes 14.40 V nominal, 16.80 V maximum charge and 10.0 A maximum discharge; MID-360 accepts 9–27 V and publishes an 18 W startup peak. At 14.40 V, 18 W corresponds to approximately 1.25 A.", "boundary": "This comparison covers the sensor alone at nominal pack voltage. It does not establish the pack’s low-voltage endpoint, cable drop, cold-start variation, simultaneous J4012 load or repeated inrush behavior.", "requiredAction": "Measure voltage at the MID-360 during startup, cold self-heating and low state of charge with the intended shared system loads.", "sourceIds": [ "rrc2054-2-datasheet", "livox-mid360-user-manual" ], "independentlyTested": false, "pathId": "path-rrc2054-to-mid360", "pathLabel": "RRC2054-2 battery → Livox MID-360" }, { "id": "rrc2054-mid360-data", "layer": "data-transport", "state": "not-applicable", "basis": "not-applicable", "statement": "No data protocol is required for the battery-to-sensor power path itself.", "boundary": "Battery telemetry and LiDAR Ethernet remain separate buses.", "requiredAction": "Document them as separate interfaces in the system diagram.", "sourceIds": [], "independentlyTested": false, "pathId": "path-rrc2054-to-mid360", "pathLabel": "RRC2054-2 battery → Livox MID-360" }, { "id": "rrc2054-mid360-timing", "layer": "timing-synchronization", "state": "not-applicable", "basis": "not-applicable", "statement": "Clock synchronization is not an applicable compatibility layer for this power-source-to-load path.", "boundary": "Power stability can affect timestamps through resets, but it does not supply time synchronization.", "requiredAction": "Record reset events during power validation; validate PTP or GPS separately.", "sourceIds": [], "independentlyTested": false, "pathId": "path-rrc2054-to-mid360", "pathLabel": "RRC2054-2 battery → Livox MID-360" }, { "id": "rrc2054-mid360-software", "layer": "software-driver", "state": "not-applicable", "basis": "not-applicable", "statement": "No software driver is required merely to energize the MID-360 from a reviewed DC branch.", "boundary": "Battery telemetry, alarm handling and LiDAR drivers remain separate software concerns.", "requiredAction": "Treat power-control and sensor-driver validation as separate test cases.", "sourceIds": [], "independentlyTested": false, "pathId": "path-rrc2054-to-mid360", "pathLabel": "RRC2054-2 battery → Livox MID-360" }, { "id": "rrc2054-mid360-validation", "layer": "system-validation", "state": "unresolved", "basis": "not-published", "statement": "No exact RRC2054-2 + MID-360 power test was selected in this audit.", "boundary": "Published voltage and current envelopes are design inputs, not proof of startup, noise immunity or runtime.", "requiredAction": "Publish raw voltage / current traces, startup success, reset count and temperature for the exact pair.", "sourceIds": [ "rrc2054-2-datasheet", "livox-mid360-user-manual" ], "independentlyTested": false, "pathId": "path-rrc2054-to-mid360", "pathLabel": "RRC2054-2 battery → Livox MID-360" }, { "id": "stack-connector", "layer": "mechanical-connector", "state": "adapter-required", "basis": "rci-derived", "statement": "The stack requires at least a SuperSpeed Type-A-to-Type-C camera cable, a MID-360 M12 splitter or production harness, an RRC battery mating connector and a fused DC distribution path.", "boundary": "No one published harness or mechanical assembly binds all four products.", "requiredAction": "Create a revisioned interconnect drawing and BOM with every connector, cable, fuse and strain-relief part number.", "sourceIds": [ "realsense-d400-rev021", "livox-mid360-user-manual", "rrc2054-2-datasheet", "rrc-smbus-cable", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-four-component-stack", "pathLabel": "D455 + MID-360 + J4012 + RRC2054-2 whole stack" }, { "id": "stack-power", "layer": "electrical-power", "state": "unresolved", "basis": "not-published", "statement": "No complete four-product power budget, startup sequence, low-state-of-charge behavior or thermal derating curve is published.", "boundary": "Adding headline watts or maximum current values would mix test conditions and omit carrier, storage, USB, network, cable and conversion losses.", "requiredAction": "Instrument every branch through cold start, peak compute load, sensor startup, steady operation and low state of charge.", "sourceIds": [ "realsense-d400-rev021", "livox-mid360-user-manual", "rrc2054-2-datasheet", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-four-component-stack", "pathLabel": "D455 + MID-360 + J4012 + RRC2054-2 whole stack" }, { "id": "stack-data", "layer": "data-transport", "state": "documented-conditional", "basis": "rci-derived", "statement": "J4012 publishes enough distinct host interfaces for one USB 3 D455 route and one Ethernet MID-360 route.", "boundary": "Port count does not prove concurrent sensor bandwidth, receive-buffer behavior, CPU / GPU contention, storage throughput or absence of dropped data.", "requiredAction": "Run both sensors simultaneously at frozen modes and log USB speed, Ethernet packet loss, frame loss, CPU / GPU load and storage latency.", "sourceIds": [ "realsense-d400-rev021", "livox-mid360-user-manual", "seeed-j4012-interface-guide" ], "independentlyTested": false, "pathId": "path-four-component-stack", "pathLabel": "D455 + MID-360 + J4012 + RRC2054-2 whole stack" }, { "id": "stack-timing", "layer": "timing-synchronization", "state": "unresolved", "basis": "not-published", "statement": "No source defines a common clock, hardware trigger bridge or measured temporal offset between the D455 stream and MID-360 PTP / GPS timestamps on J4012.", "boundary": "Host receipt time is not equivalent to synchronized sensor exposure or acquisition time.", "requiredAction": "Define the master clock and measure offset, drift and jitter across both sensor timestamp domains.", "sourceIds": [ "realsense-d400-rev021", "livox-mid360-user-manual" ], "independentlyTested": false, "pathId": "path-four-component-stack", "pathLabel": "D455 + MID-360 + J4012 + RRC2054-2 whole stack" }, { "id": "stack-software", "layer": "software-driver", "state": "documented-conditional", "basis": "rci-derived", "statement": "Official RealSense and Livox repositories separately provide Jetson / ROS-capable software paths, RealSense publishes a beta D455 firmware / SDK floor, and Seeed publishes J4012 JetPack image choices.", "boundary": "Separate support statements—and the differing official RealSense associations for firmware 5.17.3.10—do not prove that one exact kernel, JetPack, ROS distribution and driver pair works together without patches or regressions.", "requiredAction": "Freeze a single image manifest and publish reproducible installation, launch, configuration and restart logs.", "sourceIds": [ "realsense-librealsense-v2583", "realsense-d400-firmware-table", "realsense-jetson-install", "livox-ros-driver2", "seeed-j4012-getting-started" ], "independentlyTested": false, "pathId": "path-four-component-stack", "pathLabel": "D455 + MID-360 + J4012 + RRC2054-2 whole stack" }, { "id": "stack-validation", "layer": "system-validation", "state": "unresolved", "basis": "not-published", "statement": "Zero complete four-product validation packages were found or produced for this release.", "boundary": "This audit is documentary interface evidence. It is not a bench test, integration endorsement or procurement recommendation.", "requiredAction": "Publish a complete package containing hardware BOM, wiring, software manifest, raw power and timing traces, packet / frame loss, thermal soak and restart results.", "sourceIds": [ "realsense-d400-rev021", "realsense-librealsense-v2583", "realsense-d400-firmware-table", "realsense-jetson-install", "livox-mid360-user-manual", "livox-ros-driver2", "seeed-j4012-getting-started", "seeed-j4012-interface-guide", "rrc2054-2-datasheet", "rrc-smbus-cable", "rrc-pmm20" ], "independentlyTested": false, "pathId": "path-four-component-stack", "pathLabel": "D455 + MID-360 + J4012 + RRC2054-2 whole stack" } ] }