Support operations · governed actions
ResolveOps
A support-operations system that separates what should happen from how it should be explained, keeps business rules deterministic, requires approval when risk demands it, and treats external execution as a reconciled operational state rather than a chat side effect.
What governed business resolution should occur?Owns · Governed business-resolution workflows
Authority split
What should happen is separate from how it should be explained.
System model
Request to outcome without collapsing policy into chat.
External action truth
Timeout is not the same as failure.
UNKNOWN triggers reconciliation before retry; otherwise a payment/account action can be duplicated.
Cross-product boundary
High-impact execution can cross into AgentGuard.
Engineering decisions
Operational correctness lives in the failure states.
Separate resolution reasoning from policy
The model may reason about a case, but refund eligibility, ceilings, and irreversible actions remain deterministic business rules.
UNKNOWN is a first-class execution state
An external timeout may have succeeded remotely; blind retry can duplicate financial/account actions.
Approval is risk-based, not universal
Low-risk reversible work can remain efficient while high-impact actions retain human control.
Capability surface
Governed participation in support operations.
Benchmark surface
What the system is designed to measure.
The useful unit is a correctly governed resolution, not a fluent response.
Policy-labeled case fixtures, action proposal evaluation, approval/replay tests, external-failure simulation, and outcome replay.Evidence
Publicly defensible operational boundaries.
Explicit boundaries