ECZ-ID Robotics Trust

Review robotics deployment descriptors and their identity and proof posture.

Free, local-first. No source upload. No sign-in to run a check.

• Surfaces ROS / robot description (URDF) and related evidence — locally, by filename and path.
• Builds a local, claim-free evidence summary you can review and share.
• Routes to Resolver lookup, implementation guidance and supported setup.

Useful for

Useful across many legitimate roles. Commonly used by:

• Robotics integrators and operators
• Safety and reliability engineers
• Platform teams supporting fleets
• Insurers and brokers reviewing deployments

Relevant when before deploying a robot or fleet, you are mapping operator / manufacturer references, you are preparing a safety-case review.

What you can do in under a minute

1. Open or scan the workspace — run ECZ-ID Robotics Trust: Review / Scan Workspace.
2. Review the evidence — observed and not-observed, in plain English.
3. Open implementation guidance or continue supported setup where relevant.

What it looks for

• ROS / robot description (URDF)
• Robot / fleet manifest
• Safety-case evidence
• Deployment context

Example use cases

• Reviewing a ROS / URDF robot before deployment.
• Mapping operator / manufacturer references and safety-case evidence.

Example result

ECZ-ID Robotics Trust  -  deployment evidence
- package.xml ............ ROS package detected
- robot-manifest.yaml .... fleet descriptor detected
- safety-case ............ not observed, review recommended

Example result — when evidence and proof are present

ECZ-ID Robotics Trust  -  with safety-case + reference
- package.xml ............ ROS package detected
- robot-manifest.yaml .... fleet descriptor detected
- safety-case evidence ... present
- public proof reference present (Resolver-verifiable)

What results mean

Results describe observed evidence and public-proof posture — never a safety, approval, certification or compliance verdict:

evidence observed · evidence not observed · review required · no public proof reference found yet · re-check before reliance · your local policy decides.

There is no “pass/fail”. Local policy decides what is sufficient, and you should re-check before reliance.

Recommended next steps

• Show evidence — observed and not-observed, no verdict.
• Build evidence summary — a local, claim-free document you can review and save explicitly.
• Open implementation guidance — Developer Gateway.
• Open Resolver — read-only public proof lookup.
• Request Resolver Proof — for a third-party target (claim-free request).
• Begin supported setup — hand off to TrustOps (metadata only).
• Re-check later — re-run before you rely on a result.

Privacy & permissions

See the bundled PRIVACY.md for the full notice.

Frequently asked questions

Is this extension free?

Yes. Every local check is free — you never need to sign in or pay to run one.

Does it upload my source code?

No. Detection is filename/path only; no source, prompts, secrets or tool payloads ever leave your device, and there is no telemetry.

Does a missing item mean something is wrong?

No. “Evidence not observed” is neutral — your local policy decides what is sufficient.

What does it do when the public interface service is unavailable?

It keeps working from a bundled fallback contract. A refresh is optional and user-initiated.

What it does not do

• No source / prompt / secret upload, and no telemetry.
• Provides local evidence review and guidance only - it does not issue ECZ-ID proof, activate services, grant access, or make approval, safety, insurance or compliance decisions.
• Makes no safety, approval, certification or compliance claim.
• Runs no checkout or payment — commercial actions happen only in TrustOps.

Install & first use

1. In your editor's Extensions view, search for ECZ-ID Robotics Trust (publisher EcoCitizenz) and install it.
2. Open a project and trust the workspace.
3. Run ECZ-ID Robotics Trust: Review / Scan Workspace and review the evidence.

Free vs supported setup

• Free, local-first: observed / not-observed robotics evidence, an evidence summary, and routes — no sign-in and no purchase to run a check.
• Supported setup (TrustOps): maintained ECZ-ID identity, public proof and lifecycle for robotics deployment evidence — relevant when you need a resolver-verifiable result others can check, not just local review.
• You never need to buy anything to get local value; supported setup is a separate, optional step handled entirely in TrustOps.

Machine-readable facts

Links & support

• Resolver (read-only proof): https://resolver.ecocitizenz.org
• TrustOps (supported setup): https://trustops.ecocitizenz.com/start
• Developer Gateway (docs & support): https://developers.ecocitizenz.com
• Privacy: see the bundled PRIVACY.md file

ECZ-ID is independent trust infrastructure. Third-party names describe compatible ecosystems only and do not imply endorsement or affiliation. Local policy decides whether the evidence you review is sufficient.