← Back to catalogue
Published

Action, authority and delegation to an agent

EM-XCT-07 · em-xct-07

Support accountable action by linking each request and observed result to explicit authority, applicable approval and delegated limits.

Enterprise profiles Enterprise contract EnterpriseXCT

Bundle → Layer → Finding → Questions Filled

2 bundles · 2 layers · 4 findings · 10 questions

Action contract Describe the authority, conditions and intended effect of a concrete action.

Contract and authority

Assess an action's declared requirements without granting execution authority.

Action contract

State the preconditions, intended effect and evidence required for confirmation.

  1. Which preconditions does this action contract require before execution?
  2. What effect and confirming evidence does this action contract specify?

Authority binding

Identify the principal, delegated limits and applicable approval basis.

  1. Which actor and authorizing principal does this authority binding identify?
  2. What delegated scope, validity period and limits does this authority binding specify?
  3. Does this request record reference applicable standing approval or require separate per-request approval?
Requests and results Distinguish proposals, execution evidence and retry guarantees.

Request lifecycle

Assess the recorded status and outcome of a concrete action request.

Proposal or execution

Separate approval status from execution status and rejected transitions.

  1. Does this request record represent a proposal awaiting approval or an authorized instruction to execute?
  2. Which prohibited transition, if any, does this request record show as rejected, and for what reason?

Idempotent result

Describe the scope and limits of duplicate-effect prevention and result evidence.

  1. What duplicate-effect guarantee and limitations does this request's retry contract record?
  2. What principal or service scope, operation, validity window and payload compatibility rules does this request record bind to its idempotency key?
  3. What observable evidence does this result record provide for completion or an unresolved outcome?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise contract
Entry kind
contract
Domain
EnterpriseXCT
Industry
Cross-industry
Tags
EM-XCT-07W0contractActionContractActionRequestActionResultAuthorityBinding

What it is Filled

The form of a permitted action, its preconditions, effect, confirmation and idempotency.

Why it exists Filled

Support accountable action by linking each request and observed result to explicit authority, applicable approval and delegated limits.

Distinguishing features Filled

  • A description of an action in a model or document never grants permission to perform it.
  • Authority is described through an explicit binding to a principal and the limits delegated to an agent.
  • A proposed action and an executed action are separate states with separate records.
  • Duplicate-effect prevention depends on the recorded retry contract, including key scope, validity window and payload compatibility.
  • Standing approval and per-request approval are distinct recorded bases for assessing authority.

What robots and AI may and may not do Filled

Must not

  • Treat this contour or an action description as authority to execute or retry an action.
  • Treat a proposal as approved without an applicable recorded approval basis.
  • Infer duplicate-effect prevention from the presence of an idempotency key alone.
  • Report an action as complete without observable supporting evidence.
  • Represent an action outside delegated limits as authorized.

Only with a human decision

  • Resolve approval gaps for irreversible or external actions when applicable standing approval does not cover the request.
  • Approve a new authority binding or an expansion of delegated limits.
  • Review an unobserved result and obtain supporting evidence before marking the action complete.

May

  • Describe a concrete action's proposed effect, preconditions and required confirmation evidence.
  • Assess a concrete request against its recorded authority binding and delegated limits.
  • Assess whether standing approval covers a concrete request or whether per-request approval remains required.
  • Describe and assess a concrete request's retry contract and duplicate-effect guarantees.
  • Report the evidence and uncertainty recorded for a concrete action result.

Moral aspects Filled

  • Unauthorised agent actions can cause financial, legal or reputational harm to the principal.
  • Accountability must remain with the person or organisation that delegated authority.

Who is affected

  • Principals who delegate authority
  • People affected by the action
  • Operators of the systems the agent acts on

Owners Filled

Steward

An enterprise delegation steward is accountable for authority bindings, approval records, action requests and execution evidence.

Master systems

  • An authorization registry maintains authority bindings and delegated limits.
  • An approval management system maintains standing and per-request approval records.
  • An action management system maintains requests and execution states.
  • An audit evidence repository maintains execution evidence and its provenance.

Links to other meta-models Filled

references

  • WM-XCT-002 - conceptual-candidate
  • WM-XCT-029 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • An action contract is identified by action name and version, and a request has its own request identifier.
  • An idempotency key is interpreted within its declared principal or service scope, operation, validity window and payload compatibility rules.
  • Each authority binding has a unique identifier and records its principal, agent, action, validity period and delegated limits so overlapping grants remain distinguishable.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition required Filled

  • An action contract lists preconditions, effect, confirmation requirements and retry rules.
  • An action contract is distinguishable from an interface operation description or a permission record.

Capabilities and actions required Filled

  • A request can be assessed against its authority, approval basis and preconditions.
  • A recorded retry contract supports assessment of whether a repeated request is protected against duplicate effects.
  • An action result can be traced to its authority binding and confirmation evidence.

Hazards and failure modes required Filled

  • An action description can be mistaken for execution authority.
  • Unsafe retries can cause duplicate payments or publications.
  • Proposals can be mistaken for executions in reports.
  • Unsupported confirmation can conceal an unresolved action outcome.

Standards and interfaces optional Filled

  • RFC 6749 from the Internet Engineering Task Force defines the OAuth 2.0 authorization framework.
  • The OpenAPI Specification from the OpenAPI Initiative describes interface operations.
  • The Open Digital Rights Language from the World Wide Web Consortium represents permissions, prohibitions and duties.

Context of use required Filled

  • Action records describe agents or automations acting on behalf of people or organizations.
  • Authority and confirmation evidence are relevant to payments, publications and filings.

Sources Filled

  1. Current Vercy protocol/MMAS/whole-object and the published WM-XCT
  2. W3C PROV/SKOS/SHACL/ODRL where applicable
  3. Practice of source connectors, versioned schemas and policy enforcement
  4. ODRL Information Model 2.2 - Carried over from the published world model wm-xct-002-access-contract-consent; checked live (HTTP 200) on 2026-10-09.
  5. ODRL Vocabulary & Expression 2.2 - Carried over from the published world model wm-xct-002-access-contract-consent; checked live (HTTP 200) on 2026-10-09.
  6. Guidelines 05/2020 on consent under Regulation 2016/679, Version 1.1 - Carried over from the published world model wm-xct-002-access-contract-consent; checked live (HTTP 200) on 2026-10-09.

Open questions

  • Who is entitled to perform the action?
  • How to repeat a request without a double effect?
  • How to distinguish a proposal from an execution?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-xct-07/brief.json, ver-cy/world-models/card-supplements/em-xct-07.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.