ecz-id 0.1.1

ECZ-ID shared core: result contract, reason codes, safe inspection utilities and plugin discovery. Inspects, explains and routes only.

ECZ-ID Shared Core (ecz-id)

The shared core of the ECZ-ID PyPI family. It provides:

• the public result contract (ecz_id.result) that visibly separates local configuration/evidence posture from public Resolver evidence posture;
• the stable reason-code register (ecz_id.reason_codes);
• safe bounded file enumeration (ecz_id.fs) — never follows symlinks, never escapes the root, never executes discovered code;
• redaction (ecz_id.redaction) applied to every export;
• URL validation and SSRF controls (ecz_id.urlsafety) — https-only, no internal hosts, no private IPs;
• offline mode (ecz_id.offline);
• report exporters (ecz_id.report) — JSON, Markdown, text;
• the contextual next-action selector (ecz_id.next_actions) — routing only;
• report exporters including SARIF (ecz_id.report);
• the machine-readable integration layer (ecz_id.quiet_interface) — the packaged manifest, report envelope, footer and disclosure scan;
• shared inspection assembly (ecz_id.inspection), the shared specialist CLI (ecz_id.speccli), the Resolver client (ecz_id.resolver) and compare / share-guidance helpers (ecz_id.sharing);
• Central Machine Interface manifest models (ecz_id.machine_interface);
• plugin discovery (ecz_id.plugins) via the ecz_id.plugins entry-point group.

What this family never does

These packages inspect, explain and route only. They never issue or activate an ECZ-ID, never determine BOUND, never calculate carts or prices, never create proof, never execute discovered project, agent, MCP or robot code, never upload arbitrary source, and use no hidden telemetry.

No result is a safety, certification, approval, compliance, insurance or premium decision. Missing public proof is neutral — it does not mean unsafe. Local policy decides. Re-check before reliance.

CLI

ecz-id (owned exclusively by this distribution):

ecz-id about
ecz-id version
ecz-id plugins [--json]
ecz-id capabilities --json
ecz-id routes --json
ecz-id manifest --json          # structured machine-readable manifest
ecz-id explain [ECZ-2001]

Machine-readable integration

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

Each installation includes structured machine-readable metadata for automation, CI and supported integrations. The shared core provides the packaged manifest, the report machine_interface envelope and the family-wide disclosure scan.

The core 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.

• 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

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.