Run · Governed execution
Agents and software can propose the same canonical consequence through different frameworks and protocols. Aarmos governs only when that consequence reaches a supported boundary on a path established as enforcing.
At that boundary, Run applies the applicable Decision and Authority before dispatch, records the Attempt, and reports Effect only up to what the boundary can actually observe.
Enforcement state is path-specific. An enforcing path does not establish that every route to the consequence is governed. The documented path set remains unknown for every boundary below.
One consequence model
Different frameworks and protocols can arrive at the same proposed consequence. The boundary normalizes that proposal into the same governance model; it does not make an unsupported path governed by association.
Framework, protocol, adapter, or direct caller
The canonical action and affected resource
The specific path where Aarmos can mediate
Allowed only under the applicable Decision and Authority
Documented boundary view
Each row translates the current capability manifest and public claims registry. It keeps consequence identity, path state, qualification, other known paths, completeness, and Effect ceiling separate.
Runtime and interface support inventories are not documented by the current connector self-descriptions. They are not inferred here.
Database mutation
database.mutation
Governed path
Database mutation connector
Current state
What Effect can establish
Transaction commit observed
Connector conformance only; no whole-database claim
unknown
Unenumerated routes are not assumed governed.
Structured tool invocation
tool.invocation
Governed path
Structured tool connector
Current state
What Effect can establish
Tool-boundary acknowledgement observed
Connector conformance; exact or coarse binding is invocation-specific
unknown
Unenumerated routes are not assumed governed.
Release to environment
deployment.release-to-environment
Governed path
Qualified deployment admission
Current state
What Effect can establish
Target-observed presence of the exact release across declared units
Qualified admission path only; each target still requires its own proof
unknown
Unenumerated routes are not assumed governed.
Local process execution
local.process-execution
Governed path
Supervised spawn broker
Current state
What Effect can establish
Operating-system creation of the authorized process image
Reference proof only; live-host enforcement is not established
unknown
Unenumerated routes are not assumed governed.
This boundary is not presented as enforcing.
Queue message publish
queue.message-publish
Governed path
Aarmos-controlled publish relay
Current state
What Effect can establish
Broker acceptance of the exact bound message
Enforcing in the controlled qualification environment; customer proof remains required
unknown
Unenumerated routes are not assumed governed.
Structured HTTP request
http.request
Governed path
Structured HTTP request relay
Current state
What Effect can establish
Target acceptance of the declared HTTP operation
Enforcing in the controlled qualification environment; customer proof remains required
unknown
Unenumerated routes are not assumed governed.
Generic HTTPS does not establish application semantics.
Network connection
network.connect
Governed path
Egress / CONNECT seam
Current state
What Effect can establish
Connection established to the resolved network endpoint
Destination-level qualification in the controlled environment; customer proof remains required
unknown
Unenumerated routes are not assumed governed.
No payload, HTTP-operation, or business meaning is inferred.
Email send
email.send
Governed path
Provider-backed qualified relay
Current state
What Effect can establish
Provider accepted the send request; delivery is not asserted
Qualified provider-backed relay; customer proof and credential custody remain required
unknown
Unenumerated routes are not assumed governed.
Semantic depth
The same traffic can cross boundaries with different semantic depth. A coarse boundary cannot inherit the meaning available at a structured one.
http.request
Can bind a declared operation and observe target acceptance under its declared contract on the qualified relay path.
network.connect
Can mediate connection to a resolved endpoint. HTTPS is not decrypted, and payload, HTTP operation, and business meaning are not established.
Canonical state vocabulary
Completeness answers a different question: whether every relevant path is known. A strong path state never upgrades unknown completeness.
Local and hosted boundaries
Policy evaluation, receipt signing, and key custody run on customer infrastructure. The website, account, entitlement, team membership, and optional evidence delivery are separate hosted services.
This does not make an unwired path governed. A customer or live environment is enforcing only after its own path-level conformance.
The handoff
Determines authorization under declared policy.
Enforces governed execution under the applicable Decision and Authority at supported consequence boundaries.
Preserves governance evidence that can be independently verified.
Technical references