INSTRUMENT 10 · QUALIFICATION FILE & RELEASE

What has to exist before this may support real work?

Complete the qualification index, then make an explicit release decision. A score never substitutes for the evidence record — like a pilot's pre-flight checklist: every item gets physically checked before takeoff, not estimated from experience.

Example: if "known limitations and controls" is left unchecked, it means no one has written down what the AI system is known to get wrong or where it shouldn't be relied on — the equivalent of putting a machine into service on the floor without a maintenance manual. Attach that evidence, or leave the box open so the release decision reflects the real gap.

Revalidation watches: material source change · model/configuration change · drift · incident · scope expansion.

RELEASE DECISION

Improve

0/6 sections complete. Incomplete evidence limits any release decision.

WHY THIS INSTRUMENT EXISTS

A release decision needs a place where the intended use, the evidence, the configuration, the golden-set results and the named approvals live together — otherwise a verbal "looks fine" stands in for a decision that should be traceable.

Restrict, pilot, release and stop are all legitimate outcomes of the same file. Making stop and restrict as easy to select as release is what keeps the record honest rather than a formality that always ends the same way.

§7.1 Write the one-page specification first§8.3 Coverage, missed findings and false findings§5.3 Approval evidence proportional to consequence§8.5 Reporting results honestly§12.2 Sixty to ninety days: from pilot to decision§4.5 Building support without overselling the technology