Public Release - 2026-07-09
Artifact: observation_action_split_v1. This note separates what an agent can observe, what it can recommend, and what it is authorized to execute when connected to APIs, payment flows, CRM systems, support desks, or other operational tools.
Artifact
When agents are connected to APIs, payments, CRM records, tickets, or backend tools, a common failure is to collapse observation, recommendation, and execution into one permission state. The review packet keeps those states separate.
Authority Route
The packet records the observed fact, the recommendation, the requested execution, and the authority source that permits or blocks the action. This prevents an automation workflow from using tool access as a substitute for decision authority.
Review
Payment flows, API writes, account changes, CRM updates, and customer-facing actions require a traceable split between recommendation and execution. If the risk state is unclear, the route should fall back to approval, dry run, downgrade, or abort.
The public claim under review.
The fact, event, metric, API response, ticket, payment state, or CRM record observed.
The proposed action, ranking, next step, or human-facing suggestion.
The concrete action the agent or automation is being asked to perform.
The user, role, policy, approval step, contract, or delegated authority.
The API, payment button, account, CRM object, support action, or backend permission boundary.
The operational risk state: low, elevated, blocked, unclear, stale, or conflicting.
The deterministic next step: ask, dry run, require approval, downgrade, log, or abort.
The trace preserving observation, recommendation, authority, and execution decision.
The recorded state: supported, narrowed, pending, or retired.