The evidence is proven or strong, but this capability still needs a capability-specific ESP32 or Rust runtime adapter.
Intended capability
Validate this target only after a capability-specific adapter and ground-truth study exist: The compiled judgment for one cell: a periodically signed, scope-limited attestation of what the witness plane covered, every enumerated event with its evidence class and its defeats, and where observed physics agreed or diverged from the estate's declared state, with confidence. Every sentence traces to a sensed event, and every certificate carries the scope line verbatim: not a safety function, the certified stack remains authoritative, ISO 13849 out of scope, and not a conformity assessment, EU declaration of conformity, or certificate of conformity within the meaning of EU 2023/1230.
This describes the intended outcome. Readiness is needs edge adapter, evidence is class B, and a catalog mapping or recording is not proof of this outcome at a real site.
Solution blueprint
See the environment before installing it.
This exact kit is one of 191 first-class designs. It includes geometry, objects, nodes, wording, scenarios, installation, limitations, and catalog-bound readiness.
No rendered revision is available yet.
Bundled recording
A related Cobot scene
This is one recorded vertical scenario. It is not separate validation of every capability in the catalog.
01 The physics
A certificate is only as honest as its coverage map, so coverage is the opening physics it states: which cones, which links, which hours, and each sensor's defeat conditions. Its evidentiary weight comes from independence — the sensing chain shares no software, network, or clock with the robot stack it corroborates — and from restraint: divergence is attested as divergence, cause is left to the investigation, and estate data appears only as the declared side of a comparison, read-only, never trusted.
02 Shared processing path
Ledger + conformance + hold + boundary rows over the certificate period -> coverage compiler (zones, sensors, hours, no-assessment windows, staleness bounds) -> declared-vs-observed reconciliation with per-finding confidence -> reasoning-tier narrative in which every sentence cites an event row -> scope-line injection -> signed, integrity-chained certificate document.
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
03 Validation plan
Certificate discipline is validated by adversarial review, not bench: a red-team pass in which each sentence must be traced to its event row or struck; dry-run certificates issued for the own-hardware cell across a month of scripted operation, then audited line-by-line; a divergence seeded in the estate feed must surface as a divergence finding or the release is blocked.
04 Commercial hypothesis
'Cell Certificate' — for the plant compliance owner and their insurer: the month of a collaborative cell, attested by an independent witness whose every claim carries its own defeats — the corroboration a self-reported robot log cannot be.