EM-XCT-07 · Shared contract · W0
Action, authority and delegation to an agent
The form of a permitted action, its preconditions, effect, confirmation and idempotency.
Partially published; research continues
Claude: independent-study-and-r3-code-adoption-audits-complete; Grok: independent-study-and-r3-recovered-code-adoption-audits-complete.
Published results
Research note, in Russian: EM-XCT-07 remains partial: real host authority/issuer-standing and delegation evidence; broader action parameter/effect adapters, remote effects and ambiguous external outcomes; protected disclosure, continuity and recovery; quotas/rollover; stronger historical clock validation and missing edge tests; incremental/existing-Dimension native bindings and generic composer integration. Each needs a separate bounded implementation and acceptance; no production authorization is provided.
Subject boundary and candidate types
- ActionContract
- ActionRequest
- ActionResult
- AuthorityBinding
Deep research 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?
Verifiable invariants
- A description of an action does not grant permission
- A retry honors idempotency
- A result has an observable confirmation
End-to-end acceptance scenario
A repeated request creates a single effect, a prohibited transition is rejected, and a proposed action remains unexecuted.
Negative case
An agent publishes a model merely because a document describes a Publish action.
Approaches to compare
- Current Vercy protocol/MMAS/whole-object and the published WM-XCT
- W3C PROV/SKOS/SHACL/ODRL where applicable
- Practice of source connectors, versioned schemas and policy enforcement
Candidates in the live catalogue
- WM-XCT-002 · Access Contract / Consent · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-XCT-029 · Obligation / Commitment · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.