ECZ-ID Compliance Risk

Surface operational-resilience and audit-evidence gaps without claiming compliance.

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

• Surfaces operational-resilience and audit-evidence artefacts.
• Plain-English posture per evidence gap.
• Routes to Resolver lookup and supported setup.

Useful for

Useful across many legitimate roles. Commonly used by:

• Compliance and operational-resilience leads
• Risk and audit teams
• Engineering leads preparing DORA-style evidence
• Reviewers gathering control evidence

Relevant when you are assembling resilience or audit evidence, you are preparing for a review, an auditor asks where the evidence lives.

What you can do in under a minute

1. Open or scan the workspace — run ECZ-ID Compliance Risk: Scan Workspace.
2. Review findings in plain English — grouped, with neutral posture.
3. Open Resolver guidance or continue supported setup where relevant.

What it looks for

• Operational-resilience and audit/evidence artefacts (policies, control docs).
• Evidence references relevant to frameworks such as DORA — without judging compliance.
• Whether a resolver reference is present for the evidence surface.

Example result

ECZ-ID Compliance Risk  -  evidence surfaces
- operational-resilience policy . present
- audit / control docs .......... partial, review recommended
Posture: evidence posture only - never a compliance verdict

What results mean

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

resolvable · partial public proof · no public proof reference found yet · review recommended · 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

• Inspect the finding — plain-English detail, no verdict.
• Copy verification guidance — a claim-free snippet you can share.
• Open Resolver — read-only public proof lookup.
• Continue supported setup — hand off to TrustOps (metadata only).
• Open documentation — Developer Gateway.
• 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. No source, prompts, secrets or tool payloads ever leave your device, and there is no telemetry.

Does it read my file contents?

It reads filenames and paths during a scan. It only reads the contents of a file you explicitly ask it to inspect (for example an ecz-*.json you choose to validate).

Does a missing proof reference mean something is unsafe?

No. “No public proof reference found yet” is neutral — it is not a verdict of “unsafe”. It only means resolver-verifiable public proof was not detected.

What does Resolver do?

Resolver is a read-only public proof lookup. The extension can open it so you can check public proof yourself; the extension never writes, activates or decides anything.

Do I need an ECZ-ID before using the extension?

No. You can run every local check without one. An ECZ-ID is only relevant if you later choose supported setup in TrustOps.

What happens when I continue supported setup?

The extension hands off to TrustOps with metadata only. It runs no checkout itself; TrustOps handles acquisition, setup and lifecycle.

Can this extension make a compliance or approval decision?

No. It surfaces posture and routes you to proof. Local policy decides sufficiency; it never certifies, approves or guarantees.

Does it certify DORA compliance?

No. It makes no compliance claim and certifies nothing. It surfaces operational-resilience and audit-evidence gaps for your review.

What evidence artefacts can it surface?

Operational-resilience and audit-evidence references found in local files; it never asserts they satisfy any regulation.

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. Never claims DORA, regulatory or legal compliance, and makes no compliance verdict. It surfaces evidence gaps for your review.
• 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 Compliance Risk (publisher EcoCitizenz) and install it.
2. Open a project and trust the workspace.
3. Run ECZ-ID Compliance Risk: Scan Workspace and review the grouped findings.

Free vs supported setup

• Free, local-first: detected evidence gaps with neutral posture (never a compliance verdict) and routes — no sign-in and no purchase to run a check.
• Supported setup (TrustOps): maintained ECZ-ID identity, public proof and lifecycle for operational-resilience evidence posture — 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-dora
ecz-id-dora --help

• Open the matching Python package: https://pypi.org/project/ecz-id-dora/
• Explore all 10 ECZ-ID Python tools: https://developers.ecocitizenz.com/python

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

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.

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.