PUT takes effect immediately
(the resolver cache is invalidated on write). The CLI counterpart is
crewship policy get/list/set.
All endpoints require authentication and workspace context.
Validation rules:
full+blockis forbidden.reasonis required when settingautonomy_level=full.
List Policies
crewship policy list to render the overview table.
Response: 200 OK
Response Fields
Get Crew Policy
guided / warn) are
baked into the database, so this is always a single read.
Response:
200 OK
set_by_user_id / set_at / reason are omitted on crews whose policy still
matches the seed defaults (no operator has ever flipped it).
Set Crew Policy
set_by_user_id, set_at,
reason) atomically with the value change and invalidates the resolver cache
so the next decision sees the new state.
Request Body:
200 OK — the same shape as GET, reflecting the new state and the freshly-recorded audit triple.
Journal event:
policy.changed (workspace audit feed)