Skip to main content
POST
Resolve a concern or violation
Authorization is org-scoped. A resolution mutates the agent’s governance state (it can amend the agent’s alignment card) and is recorded as correction-history, so the caller must be a member of the organization that governs {agent_id}. A caller authenticated against a different org receives 403 Forbidden; an unknown agent id receives 404 Not Found. The target_id must reference an existing checkpoint or trace belonging to the agent — a target_id that does not exist for the agent is rejected with 404 Not Found rather than persisting a dangling resolution.

Authorizations

Authorization
string
header
required

Supabase JWT token in Authorization: Bearer header

Path Parameters

agent_id
string
required

Agent identifier (e.g. smolt-abc123)

Body

application/json
target_type
enum<string>
required
Available options:
checkpoint,
trace
target_id
string
required
resolution_type
enum<string>
required
Available options:
acknowledged,
allow_action,
add_value
action_name
string

Required when resolution_type is allow_action

value_name
string

Required when resolution_type is add_value

Response

Resolution created

resolution_id
string
resolution_type
string
resolved_by
string
card_modified
boolean