Skip to content
ECZ-IDIoT
Free Passport: Get a FREE IoT Passport

Authority · Intent · ECZ-ID IoT

ECZ-ID Intent

Define the authorised objective, constraints and validity of what a Passport may do.

ECZ-ID Intent records what a Passport may do — its objective, its constraints and how long that holds — as an Intent that only an owner or administrator of your organisation can authorise. The Passport says who; the Intent says what for.

Configure in TrustOps(opens in a new tab — trustops.ecocitizenz.com)See the tiers and pricesAll IoT products
Type
Authority & evidence
Price
Tiers and prices below, read from TrustOps
Acquired and paid in
TrustOps
Operated in · proved by
Dashboard · Resolver

The problem

Why it matters.

A Passport says what your connected device is and who operates it. It does not say what the connected device is authorised to do, so every counterparty and reviewer has to ask, and the answer lives in emails and contracts.

Built for

  • Operators who need to state what an ECZ-ID entity is authorised to do, not only who it is.
  • Teams preparing an authorised boundary for ECZ-ID Intent Control to evaluate actions against.
  • Reviewers who ask who authorised an entity's objective, and for how long.

What changes

  • The authorised objective, constraints and validity in one place, attached to the Passport.
  • A clear line between identity (the Passport) and authority (the Intent).
  • An authorised boundary that ECZ-ID Intent Control can evaluate a proposed action against.

What you receive

Concrete deliverables, not a vague trust score.

  • Covered places for authorised Intents, set by the plan.
  • Each Intent's objective, constraints and validity, recorded against the Passport it applies to.
  • Authorisation by an owner or administrator of your organisation, and by no one else.
An Intent
Applies to
ECZ-XX-XXXXXX::IOT_DEVICE-XXXXXX
Objective
What the Passport is authorised to do
Constraints
The limits that objective holds within
Validity
How long the authorisation holds
Authorised by
An owner or administrator of your organisation

Illustrative structure with placeholder values. Intents are defined and authorised in the Dashboard.

How it works

A short path from need to something usable.

  1. Choose the Passport an Intent applies to.

  2. Define its objective, its constraints and its validity.

  3. An owner or administrator of your organisation authorises it.

  4. ECZ-ID Intent Control can then evaluate a proposed action against it.

How it relates to your Passport

An Intent attaches to a Passport and never changes it: the ECZ-ID, its Resolver record and your Parent tier stay as they are. Identity is not authority — the Passport says who, the Intent says what for.

Use cases

  • Stating what one of your connected devices is authorised to do before a counterparty relies on it.
  • Giving ECZ-ID Intent Control a boundary to evaluate proposed actions against.
  • Answering a reviewer who asks who authorised an objective, and until when.

Tiers and price

What it costs, and where you buy it.

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal. Read from the TrustOps projection generated . All pricing

After purchase

  1. TrustOps acquires

    Configure and buy in TrustOps, which owns payment and entitlement.

  2. Dashboard operates

    The entitlement appears in your Dashboard, where you operate it.

  3. Resolver proves

    Public facts stay on the Resolver; buying never changes what a record proves.

Privacy, security and evidence

What is collected, published and kept.

  • Only an owner or administrator of your organisation can authorise an Intent.
  • Payment authorises nothing; buying a plan only adds covered places.
  • ECZ-ID does not sit in your execution path and does not enforce an Intent.

Boundaries

The claims stop here.

  • A Passport is not an Intent authorisation, and payment authorises nothing.
  • An Intent is authorised only by an owner or administrator of your organisation.
  • An Intent is enforced only where an enforcement point you run mediates the action; ECZ-ID does not enforce it.
  • Intent coverage is not AEC capacity.

Integrations and questions

Works with what you already run.

  • ECZ-ID Intent Control, which evaluates a proposed action against an Intent.
  • Dashboard: define Intents and have them authorised.
  • The enforcement points you already run, which decide whether an action goes ahead.

Build and integrate it from code: IoT & Connected Systems(opens in a new tab — developers.ecocitizenz.com)

Does my Passport already authorise what my connected device does?
No. A Passport is not an Intent authorisation. It says who the connected device is and who operates it; an Intent says what it may do.
Does buying a plan authorise anything?
No. Payment authorises nothing. An Intent is authorised only by an owner or administrator of your organisation.
Will ECZ-ID stop an action that falls outside an Intent?
No. An Intent is enforced only where an enforcement point you run mediates the action. ECZ-ID Intent Control evaluates proposed actions; it does not sit in your execution path.

Related

Keep the identity free. Add this when the outcome is worth it.

Your IoT Passport stays free. ECZ-ID Intent sits above it and is acquired in TrustOps.

Configure in TrustOps(opens in a new tab — trustops.ecocitizenz.com)