Identity is referenced
The machine keeps its native identity in the system where it operates. ECZ-ID references that identity; it does not issue a competing execution identity.
The ECZ-ID model
Customer authority first. Machine delegation second.
ECZ-ID works alongside RMM, PSA, IAM and security controls. It records customer authority, machine delegation, state and evidence; execution remains with the systems you already operate.
The invariant
Operator Delegation is always a subset of Customer Authority
OPERATOR DELEGATION SCOPE ⊆ CUSTOMER AUTHORITY SCOPE
If the client has not authorised a surface or action class, the operator cannot delegate it to a machine under that authority. Narrowing, suspension, revocation and replacement remain explicit state changes.
Accountability chain
One connected record from client authority to independent re-check
- Customer
- Customer Authority
- MSP / Accountable Operator
- Operator Delegation
- Machine Actor
- Native Identity
- MCP / API / Action Surface
- Evidence
- Current State
- Independent Re-check
Operating records
The model keeps distinct questions distinct
Authority is client-specific
Customer Authority records what one client authorised, over which surfaces and action classes, with effective, review and expiry dates where applicable.
Delegation is bounded
The MSP's Operator Delegation to a machine actor must stay inside the Customer Authority scope. It cannot silently widen the client's grant.
State remains answerable
Active, suspended, revoked, superseded and expired states are connected to a history of state events rather than overwritten.
Evidence stays referential
Evidence references point back to the source system and event. ECZ-ID does not duplicate the telemetry or become the action path.
Clients can re-check
A scoped client view and Resolver provide the current answer without exposing another client's record or the MSP's operating console.
Integration
Connected to the stack, outside the execution path
RMM and PSA operate the service relationship; IAM provides native identities and technical permissions; SIEM, EDR and MDR retain execution telemetry. ECZ-ID records the separate customer-authority and machine-delegation chain.