Assessment1 min readOutline
SAI-280 knowledge check
Verify tool, identity, permission, approval, confinement, memory, receipt, evaluation, and incident controls.
Last content review 2026-08-03Included in SAI-280
Scenario questions
- Why is model output a proposal rather than authorization?
- What belongs in a governed tool registry?
- Which identities must remain distinguishable during a run?
- When must action authorization be rechecked?
- What makes human approval sufficiently specific?
- Which boundaries apply to durable agent memory?
- How should a run receipt represent partial success?
- What should happen when policy or evidence services fail?
Completion criteria
The design passes when purpose, authority, identities, tools, typed inputs, permissions, approvals, confinement, memory, budgets, stop conditions, receipts, evaluation, failure, compensation, and incidents are explicit and enforced outside model instructions.
Completion confirms conceptual readiness only. Practical assessment remains unavailable while SAI-280 is in roadmap status.