EVIDE for Home Robotics

EVIDE Home Robot Safety is a proposed evidence service for household robotics. The resident selects the event categories that matter in their home. When an enabled event occurs, the robot or its service platform can send a limited, structured intake to EVIDE for independent preservation. The precise triggers, supported data and integrations depend on the robot manufacturer and the agreed deployment.

An owner or authorized resident could select from event categories such as:

1. Choose the boundaries. The resident or responsible operator declares enabled categories, relevant rooms, contacts, retention choices and who may review records. A robot's operational limits may also be declared in advance through EVIDE ANCHOR where applicable.
2. Detect and act locally. The robot or its safety system responds according to its own design. An urgent response must not depend on internet access or on EVIDE accepting an intake.
3. Submit a limited intake. The integration sends the event type, reported observation, time references, robot and deployment references, declared confidence or uncertainty, local response, and escalation status. It identifies the source of each claim.
4. Preserve the boundary. EVIDE independently records the submitted declaration and its receipt time. Supporting material can be referenced as external artifacts where supported, with origin and integrity values declared by the submitter.
5. Review what can be reconstructed. The resident, manufacturer, service provider or authorized reviewer can later distinguish the robot's report from the independently preserved receipt and from any separate evidence.

The starting point is an event record with the minimum useful information, not continuous video or unrestricted room audio. Photos, video, sensor logs or medical details require a specific reason, appropriate authority and an agreed handling process. A resident should be able to understand which events are enabled and who receives them. Household members, guests and care recipients may have different privacy interests, which must be addressed in the deployment design.

Records can refer to externally held material without EVIDE receiving the underlying file. Where an integrity hash is supplied by the submitter, EVIDE preserves it as part of the declared reference; EVIDE does not verify the underlying file's truth, completeness or integrity independently.

EVIDE is an external evidentiary layer. It does not remotely stop a robot, replace an emergency stop, diagnose an injury, decide whether an intruder is present, dispatch emergency services, or assign fault. Those actions require separately designed safety, emergency and human decision processes. Identity verification, where used, is provided by DAPI; EVIDE associates the declared identity reference with a record.

For manufacturers and home service providers, this creates a path to test a small set of event declarations without exposing continuous telemetry, internal control logic or source code. For residents, it offers a clearer answer to a practical question:

SOS EVIDE is a separate proposed service for robot-initiated reports of situations that may require human attention. Imagine a robot encountering a road accident, a person apparently in difficulty, smoke in a shared space or another unexpected hazard. It could submit a bounded intake stating what it reported observing, where and when it reported it, how uncertain it was, and what local action or notification followed.

The intake would enter a defined human review and routing process. It would not, by itself, certify an emergency or automatically instruct public authorities. A future SOS EVIDE page should specify consent and legal basis, location handling, false reports, duplicate reports, reviewer duties, recipient selection, response timing and failure modes before making any operational promise.

The two may share EVIDE's evidentiary infrastructure while requiring different permissions and workflows.

6. EVIDE My AI Rules: when a household rule changes

Household rules for a robot are rarely set once. Rooms, schedules, visitors and care needs change, and the rules change with them. EVIDE My AI Rules is an experimental direction that applies EVIDE to the rules a household declares for its robot and to later changes submitted to EVIDE. Its contribution is evidentiary: preserving an attributable, time-referenced history of what was declared and of what was later changed, so that it can be examined afterwards.

What the record can make examinable

• Which rule was declared: the declared content, as preserved in the record.
• Who declared it, or who proposed a change, according to the attribution available: the declarant stated in the record, any proposer the declaration names, and the identity associated with the submission (with DAPI where used).
• Which earlier rule a change refers to: a declared link to the earlier declaration, through its digest.
• Whether the change is presented as a restriction, an expansion, a clarification or a revocation: as declared by its author, not as judged by EVIDE.
• When the declaration says the change happened: a time supplied by the submitter.
• When EVIDE actually acquired the declaration: the acquisition timestamp recorded by EVIDE.
• Which supporting materials were only referenced, and which were actually received, stored and hashed by EVIDE.

A small example

1. Record 1 · Rule declared
   Resident A declares: "The robot must not enter the bedroom." The time the declaration states and the time EVIDE acquired it are kept as two separate values.
2. Record 2 · Exception proposed
   A temporary exception is proposed: the robot may enter the bedroom on Saturday mornings for cleaning, for the next four weeks. The declaration is submitted by the home care service (the declarant) and states that household member B proposed it (the proposer). It is linked to Record 1 and presented as an expansion.
   Preserved: the proposal, its link to Record 1, who declared it and whom it names as proposer. Not shown: that the exception was approved or applied.
3. Record 3 · Approval, only if acquired
   A separate declaration, for example by resident A, linked to Record 2. Without it, the history shows a proposal and nothing more.
4. Record 4 · Configuration loading declared, only if acquired
   A separate declaration, for example by the robot's service platform, stating that the exception was loaded into the robot's configuration. It does not show that the exception was active or used by the robot, nor how the robot actually behaved.

Record 2 does not replace Record 1 in the declared history. Whoever examines the history later finds the original rule, the proposal and, where they were acquired, the approval and the configuration loading statement, each with its own author and time references.

Available today, and still experimental

How a later Declaration links to an earlier one: EVIDE ANCHOR, Section 3

Declared time versus acquisition time: EVIDE ANCHOR, Section 8

Referenced versus received material: EVIDE Artifacts, Section 4

Where experimental work is tested: EVIDE Governance Lab

EVIDE invites robotics manufacturers, home care providers and deployment partners to define a small, synthetic, non-sensitive pilot: one robot or simulated integration, two or three declared event types, a minimum intake schema and a review of what can actually be reconstructed. The Governance Lab's existing sequence is registration, mutual NDA, Experimental Scope Note and bounded PoGR.

Discuss a pilot: info@certifywebcontent.com
Explore EVIDE for Physical AI: app.certifywebcontent.com/docs/evide-physical-ai/
Explore the Governance Lab: lab.certifywebcontent.com

EVIDE for Physical AI: Evidentiary infrastructure for robotics and autonomous systems

EVIDE ANCHOR: Declared operational perimeter

EVIDE Artifacts: External references vs. received deposits

EVIDE Governance Lab: Bounded pilots and experimental protocols