ECZ-ID Drone & Mobility Pack
Drone, robotaxi / freight insurance-readiness and cloud evidence with the ECZ-ID Hub.
An ECZ-ID Extension Pack: one install adds the specialists below. The pack itself adds no scanner — each specialist runs locally and independently, and you can install components on their own instead.
Useful for
Useful across many legitimate roles. Commonly used by:
- Drone and autonomous-mobility operators
- Brokers and risk engineers
- Compliance and platform teams
Relevant when you are assembling drone and robotaxi / freight evidence, you are reviewing cloud trust for the supporting platform.
Included extensions
- ECZ-ID Hub (
ecocitizenz.eczid) — the ECZ-ID trust cockpit — routes you to the right specialist.
- Drone Insurance Readiness (
ecocitizenz.eczid-drone-insurance) — drone / UAS evidence for insurance review.
- Robotaxi & Freight Insurance Readiness (
ecocitizenz.eczid-robotaxi-freight-insurance) — autonomous fleet evidence for insurance review.
- Cloud Trust (
ecocitizenz.eczid-cloud-trust) — cloud / IaC surfaces and identity references.
Common workflows
- Assemble drone and robotaxi / freight evidence packs.
- Review cloud trust for the supporting platform.
Installation outcome
- Installs 4 ECZ-ID extensions (including the Hub) in one step.
- Every check stays free and local-first; nothing is uploaded and there is no telemetry.
- The Hub gives one cockpit; each specialist also works standalone.
Example result
ECZ-ID Drone & Mobility Pack - installs 4 extensions
- ECZ-ID Hub
- Drone Insurance Readiness
- Robotaxi & Freight Insurance Readiness
- Cloud Trust
Run: ECZ-ID: Show All Specialists
First-use path
- Install the pack and trust your workspace.
- Run ECZ-ID: Show All Specialists from the Hub to see what is installed.
- Run a specialist's Review / Scan Workspace and review the evidence.
Privacy & permissions
Local-first. Filenames and paths only. No source / prompt / secret upload. No telemetry. Respects VS Code Workspace Trust. Each included extension makes no safety, approval, certification or compliance claim.
FAQ
Can I install the components separately? Yes — every extension in this pack is also available on its own.
Does the pack add any new scanning? No. A pack only groups extensions; all checks come from the specialists.
Free vs supported setup
- Free, local-first: local evidence review — no sign-in and no purchase to run a check.
- Supported setup (TrustOps): maintained ECZ-ID identity, public proof and lifecycle for mobility insurance-readiness — 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.
Python / CLI
Prefer Python, CI or terminal automation?
python -m pip install ecz-id-robotics
ecz-id-robotics --help
The Python tools run locally and inspect, explain and route only — the same role boundary as this extension. They do not issue an ECZ-ID, create public proof or replace Resolver proof.
Machine-readable facts
| Field |
Value |
| Product |
ECZ-ID Drone & Mobility Pack |
| Identity |
ecocitizenz.eczid-pack-drone-mobility |
| Publisher |
EcoCitizenz |
| License |
Free; see the bundled LICENSE.txt |
| Version |
0.1.1 |
| Page family |
extension-pack |
| Purpose |
Drone, robotaxi / freight insurance-readiness and cloud evidence with the ECZ-ID Hub. |
| Applicable audiences |
Drone and autonomous-mobility operators; Brokers and risk engineers; Compliance and platform teams |
| Applicable scenarios |
you are assembling drone and robotaxi / freight evidence; you are reviewing cloud trust for the supporting platform |
| Members |
ecocitizenz.eczid, ecocitizenz.eczid-drone-insurance, ecocitizenz.eczid-robotaxi-freight-insurance, ecocitizenz.eczid-cloud-trust |
| Primary command |
ECZ-ID: Show All Specialists |
| Inputs |
None — a pack contains no scanner; each member detects its own artefacts |
| Outputs |
Installs the listed extensions (including the Hub) in one step; each member produces its own outputs |
| Independent management |
Every member can be enabled, disabled or uninstalled on its own |
| Data handling |
Filenames and paths only; no source / prompt / secret upload; no telemetry; retention none |
| Network behaviour |
None — a pack runs no code; each installed extension manages its own |
| Result states |
evidence observed; evidence not observed; no public proof reference found yet; review recommended; re-check before reliance; local policy decides |
| Limitations |
Does not issue proof, approve, certify, insure, underwrite, determine compliance, or run checkout |
| Canonical machine discovery |
https://machine.ecocitizenz.org/.well-known/ecz-machine.json |
| Public proof |
https://resolver.ecocitizenz.org |
| Documentation |
https://developers.ecocitizenz.com |
| Supported setup |
https://trustops.ecocitizenz.com/start |
| Re-check |
Re-run before reliance |
Need help choosing the right ECZ-ID route?
Use ECZ-ID GPT guidance: https://trustops.ecocitizenz.com/start#gpt-guidance
Route guidance only. TrustOps handles setup; Backend/Core writes truth; Resolver proves public state. Local policy decides reliance. Re-check before reliance.
Support & links
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.