← Assurance

Objective

Where policy demanded a human decision, a human actually made it, in time, and in sufficient number.

Assurance

automated — ARC decides this from its own records

Frequency

continuous

Severity if it fails

critical

Enabled

Yes

Category

authorization

For every action in the window whose decision was REQUIRE_APPROVAL and which executed, assert that an approval request exists, that it reached approved status, that the distinct approving votes met the required minimum, that every vote was cast before execution began, and that separation of duties was honoured where the rule demanded it.

• Whether an approval can be attributed to a named individual depends on how that operator was authenticated, which varies by deployment and can vary between two approvals in the same window. Each assessment therefore states the attribution of the votes it actually examined, rather than this catalogue asserting one answer for every installation.

Status

Pass

Summary

All 1 approval-gated executions had a valid human approval recorded before they ran.

Evaluated

2026-10-26 09:18:30Z

Assessment

arc_asm_3801c1…

Covering 2026-09-26 09:18:30Z to 2026-10-26 09:18:30Z — 7 action(s) and 8 evidence record(s) fell in that window. Every status below describes that period and nothing outside it.