Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:15:20 UTC

A.10:4.5 - Classify bounded reliance

The canonical local RelianceDisposition member set is exactly: pass, degrade, abstain, reopen, evidence-needed, assurance-needed, and blocked-current-use. pass supports only the bounded use; degrade supports only the named narrower or reversible use.

assurance-needed says that A.10 alone cannot support the attempted use because a direct domain rule or receiving decision requires a separately stated assurance claim. It creates no assurance claim and does not open B.3 until that claim is current. No disposition is claim truth, CV.Status, gate decision, selector outcome, approval, permission, release, assurance, or Work authorization.

When a named assurance claim is current, use B.3 for that assurance question. A.10 continues to supply the source and provenance paths but does not issue the assurance result. Consequential evidence use without such a claim stays with the direct safety, access, status, gate, permission, release, responsibility, or controlled-action pattern.

A reliance limitation qualifies the attempted use. When advice must also say what to do next, use C.11.DUA to compose a feasible continuation from that limitation. Further inquiry is one possible continuation. Retain the unsupported claim boundary when choosing a narrower use, another action or a stop. Use an already adequate C.11 choice directly.