Skip to main content

`POST /v1/internal/statements/regen`

POST 
/v1/internal/statements/regen

Authorization mirrors the platform's canonical Flow proxy-back gate (sys flow_delegate::execute_step): the caller must present an Auth-issued M2M bearer with sentin8:sys:steps:execute (Flow's sentin8-flow-sys client). Transport identity (PQ-TLS + platform CA) is machine identity, not service authorization; anonymous → 401, wrong scope → 403. The workflow's env is cross-checked against the bearer's env claim (a proxy-back can only act on an env its token can address; the platform plane bypasses via is_platform_admin).

Flow proxy-back for the statement-regen workflow (design §10).

Responses​

OK