Skip to content
ECZ-IDDevelopers

Developers

Changelog

What changed on this site, newest first. Product changes in ECZ-ID Core, TrustOps and the Resolver are announced by those surfaces.

  1. V5.1: production truth, onboarding and orientation

    • Production status re-measured against Core, the Resolver and TrustOps. Evidence and LedgerCore are now labelled not publicly retrievable, because production ledger anchoring is not yet proven. Graph Intelligence is labelled not generally available. Proven bindings and partner delegation are stated as not yet released.
    • A six-step Get started path, from what ECZ-ID is to the guided flow for your machine. The five-minute introduction now shows the expected output of every command, measured that day.
    • Guided flows show a progress bar naming the step being read.
    • The floating Quick routes navigator is restored to its original form: the V5 routes as one filterable vertical list, with its own scroll, opening above the trigger, a separate one-click Back to top control, and a short group for the page being read. The homepage hero returns to one technical object, the live record.
    • Concepts are mapped onto the Accountability Chain. The consequence boundary has its own diagram, and Guides are grouped by what you need to do. Each Reference page states its contract class: Core contract, public Resolver projection, public schema, or documented ahead of release.
    • Tools are grouped as inspect, verify, build, understand and signed-in operation. SDKs and packages list the editor extensions, the plugin collection and the Python tools.
    • Developer Trust gains a starting choice (MCP, agents, or both), a diagram of the two sides of the connection, and a first sixty seconds that uses each extension’s own commands.
    • One EcoCitizenz emblem family, cut from the founder master, used for the header, footer, favicons, app icons and the sharing image.

    Get startedConceptsReferenceDeveloper Trust

  2. V5: Reciprocal Trust Infrastructure for the Machine Economy

    • New information architecture: Get started, Concepts, Quickstarts, Guides, SDKs, Reference, Tools, Developer Trust and Changelog.
    • The Accountability Chain as the organising model: identity, authority, delegation, Intent, current state, decision, action, Receipt, re-check.
    • First-class technical homes for Intent, IntentControl, decisions, enforcement modes, Receipts, evidence and LedgerCore, each labelled with its production status.
    • Seven family quickstarts built from the live TrustOps families contract, each with a relying-party check measured against production.
    • Reference pages for the ECZ-ID format, Passport model, bindings, the Intent envelope, the decision contract, the Receipt, ReasonCodes (including the public rcv-1.0.0 registry), ResultStates and the Resolver output.
    • Catalogue-era pages (solution routes, domains, the child Passport catalogue, packages and flows) preserved at their addresses with a notice, and listed at /legacy/.
    • The retired legacy name for IntentControl removed from every public surface; a build gate keeps it out.
    • Seven guided flows, one per Passport family, each carrying one kind of machine through the Accountability Chain with a status, an example, the expected output and its proof boundaries at every step.
    • The Accountability Chain in its full ten-link form, adding Evidence and Re-verify.
    • MCP Trust and Agent Trust product pages restored to lead with the product, with Community, Pro and Developer Trust Pro side by side, capabilities matched to the shipped extensions, and a Developer Trust Pro page for the one-licence bundle.
    • A Utility Rail with site search across documentation, guided flows, ReasonCodes and ResultStates.
    • Developer Trust prices and IntentControl, Intent and Receipt status checked against the TrustOps commerce catalogue by a build gate.

    Guided flowsConceptsDeveloper Trust ProPreserved pages

  3. A quickstart that works

    • One integration end to end at /quickstart/, every command run against production first.
    • A runnable zero-dependency example and a worked first-party interoperability example.
    • The Digital Entity Graph in the quickstart uses the estate’s own model.

    First integration

  4. Graph Intelligence documentation

    • Public documentation of Graph Intelligence as used in the signed-in TrustOps console.

    Graph Intelligence

  5. Plugins, and our own Business Passport in the footer

    • The /plugins/ page for the ECZ-ID agent plugin estate, with support, privacy and terms for each plugin.
    • EcoCitizenz Ltd’s live Business Passport badge in the footer, linking to its Resolver record.

    Plugins

  6. Universal Install

    • Every route for installing or connecting ECZ-ID verification, generated from the version constants, including Cursor.

    Universal install

  7. First-party machine manifests

    • ecz-agent.json and ecz-mcp.json published under the operator ECZ-ID, with ecz-agent.json stating plainly that this site is not an agent.
    • An AI catalog entry for the first-party Trust MCP server.

    Machine manifests

  8. Developer Trust

    • The Developer Trust suite pages, the free MCP Trust and Agent Trust extensions, and the Preflight report.

    Developer Trust

  9. Python tools

    • The /python/ page for the ECZ-ID Python tool family.

    Python tools