← Back to catalogue
Published

Enterprise Action Requests

vr.profile.enterprise-action-requests · enterprise-action-requests

Describe governed actions, preserve immutable intent and validate a bounded local execution history without deriving permission from descriptions.

Enterprise profiles Cross-cutting context EnterpriseAction and authority
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Filled

5 bundles · 10 layers · 26 findings · 52 questions

Definition Definition of company action requests.

Operation semantics

Questions and evidence for operation semantics.

Operation boundary

Exact immutable ActionDefinition and parameter contract

  1. Which versioned operation is described? host-guidance
  2. Is it descriptive-only or executable in this binding? host-guidance

Neighbor alignment

Pinned comparison and explicit relation

  1. Does K2 actClass overlap this operation? host-guidance
  2. Does a capability or obligation authorize it? host-guidance

Definition governance

Questions and evidence for definition governance.

Revision and stewardship

Stable definition ID, revision chain, steward, master and validity

  1. Who governs this definition? host-guidance
  2. What changed across revisions or retirement? host-guidance
Request Request of company action requests.

Intent and identity

Questions and evidence for intent and identity.

Intent boundary

Closed immutable intent and exact definition pin

  1. What exact effect is being requested? host-guidance
  2. What is the smallest valid request? host-guidance

Retry identity

Retained actor-scoped key hash and intent bytes

  1. How can a caller recover a lost response? host-guidance
  2. Does a changed body reuse the old key? host-guidance

Host identity

Host-minted request ID and submission event

  1. Which Dimension owns this request? host-guidance
  2. Who mints its ID? host-guidance
Authority Authority of company action requests.

Authority basis and scope

Questions and evidence for authority basis and scope.

External authority basis

Host rule, issuer-standing Pin and external basis Pin

  1. Who can act for whom? host-guidance
  2. Who verified the issuer has standing? host-guidance

Scope intersection

One complete matching pair of scopes

  1. Are both principal and actor allowed? host-guidance
  2. Are action, resource, purpose and audience exact? host-guidance

Current decisions and disclosure

Questions and evidence for current decisions and disclosure.

Fresh decision

Policy revision, control sequence, decision and rule digests

  1. Which policy applied at this try? host-guidance
  2. Was the definition still available? host-guidance

Disclosure

Current read decision independent of execute

  1. Can this caller see the outcome now? host-guidance
  2. Could an error reveal hidden existence? host-guidance
Execution Execution of company action requests.

Admission and local effect

Questions and evidence for admission and local effect.

Submission versus proposal

Submission, delivery and try event identities

  1. Has intent been admitted or merely proposed? host-guidance
  2. Did a delivery actually lead to a try? host-guidance

Atomic effect

Before/after revisions and one local transaction

  1. What changed in the resource? host-guidance
  2. Are the key, effect and receipt committed together? host-guidance

Replay

Retained receipt and immutable digest

  1. Has this request already produced an effect? host-guidance
  2. Did the resource change in the meantime? host-guidance

Terminal and compensating operations

Questions and evidence for terminal and compensating operations.

Deadline

Half-open request deadline and terminal history

  1. Can a first effect still occur? host-guidance
  2. Is an old committed receipt being mistaken for expiry? host-guidance

Cancellation

Current cancel decision and serialized disposition

  1. Can a pending request be cancelled? host-guidance
  2. Which terminal operation won the race? host-guidance

Compensation

Original receipt, exact old labels and current revision

  1. Which effect is to be compensated? host-guidance
  2. Has intervening work changed its revision? host-guidance
Evidence Evidence of company action requests.

Observer knowledge and correction

Questions and evidence for observer knowledge and correction.

Observer knowledge

Observation event and identified observer

  1. What does the caller know about the result? host-guidance
  2. Is uncertainty local to the observer? host-guidance

Correction

Linear correction edge and reason

  1. Which observation is corrected? host-guidance
  2. Does the predecessor still exist unchanged? host-guidance

Master history and continuity

Questions and evidence for master history and continuity.

Mastership

One SQLite master and labeled native evidence

  1. Which store is authoritative for execution? host-guidance
  2. Is a native export being treated as a second master? host-guidance

History validation

Replay report and externally expected manifest root

  1. Do the records form a coherent history? host-guidance
  2. Does this prove authenticity or the latest cut? host-guidance

Export recovery

Exact manifest, snapshot and deterministic native files

  1. Was every file captured at one cut? host-guidance
  2. Can an interrupted export be resumed safely? host-guidance

Retention

Terminal-only key retirement event and retained key slot

  1. Can this key be reused after retirement? host-guidance
  2. Which evidence is retained? host-guidance

Restore continuity

Recovery decision and external continuity root

  1. Could this be a coherent old database? host-guidance
  2. What external anchor establishes the latest state? host-guidance

Representation and adoption

Questions and evidence for representation and adoption.

Byte identity

Explicit Python encoding and raw artifact SHA

  1. Which canonical bytes define equality? host-guidance
  2. Are ordering or Unicode silently normalized? host-guidance

Native binding

Three synthetic installation reports and exact file readback

  1. Do stored native records match the semantic snapshot? host-guidance
  2. Did the companion validator run after outer checks? host-guidance

Adoption boundary

Descriptive minimum profile, synthetic execution profile and limits

  1. Which use cases are useful today? host-guidance
  2. Which production responsibilities remain external? host-guidance

Classifiers Filled

Family
Enterprise profiles
Category
Cross-cutting context
Entry kind
companion-contract
Navigation path
NAV.XCT
Domain
EnterpriseAction and authority
Industry
Cross-industry
Tags
EM-XCT-07actionrequestauthoritydelegationidempotencyreceiptcompensation
Also called
Action authority and delegation, ActionDefinition, ActionRequest, EM-XCT-07

What it is Filled

A companion contract for a Company Dimension that records governed actions: what an action is, who asked for it on whose behalf, under which authority, and what local execution happened, with immutable intent and receipts. It describes and validates; it does not run external side effects.

Why it exists Filled

Describe governed actions, preserve immutable intent and validate a bounded local execution history without deriving permission from descriptions.

Distinguishing features Filled

  • Separates the description of an action from the permission to perform it: a defined action grants nothing by itself.
  • Keeps the requested intent immutable and digest-bound, so a retry can be proven to be the same request.
  • Records execution as a bounded local history with receipts, unlike a workflow engine that runs the action.
  • Treats compensation as a new request with its own key, never as an undo of a committed effect.

What robots and AI may and may not do Filled

Must not

  • Treat an action definition, a role name or a neighbouring model as permission to act.
  • Fill a missing actor, principal, purpose or resource revision by guessing.
  • Reapply an old effect when asked for evidence, or claim an undo after commit.
  • Combine partial grants from different rules into one permission.
  • Produce external side effects through the local adapter; those need their own contract.

Only with a human decision

  • Granting submit permission for a proposed action.
  • Approving compensation for a committed effect.
  • Resolving a request whose context no longer matches the original intent.

May

  • Draft an action request with actor, principal, resource revision, purpose and audience filled from verified context.
  • Retry a request with the same intent and idempotency key after continuity is established.
  • Cancel or let expire a request that is still pending.
  • Return retained evidence of a past execution to a caller allowed to read it.

Moral aspects Filled

  • An agent acting for a person can cause harm in that person's name; the principal must be explicit and verifiable.
  • Denied reads must return a uniform withheld response so the record does not leak who asked for what.
  • Execution history is evidence about people's decisions and must not be rewritten to hide responsibility.

Who is affected

  • Principals on whose behalf actions are requested
  • People affected by the executed action
  • Operators accountable for the host system

Owners Filled

Steward

The host operator of the Company Dimension holds authority over admission and execution; the action definition belongs to the owner of the domain process it describes.

Master systems

  • Host identity and access management for actors and principals
  • Domain system of record for the resource being acted upon

Links to other meta-models Filled

references

  • WM-XCT-002 - 0.3.0-research.1
  • WM-XCT-029 - 0.3.0-research.1
  • WM-XCT-001 - 0.3.1-enterprise.1

aligned

  • vr.wm-xct-002
  • vr.wm-xct-029
  • vr.wm-xct-001

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Action definition ID and version, immutable once published.
  • Request ID bound to a client intent digest and an idempotency key.
  • Server admission ID bound once at admission, kept outside the client digest.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: it has no physical body to measure.

Recognition optional Filled

  • An action request names an actor, a principal, a target resource revision, a purpose and an idempotency key.
  • It is confused with a task (a unit of work) and with an audit log entry (a record after the fact).

Capabilities and actions required Filled

  • Keep description separate from permission; do not invoke descriptive-only definitions. Requires the applicable host authority.
  • Keep optional crosswalk descriptive; never infer permission from a neighbor model. Requires the applicable host authority.
  • Add a new revision for changed meaning; never replace the same ID/version. Requires the applicable host authority.
  • Ask for missing actor, principal, resource revision, purpose or audience; do not fill them by guessing. Requires the applicable host authority.
  • Retry the same intent and key only after continuity is established. Requires the applicable host authority.
  • Keep server ID outside client intent digest; bind it once at admission. Requires the applicable host authority.
  • Require host verification; do not construct a second mandate master. Requires the applicable host authority.
  • Intersect both scopes within the same rule; do not combine partial grants. Requires the applicable host authority.
  • Check current inputs under the effect transaction. Requires the applicable host authority.
  • Return the uniform withheld response when read is denied. Requires the applicable host authority.
  • Require explicit submit permission; preserve proposal origin without executing it. Requires the applicable host authority.
  • Use only the bounded local adapter; external side effects need another contract. Requires the applicable host authority.
  • Return permitted retained evidence; never reapply an old effect. Requires the applicable host authority.
  • Expire only pending requests; preserve committed state. Requires the applicable host authority.
  • Cancel pending intent only; do not claim undo after commit. Requires the applicable host authority.
  • Create a new request and key; refuse stale or context-mismatched compensation. Requires the applicable host authority.
  • Record knowledge separately from authoritative effect state. Requires the applicable host authority.
  • Append a correction; never edit a receipt or erase the original. Requires the applicable host authority.
  • Keep export read-only with explicit capture time and sequence. Requires the applicable host authority.
  • Separate internal consistency from authenticated current admission. Requires the applicable host authority.
  • Resume identical bytes; a changed cut needs a new directory. Requires the applicable host authority.
  • Keep nonreuse evidence; this fixture has no erasure mechanism. Requires the applicable host authority.
  • Stop and reconcile before dispatch after uncertain restoration. Requires the applicable host authority.
  • Reject duplicates/floats/surrogates; never label this encoding JCS. Requires the applicable host authority.
  • Validate nested facets/history explicitly; outer envelopes alone are insufficient. Requires the applicable host authority.

Hazards and failure modes required Filled

  • Duplicate execution when a retry is not recognised as the same intent.
  • Privilege escalation when a description is read as a grant.
  • Stale execution when inputs changed between request and effect.

Standards and interfaces required Filled

  • Idempotency-key practice of HTTP APIs (IETF draft Idempotency-Key header).
  • W3C PROV for execution evidence.

Context of use required Filled

  • Used inside a Company Dimension where a host system authenticates actors and enforces permissions.

Sources Filled

  1. Research record EM-XCT-07: independent provider studies, audits and reconciled findings - Evidence behind the release; claims in the card trace to it.
  2. Enterprise Action Requests 0.1.0 specification - Normative release, digest sha256:3fc7364792c8f90cd4c1652448fb78bc84fb0e019df606593653f16d4afb300a

Open questions

  • Use the pinned companion schema/validator and trusted-host binding. Native outer validation alone does not enforce nested semantics. Consult the released adoption limits. Use descriptive ActionDefinitions without inferring permission. Execution is a finite synthetic local-label fixture. Read the publication addendum for host authority and admission duties, receipt disclosure, archive/recovery limits, missing edge tests and the nine-asset candidate installation boundary. Required reading: https://ver.cy/models/enterprise-action-requests/versions/0.1.0/publication-addendum.md

Machine files

Card as JSON Specification AGENTS.md Package Source Card backlog vercy.card/1

Provenance

enterprise research · reviewable-draft

Built from: models/enterprise-action-requests/versions/0.1.0/spec.json, models/enterprise-action-requests/catalogue-entry.json, ver-cy/world-models/card-supplements/enterprise-action-requests.json