THE CURRENT ECZ-ID MODEL, IN PLAIN ENGLISH.

ECZ-ID is Reciprocal Trust Infrastructure for the Machine Economy: an independent identity, authority, Intent, decision and evidence layer around consequential machine activity.

Agent, MCP, Plugin, API, IoT, SDK and Service & Workload. They sit under the accountable organisation's Business Passport. Product categories, robot classes, custody routes and risk-policy products are not additional launch Passport families.

The Business Passport is the accountable parent organisation identity. Declared starts free. Verified and Assured provide stronger organisation-verification tiers where the reliance context requires them.

No. Identity is not authority. A Passport does not automatically establish permission, delegated authority, safety, compliance or approval. Authority and Intent are distinct parts of the accountability chain.

Permission describes what a credential or system can reach. ECZ-ID Intent describes the authorised objective and its bounds: what the actor is meant to do, where, within what constraints and for how long.

IntentControl is the decision/control layer that evaluates a proposed action against identity, authority, delegation, Intent, policy, current state and constraints on a configured decision path. It does not mean ECZ-ID executes the customer's action.

PulseGuard is the current-state monitoring capability: it helps answer what relevant trust state is now, where configured.

Watch is the change-monitoring capability: it helps answer when something relevant changes, where configured.

A Receipt is a retrievable evidence object for what the recording system recorded about an event, decision, action, result or state. A valid Receipt does not automatically prove every underlying real-world assertion was true.

LedgerCore is blockchain-backed integrity and retention infrastructure for eligible evidence. Where the configured path supports it, eligible evidence can be anchored into confidential, tamper-evident ledger infrastructure. Integrity does not certify underlying truth.

Use TrustOps for acquisition, setup, entitlement, activation and lifecycle. Start with the free identity layer, then add paid operating capabilities only where the consequence requires them.

Use Resolver for public read-only proof. Re-check the current published state at the time of reliance rather than treating a past screenshot, badge or cached response as current truth.

Developer Gateway explains contracts, schemas, quickstarts, guided flows and integration patterns. It issues nothing and proves nothing; Core determines canonical state and Resolver exposes public proof.

No. ECZ-ID is provider-neutral by position. It binds, integrates, resolves, interprets and proves around the systems beneath it rather than replacing every identity, protocol, cloud or payment system.

No. ECZ-ID provides accountable state, decision and evidence infrastructure. Regulators, auditors, insurers, buyers and other relying parties retain their own obligations, policy and judgement.