ECZ-ID Robotics Inspection

Map your robot or fleet to its ECZ-ID Robot Passport — statically, safely, in one command. ecz-id-robotics inspects robot deployment descriptors and ROS workspaces, maps the operating environment to the parent Robot Passport, and routes passport setup to TrustOps. It inspects, explains and routes only.

It never connects to or commands a robot, never starts ROS, and never executes robot code. It never issues or activates an ECZ-ID, never prices or carts, and never certifies. Missing public proof is neutral. Local policy decides. Re-check before reliance.

One-command free trial

$ uvx ecz-id-robotics inspect ./my-robot
# or: pipx run ecz-id-robotics inspect ./my-robot

Genuine example result

ECZ-ID inspection: ./my-robot [ecz-id-robotics]
A. configuration posture : PRESENT
B. public proof posture  : NOT_CHECKED  (neutral)
reason codes : ECZ-1000, ECZ-2002, ECZ-5000

ECZ-5000 routes passport setup to TrustOps — this package only routes.

Supported inputs

• robot_deployment.json, robot.json, fleet.json.
• ROS package.xml files (parsed only after DTD/entity rejection).
• Observes operating_environment → parent passport (industrial → Industrial, public-space → Public-Space, domestic → Domestic Robot Passport); manufacturer/owner/operator/integrator/maintainer; firmware/software/API/cloud/model/dataset/IoT/supply-chain; teleoperation; maintenance and incident references.

Valuable free capabilities

Two-sided posture; scaffold a static robot profile; compare drift; JSON / Markdown / text / SARIF; redaction; offline.

Unsupported inputs

Not a robot controller, simulator or telemetry client. Never launches ROS nodes or connects to hardware.

What the result means / does not mean

Posture describes your local deployment descriptor; the public side is neutral read-only Resolver evidence. Not a safety, certification or compliance verdict; does not command or connect to a robot.

Compare / drift, CI

$ ecz-id-robotics compare ./last ./current --json
$ ecz-id-robotics inspect . --sarif > robotics.sarif

Machine-readable integration

Machine Interface · Manifest · Resolver · Operator setup · Developer guidance

Each installation includes structured machine-readable metadata for automation, CI and supported integrations. Every JSON report embeds a compact machine_interface object with the canonical roots and safe, read-only actions.

The package runs locally to inspect, explain and route. It does not issue an ECZ-ID, write canonical truth, create public proof, price a cart, or replace Resolver proof.

$ ecz-id-robotics manifest --json

• Central Machine Interface: https://machine.ecocitizenz.org/.well-known/ecz-machine.json
• Resolver (read-only public proof): https://resolver.ecocitizenz.org
• Operator setup (TrustOps): https://trustops.ecocitizenz.com/start
• Developer Gateway: https://developers.ecocitizenz.com

Privacy and no telemetry

Bounded, read-only, symlink-refusing inspection; XML DTD/entities rejected. No telemetry, no source upload. Secrets redacted on every export. Offline mode (--offline / ECZ_ID_OFFLINE=1) skips all network.

Continue with ECZ-ID

• Operator setup: https://trustops.ecocitizenz.com/start
• Developer guidance: https://developers.ecocitizenz.com
• Public Resolver proof: https://resolver.ecocitizenz.org
• Central Machine Interface: https://machine.ecocitizenz.org/.well-known/ecz-machine.json
• EcoCitizenz: https://www.ecocitizenz.com
• Specifications and governance: https://www.ecocitizenz.org
• ECZ-ID on Visual Studio Marketplace: https://marketplace.visualstudio.com/publishers/ecocitizenz
• ECZ-ID on Open VSX: https://open-vsx.org/namespace/ecocitizenz
• Explore the ECZ-ID Python tool family: https://pypi.org/search/?q=ecz-id

Licence and trademarks

Apache-2.0 (see LICENSE, NOTICE). The code licence grants no trademark rights; “ECZ-ID” and “EcoCitizenz” are trademarks of their owner(s) — see TRADEMARKS.md. Changelog: CHANGELOG.md. Security: SECURITY.md.

CLI: ecz-id-robotics  |  Import: ecz_id_robotics  |  Plugin group: ecz_id.plugins