EM-XCT-07 · Enterprise profiles · Published 0.1.0

Enterprise Action Requests

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

5 bundles · 10 layers · 26 findings · 52 questions

Required 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.

Publication addendum and exact limits

Use in a Company Dimension

Start with a descriptive ActionDefinition and steward. Executable use is limited to the synthetic adapter and requires explicit current host authority and disclosure.

Research assurance: reviewable-draft. This is a bounded original companion. Synthetic local reference with finite lifetime. Host authentication, standing verification, rate/admission limits, disclosure, archive isolation and continuity are external duties. No distributed effects, legal mandate verifier, delegation chains, production restoration or generic composer acceptance. Adoption limits.

Bundles → Layers → Findings → Questions

Collect the expected evidence for each question. Unknown context remains explicit. Listed actions confer no operational permission.

AR-B1Definition2 layers

Definition of company action requests.

AR-B1-L1Operation semantics2 findings

Questions and evidence for operation semantics.

AR-F01

Operation boundary

Exact immutable ActionDefinition and parameter contract

Questions
  1. AR-Q01 Which versioned operation is described?host-guidance
    Expected answer
    • ActionDefinition.definitionId, version and full-content sha256
    • Resolve the exact pin and describe name, targetType, precondition and effectBoundary.
  2. AR-Q02 Is it descriptive-only or executable in this binding?host-guidance
    Expected answer
    • ActionDefinition.mode, adapter and parameterContract
    • Return descriptive-only or synthetic-executable; descriptive-only has no invocation path.
Artifacts
  • Exact immutable ActionDefinition and parameter contractRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Keep description separate from permission; do not invoke descriptive-only definitions. Requires the applicable host authority.
AR-F03

Neighbor alignment

Pinned comparison and explicit relation

Questions
  1. AR-Q05 Does K2 actClass overlap this operation?host-guidance
    Expected answer
    • legacyCrosswalk Pin and verified K2 comparison
    • State overlap/narrower/broader/unverified; a name match is not exactMatch.
  2. AR-Q06 Does a capability or obligation authorize it?host-guidance
    Expected answer
    • Current complete host rule and conceptual capability/obligation references
    • Report that a capability or duty alone provides no execution permission.
Artifacts
  • Pinned comparison and explicit relationRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Keep optional crosswalk descriptive; never infer permission from a neighbor model. Requires the applicable host authority.
AR-B1-L2Definition governance1 findings

Questions and evidence for definition governance.

AR-F02

Revision and stewardship

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

Questions
  1. AR-Q03 Who governs this definition?host-guidance
    Expected answer
    • ActionDefinition.stewardId, masterId and host-verified governance evidence
    • Identify semantic steward and authoritative source; unknown standing stays unknown.
  2. AR-Q04 What changed across revisions or retirement?host-guidance
    Expected answer
    • Retained definition versions, recorded_at, control_sequence and retired_sequence
    • Compare exact version bytes and monotonic retirement; do not infer a revision from a renamed label.
Artifacts
  • Stable definition ID, revision chain, steward, master and validityRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Add a new revision for changed meaning; never replace the same ID/version. Requires the applicable host authority.
AR-B2Request1 layers

Request of company action requests.

AR-B2-L1Intent and identity3 findings

Questions and evidence for intent and identity.

AR-F04

Intent boundary

Closed immutable intent and exact definition pin

Questions
  1. AR-Q07 What exact effect is being requested?host-guidance
    Expected answer
    • Intent.definition, resourceId, expectedRevision and ordered parameters.labels
    • Describe exactly the requested replacement and any compensation reference.
  2. AR-Q08 What is the smallest valid request?host-guidance
    Expected answer
    • All required Intent fields in action.schema.json plus authenticated host actor
    • List missing required context; no defaults for principal, audience, revision or authority.
Artifacts
  • Closed immutable intent and exact definition pinRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Ask for missing actor, principal, resource revision, purpose or audience; do not fill them by guessing. Requires the applicable host authority.
AR-F05

Retry identity

Retained actor-scoped key hash and intent bytes

Questions
  1. AR-Q09 How can a caller recover a lost response?host-guidance
    Expected answer
    • Original exact intent, actor-scoped key, trusted continuity evidence and readable retained receipt
    • Use authorized lookup or identical retry; do not mint a replacement key on uncertainty.
  2. AR-Q10 Does a changed body reuse the old key?host-guidance
    Expected answer
    • Retained canonical intent bytes and new proposed canonical bytes in the same key slot
    • Equal bytes permit replay; changed bytes conflict, disclosed only with both read contexts.
Artifacts
  • Retained actor-scoped key hash and intent bytesRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Retry the same intent and key only after continuity is established. Requires the applicable host authority.
AR-F06

Host identity

Host-minted request ID and submission event

Questions
  1. AR-Q11 Which Dimension owns this request?host-guidance
    Expected answer
    • Intent.dimensionId and authoritative store meta.dimension
    • Require exact namespace equality; report the owning Dimension, not a request ID.
  2. AR-Q12 Who mints its ID?host-guidance
    Expected answer
    • ActionRequest.requestId and causal SubmissionEvent
    • Identify the fixture host as ID minter and show admission linkage; client intent excludes requestId.
Artifacts
  • Host-minted request ID and submission eventRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Keep server ID outside client intent digest; bind it once at admission. Requires the applicable host authority.
AR-B3Authority2 layers

Authority of company action requests.

AR-B3-L1Authority basis and scope2 findings

Questions and evidence for authority basis and scope.

AR-F07

External authority basis

Host rule, issuer-standing Pin and external basis Pin

Questions
  1. AR-Q13 Who can act for whom?host-guidance
    Expected answer
    • Rule.actorId, principalId, mode, basis and both exact scopes
    • Describe self or direct representation and the declared basis; no transitive delegation inference.
  2. AR-Q14 Who verified the issuer has standing?host-guidance
    Expected answer
    • Rule.issuerId, issuerStanding Pin and external host verification evidence
    • Name verifier/evidence if supplied; reference shape or hash alone cannot verify standing.
Artifacts
  • Host rule, issuer-standing Pin and external basis PinRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Require host verification; do not construct a second mandate master. Requires the applicable host authority.
AR-F08

Scope intersection

One complete matching pair of scopes

Questions
  1. AR-Q15 Are both principal and actor allowed?host-guidance
    Expected answer
    • One Rule with complete principalScope and delegateScope at host time
    • Evaluate both scope predicates in that same rule; never combine partial rules.
  2. AR-Q16 Are action, resource, purpose and audience exact?host-guidance
    Expected answer
    • Intent context and each scope dimensionId, full definition, resourceId, purpose, audience, actions and interval
    • Return exact matches/mismatches by axis; no wildcard or implicit audience.
Artifacts
  • One complete matching pair of scopesRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Intersect both scopes within the same rule; do not combine partial grants. Requires the applicable host authority.
AR-B3-L2Current decisions and disclosure2 findings

Questions and evidence for current decisions and disclosure.

AR-F09

Fresh decision

Policy revision, control sequence, decision and rule digests

Questions
  1. AR-Q17 Which policy applied at this try?host-guidance
    Expected answer
    • TryEvent.decision.policyRevision, matchedRuleDigests and controlSequence plus retained policies
    • Identify the latest policy at that sequence and recompute the match set.
  2. AR-Q18 Was the definition still available?host-guidance
    Expected answer
    • Definition validFrom/validUntil and retirement overlay at TryEvent controlSequence
    • Evaluate half-open time and retirement; native active state is not availability.
Artifacts
  • Policy revision, control sequence, decision and rule digestsRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Check current inputs under the effect transaction. Requires the applicable host authority.
AR-F10

Disclosure

Current read decision independent of execute

Questions
  1. AR-Q19 Can this caller see the outcome now?host-guidance
    Expected answer
    • Current authenticated actor, intent context and matching read scopes at now
    • Evaluate read independently of execute; old permission does not imply current disclosure.
  2. AR-Q20 Could an error reveal hidden existence?host-guidance
    Expected answer
    • Actual endpoint response and current read decision for any original/new conflict contexts
    • Without read return only withheld; do not infer hidden existence from that result.
Artifacts
  • Current read decision independent of executeRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Return the uniform withheld response when read is denied. Requires the applicable host authority.
AR-B4Execution2 layers

Execution of company action requests.

AR-B4-L1Admission and local effect3 findings

Questions and evidence for admission and local effect.

AR-F11

Submission versus proposal

Submission, delivery and try event identities

Questions
  1. AR-Q21 Has intent been admitted or merely proposed?host-guidance
    Expected answer
    • One SubmissionEvent, immutable request and admission policy
    • Distinguish host admission from a proposal in another domain; absence in an incomplete export is unknown.
  2. AR-Q22 Did a delivery actually lead to a try?host-guidance
    Expected answer
    • Complete operation group at a controlSequence with DeliveryEvent and execute TryEvent
    • Require delivery followed by its same-request try; a delivery alone is incomplete evidence.
Artifacts
  • Submission, delivery and try event identitiesRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Require explicit submit permission; preserve proposal origin without executing it. Requires the applicable host authority.
AR-F12

Atomic effect

Before/after revisions and one local transaction

Questions
  1. AR-Q23 What changed in the resource?host-guidance
    Expected answer
    • ReceiptEvent before/afterRevision and before/afterLabels with resource revision history
    • Report the precise local effect; order and duplicate labels are retained.
  2. AR-Q24 Are the key, effect and receipt committed together?host-guidance
    Expected answer
    • Request, key slot, effect revision and receipt within one committed SQLite transaction
    • Check atomic local history and rollback evidence; no inference about remote systems or power failure.
Artifacts
  • Before/after revisions and one local transactionRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Use only the bounded local adapter; external side effects need another contract. Requires the applicable host authority.
AR-F13

Replay

Retained receipt and immutable digest

Questions
  1. AR-Q25 Has this request already produced an effect?host-guidance
    Expected answer
    • Request terminal history and retained receiptId/ReceiptEvent
    • Return whether a local effect committed; caller observation is a separate claim.
  2. AR-Q26 Did the resource change in the meantime?host-guidance
    Expected answer
    • Current resource revision compared with original receipt.afterRevision
    • Report intervening work while preserving the old receipt; a replay never reapplies its effect.
Artifacts
  • Retained receipt and immutable digestRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Return permitted retained evidence; never reapply an old effect. Requires the applicable host authority.
AR-B4-L2Terminal and compensating operations3 findings

Questions and evidence for terminal and compensating operations.

AR-F14

Deadline

Half-open request deadline and terminal history

Questions
  1. AR-Q27 Can a first effect still occur?host-guidance
    Expected answer
    • Pending state, now, Intent.expiresAt, availability, scope and revision guard
    • A first effect requires now below deadline plus all other guards; deadline alone is not permission.
  2. AR-Q28 Is an old committed receipt being mistaken for expiry?host-guidance
    Expected answer
    • Replayed terminal state and original receipt occurrence
    • A committed request remains committed after the deadline; only pending can expire.
Artifacts
  • Half-open request deadline and terminal historyRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Expire only pending requests; preserve committed state. Requires the applicable host authority.
AR-F15

Cancellation

Current cancel decision and serialized disposition

Questions
  1. AR-Q29 Can a pending request be cancelled?host-guidance
    Expected answer
    • Current cancel scopes, retained-key status, pending state and request deadline
    • Explain whether authorized cancellation can transition pending; committed state cannot be undone.
  2. AR-Q30 Which terminal operation won the race?host-guidance
    Expected answer
    • Serialized TryEvent/DispositionEvent/ReceiptEvent control sequence
    • Identify the single terminal winner from complete history; timing guesses do not resolve a race.
Artifacts
  • Current cancel decision and serialized dispositionRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Cancel pending intent only; do not claim undo after commit. Requires the applicable host authority.
AR-F16

Compensation

Original receipt, exact old labels and current revision

Questions
  1. AR-Q31 Which effect is to be compensated?host-guidance
    Expected answer
    • New intent.compensatesReceiptId and retained original receipt with original request context
    • Require a new key/request and exact original before-labels plus the same narrow context.
  2. AR-Q32 Has intervening work changed its revision?host-guidance
    Expected answer
    • Current resource revision, original afterRevision and definition availability
    • Refuse stale revision or retired definition; matching current labels do not substitute for revision.
Artifacts
  • Original receipt, exact old labels and current revisionRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Create a new request and key; refuse stale or context-mismatched compensation. Requires the applicable host authority.
AR-B5Evidence3 layers

Evidence of company action requests.

AR-B5-L1Observer knowledge and correction2 findings

Questions and evidence for observer knowledge and correction.

AR-F17

Observer knowledge

Observation event and identified observer

Questions
  1. AR-Q33 What does the caller know about the result?host-guidance
    Expected answer
    • ObservationEvent observerId, claim, reason and time
    • Report caller knowledge as asserted, never as authoritative effect truth.
  2. AR-Q34 Is uncertainty local to the observer?host-guidance
    Expected answer
    • Observation claim alongside independent retained receipt history
    • Keep caller-unknown local to the observer; do not convert it into executor failure.
Artifacts
  • Observation event and identified observerRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Record knowledge separately from authoritative effect state. Requires the applicable host authority.
AR-F18

Correction

Linear correction edge and reason

Questions
  1. AR-Q35 Which observation is corrected?host-guidance
    Expected answer
    • ObservationEvent.correctsEventId, same request and observer
    • Resolve exactly one predecessor and identify the changed knowledge claim.
  2. AR-Q36 Does the predecessor still exist unchanged?host-guidance
    Expected answer
    • Retained predecessor bytes and correction edges
    • Verify predecessor is unchanged and has at most one immediate correction; do not erase it.
Artifacts
  • Linear correction edge and reasonRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Append a correction; never edit a receipt or erase the original. Requires the applicable host authority.
AR-B5-L2Master history and continuity5 findings

Questions and evidence for master history and continuity.

AR-F19

Mastership

One SQLite master and labeled native evidence

Questions
  1. AR-Q37 Which store is authoritative for execution?host-guidance
    Expected answer
    • Trusted host-selected executor store identity, epoch and continuity evidence
    • Identify one execution master; a matching epoch alone cannot prove the newest store.
  2. AR-Q38 Is a native export being treated as a second master?host-guidance
    Expected answer
    • Native binding declaration, snapshot cut and manifest assurance
    • Classify native export as evidence projection with no execution or overwrite authority.
Artifacts
  • One SQLite master and labeled native evidenceRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Keep export read-only with explicit capture time and sequence. Requires the applicable host authority.
AR-F20

History validation

Replay report and externally expected manifest root

Questions
  1. AR-Q39 Do the records form a coherent history?host-guidance
    Expected answer
    • Complete bounded snapshot and validate_snapshot report including operation completion
    • Assess internal consistency: current-at-sequence policies, lifecycle, effect, correction and resource history.
  2. AR-Q40 Does this prove authenticity or the latest cut?host-guidance
    Expected answer
    • Externally trusted source identity and expected latest-history anchor, if available
    • Internal validity does not prove authenticity or latest state; missing external anchor is insufficient context.
Artifacts
  • Replay report and externally expected manifest rootRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Separate internal consistency from authenticated current admission. Requires the applicable host authority.
AR-F21

Export recovery

Exact manifest, snapshot and deterministic native files

Questions
  1. AR-Q41 Was every file captured at one cut?host-guidance
    Expected answer
    • Manifest controlSequence/eventSequence/exportedAt, snapshot and exact projected files
    • Verify all retained files belong to the same cut; unexpected files or directories invalidate closure.
  2. AR-Q42 Can an interrupted export be resumed safely?host-guidance
    Expected answer
    • Original retained cut and current directory bytes plus interruption type
    • Resume only identical intact partial files; a torn file or changed cut requires a fresh directory.
Artifacts
  • Exact manifest, snapshot and deterministic native filesRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Resume identical bytes; a changed cut needs a new directory. Requires the applicable host authority.
AR-F22

Retention

Terminal-only key retirement event and retained key slot

Questions
  1. AR-Q43 Can this key be reused after retirement?host-guidance
    Expected answer
    • Terminal state, KeyRetirementEvent and retained actor/key slot
    • Retirement forbids reuse and emits no new effect; it is not deletion.
  2. AR-Q44 Which evidence is retained?host-guidance
    Expected answer
    • Retained immutable request, complete history, original receipt and policy snapshots
    • State full retention explicitly; legal erasure or minimization is outside this fixture.
Artifacts
  • Terminal-only key retirement event and retained key slotRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Keep nonreuse evidence; this fixture has no erasure mechanism. Requires the applicable host authority.
AR-F23

Restore continuity

Recovery decision and external continuity root

Questions
  1. AR-Q45 Could this be a coherent old database?host-guidance
    Expected answer
    • Recovery history and external continuity evidence, not merely epoch/hash equality
    • Recognize that a coherent older database can pass internal checks and replay.
  2. AR-Q46 What external anchor establishes the latest state?host-guidance
    Expected answer
    • Host-trusted external latest-history root and reconciliation decision
    • Name the actual root if supplied; otherwise halt dispatch after uncertain restore and request it.
Artifacts
  • Recovery decision and external continuity rootRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Stop and reconcile before dispatch after uncertain restoration. Requires the applicable host authority.
AR-B5-L3Representation and adoption3 findings

Questions and evidence for representation and adoption.

AR-F24

Byte identity

Explicit Python encoding and raw artifact SHA

Questions
  1. AR-Q47 Which canonical bytes define equality?host-guidance
    Expected answer
    • Exact encoded definition/intent/rule bytes and SHA-256 under documented Python rules
    • Separate semantic-content digest from raw-file hash; this contract is not RFC 8785 JCS.
  2. AR-Q48 Are ordering or Unicode silently normalized?host-guidance
    Expected answer
    • Original ordered arrays and Unicode code points compared with encoded output
    • Retain ordering, duplicates and distinct Unicode forms; reject floats, duplicate keys and surrogates.
Artifacts
  • Explicit Python encoding and raw artifact SHARequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Reject duplicates/floats/surrogates; never label this encoding JCS. Requires the applicable host authority.
AR-F25

Native binding

Three synthetic installation reports and exact file readback

Questions
  1. AR-Q49 Do stored native records match the semantic snapshot?host-guidance
    Expected answer
    • Stored companion snapshot/manifest inside Dimension and complete stored native record set
    • Reconstruct projections and compare every stored record with the cut; native state is not availability.
  2. AR-Q50 Did the companion validator run after outer checks?host-guidance
    Expected answer
    • Actual native outer report plus installed companion nested/readback report
    • Require both checks and their exact asset hashes; an outer pass cannot validate nested semantics.
Artifacts
  • Three synthetic installation reports and exact file readbackRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Validate nested facets/history explicitly; outer envelopes alone are insufficient. Requires the applicable host authority.
AR-F26

Adoption boundary

Descriptive minimum profile, synthetic execution profile and limits

Questions
  1. AR-Q51 Which use cases are useful today?host-guidance
    Expected answer
    • Selected descriptive or synthetic execution profile and required governance/evidence
    • Choose descriptive definition adoption or the bounded local reference; do not imply generic execution.
  2. AR-Q52 Which production responsibilities remain external?host-guidance
    Expected answer
    • Documented external duties: authentication, standing, disclosure, continuity, retention and scale
    • Identify which duties the adopting host implements and which remain unknown or deferred.
Artifacts
  • Descriptive minimum profile, synthetic execution profile and limitsRequired retained or host-supplied evidence; missing facts remain insufficient context.
Actions and unknown handling
  • Adopt the smallest useful profile; do not claim distributed execution readiness. Requires the applicable host authority.

Research and validation

Actual independent Claude and Grok studies and three implementation audit rounds are preserved. Both final R3 complete-source static audits accept with explicit limits, followed by complete adoption-document review and exact addendum wording review. Grok first reported omitted bundle input; all nine source fragments were recovered inline before its final verdict. Earlier disagreement is retained. Executed tests and native checks are separate Codex evidence. Executed tests and native checks are recorded separately. Research dossier · Review and limits · Tests · Native acceptance · Checksums.

Catalogue identity: vr.profile.enterprise-action-requests. EM-XCT-07 remains a broader, partially covered research contour. Parent models are semantic references; no subtype or whole-parent conformance is asserted.