The Release Decision
Updated
AdvancedWhat you'll learn
~18 min- State the release-decision thesis and its six corollaries in your own words
- Assign the risk acceptor, the independent reviewer, and the release owner before any test runs
- Place the record where a security officer can use it and state what it does not claim
What it is: the definition this training builds toward — a release decision as a bounded, signed, time-limited claim about one named use case and one deployable configuration — and the three roles assigned before any test runs.
What it buys: a signature that means something specific: who accepted what residual risk, on what dated evidence, until when. Without it, “approved” is a meeting minute, and the first question after an incident has no answer.
What to fund: the independent reviewer’s hours — someone who neither built nor bought the system, a house bar one notch stricter than the federal one — and the risk acceptor’s time to read the record rather than its summary.
Before the detail — Artifact: the record header with roles named. Status of what follows: binding where M-25-21 applies; reusable guidance elsewhere.
Prompt first: draft the header for MU-AI-004
Open your workspace agent on scripts/t7-substrate/data/release-decision-record.template.md and the register entry for MU-AI-004, switch into plan mode, and start with (if you do not have live exports or files handy, ask it to generate a small Meridian practice sample from the lesson’s scenario first):
Draft only the header table of the release-decision record for MU-AI-004 from its register entry and tier record. Leave roles, dates, and unpinned versions marked NEEDS-OWNER, and note who is disqualified as reviewer.Check that the plan or draft covers:
- Use case, system ID/name, deployment, tier, and gate path populated from the register and tagged
SOURCE: register - Version boundary recorded honestly (
alias, not pinnedandNEEDS-OWNERwherever an immutable digest is absent) - Lifecycle state set to
draft, with decision, decision date, and valid-through date markedNEEDS-OWNER - Risk acceptor, independent reviewer, and release owner marked
NEEDS-OWNER, explicitly disqualifying anyone who built or bought the system from the independent reviewer seat
If the agent invents names for the roles or fills in a decision date, reply: "Leave every role name, date, and decision value marked NEEDS-OWNER and list only the reviewer disqualifications."
The header is the part of the record that can be written on day one, and the reason to write it on day one is the roles. An agent asked to fill in a reviewer will pick a plausible senior name; the register says who is disqualified, and that is the only thing it is allowed to say. Everything else — the version, the date, the decision — is a fact somebody will earn later.
The bridge: you already sign expiring authorizations
If you work in a federal environment you have signed, or watched someone sign, an ATO (the formal authorization for a system to operate), and the rule from Federal Delivery 1.1 (a separate training in this series) is already yours: authorization is a signed, expiring decision. If you work commercially, a change-approval record with an approver and a review date is the same shape. Neither is new.
What is new is that behavior moves without a code change. A provider moves the alias your deployment points at; a suite feature updates on the vendor’s schedule; a classifier is retrained on a quarter’s data. Your authorization described a system whose behavior is now different, and nothing in the change pipeline fired, because nothing in your repository changed. So the decision must name the version boundary it was made against and expire on its own, without waiting for a change request that will never come.
The thesis
An AI release decision is a bounded, signed, time-limited authorization claim about a named use case and deployable system configuration — including the model or service version boundary — supported by dated evidence, independent review, declared conditions, and a named risk acceptor. It is not, by itself, a certification or an ATO.
Each word does work. Bounded: one use case, one configuration, the version boundary included — not “the chatbot.” Signed: a named person who accepts the residual risk, not a committee. Time-limited: a valid-through date that holds regardless of whether any trigger fires. Dated evidence: runs that can be reopened. Independent review: findings recorded by someone who did not build or buy it. Declared conditions: what must remain true. And the negative is the most important clause: the record supports evidence for an authorization and for existing controls; it does not replace either. This is assurance (the evidence-backed decision that a system may run), stated so it can be checked.
Six corollaries follow, and each names a place where a claim quietly overreaches. That structure looks like:
SIX COROLLARIES where a release claim quietly overreaches1 you cannot assure what you cannot list2 consequence and reversibility decide the gates, not the vendor's confidence3 the customer controls the test design and the sealed data; vendor-run results are declared as such and reproducible where practicable4 a single-attempt attack number is insufficient when retries are plausible - report by attempt budget5 a name alone does not prove an immutable version6 a fired trigger starts a clock, and an unanswered clock expires the decisionThe only honest pass statement is: “passed the named gates on the named set; no claim beyond it.” Each corollary is the exact sentence an assessor writes when the claim exceeded the evidence.
Roles assigned before testing
Three roles, assigned before any test runs. The risk acceptor signs — the person whose function absorbs the loss if the system is wrong, senior enough that the signature is theirs to give. The independent reviewer records findings and was not involved in building the system — M-25-21’s bar is “an independent reviewer within the agency who has not been involved in the development”; this training adds “or buying it,” a stricter house rule, because the person who chose the vendor has a stake in the verdict. The release owner runs the gates and assembles the record. For MU-AI-004, P. Delgado built it, so he can be the release owner and cannot be the reviewer; the risk acceptor sits above Asset Management.
Before testing, because a reviewer chosen after the results is chosen for the results. The sponsor who picks the reviewer once the evaluation looks good has already decided, and the record will read as if the decision were reviewed.
Naming the roles first costs a single agenda item; naming them after costs the credibility of every signature that follows.
The seam: where the record lands
Declare the frame first. Meridian operates one specified AI use case on behalf of a covered agency, and the contract expressly incorporates the applicable federal requirements — the contracting officer wrote M-25-22’s terms (OMB’s April 2025 memo on buying AI; OMB being the White House budget office that binds agencies) into the task order. The agency determines applicability, and AI risk acceptance is separate from an ATO. The European Union’s AI law does not reach a US utility serving US customers, and this training does not teach it.
The commercial starting practice is an approval record in a governance platform or an internal register — a signer, an approval date, a review-due date. The federal delta is that M-25-21 (OMB’s April 2025 memo on agency AI use) names the practices the record must evidence for high-impact use — an impact assessment, an independent reviewer, a signed risk acceptance — with a documented-by date that has passed.
The ISSO (the system’s security officer) needs the record where an assessor reads, not in a separate tool. The handoff artifact is the record itself, filed as an appendix to the system’s SSP (the system security plan — the package an assessor reads).
Where a condition is still open and it amounts to a control deficiency, a linked POA&M item (the tracked list of open weaknesses with dates) points at the record; the record itself is evidence, not a weakness.
What is not equivalent is the honest negative. No NIST AI control overlay is published: COSIS (Control Overlays for Super Intelligence Systems, NIST’s planned AI overlays for its security-control catalog, renamed from COSAiS on October 20, 2026) is still a concept paper and an outline as of 2026-11-07, so the record supports evidence for existing controls rather than mapping to AI-specific ones. And the record is not an ATO, and an ATO is not an AI risk acceptance; a system can hold one and lack the other.
The record, by its sections
The template at scripts/t7-substrate/data/release-decision-record.template.md opens with the header table you drafted above, then runs: impact, baseline, and benefit; evidence reviewed, every link resolving to a logged run; gate results as separate gates, never a blended score; conditions of release, each verifiable, including a halt procedure with a tested date; determinations, exceptions, and waivers; the triggers that suspend or expire the decision; and two signatures that mean different things — artifact integrity says these are the bytes reviewed, risk acceptance says the residual risk is accepted. Every field stays; “n/a - reason” replaces deletion.
Stop and escalate when the proposed independent reviewer built or bought the system, or when nobody with the authority to accept residual risk will sign — the acceptor’s test is authority, the reviewer’s is independence. A system with no signer gets no record and does not ship, and finding a signer is a decision for the governance board, not for the release owner.
Which of these is a release decision?
Practice status — among organizations that put AI systems into production under a named approver, commercial and federal
| Practice | Status | Also called |
|---|---|---|
| signed risk acceptance by a named acceptor | required where M-25-21 applies; common baseline elsewhere | approval sign-off |
| independent reviewer not involved in development | required where M-25-21 applies; strong optional elsewhere | second-line review |
| reviewer also not involved in buying the system | house rule (this training); strong optional elsewhere | acquisition-independent review synonym: sufficient independence / second-line review |
| fixed valid-through date independent of triggers | strong optional | review-due date |
| release decision record with resolvable evidence links | common baseline | model approval record |
| AI risk acceptance kept separate from the ATO | required where M-25-21 applies | none - do not conflate the two |
| mapping to an AI-specific control overlay | emerging - none published | none; supports evidence for existing controls |
| artifact-integrity signature distinct from risk acceptance | reference-shop | signed attestation |
Scale: required | common baseline | strong optional | reference-shop (seen only at organizations that publish their own practice) | emerging
Key takeaway
A release decision is a bounded, signed, time-limited claim about one named use case and one deployable configuration, version boundary included, supported by dated evidence, independent review, and declared conditions, with a named risk acceptor — and not, by itself, a certification or an ATO. Six corollaries mark where claims overreach, and the only honest pass statement is “passed the named gates on the named set.” The three roles are assigned before testing so the reviewer is not chosen for the results, and the record lands where the assessor already reads, supporting evidence for existing controls because no AI overlay yet exists. Module 2 turns to the evidence packet: what the model and its provider say about themselves, read from the risk acceptor’s seat.
- LEADERSHIP DECISION
- name the risk acceptor and the independent reviewer for every high-impact system before its first test - and accept that a system with no signer does not ship
- PRACTITIONER ACTION
- draft the record header from the register with the agent; leave the version, date, decision, and names NEEDS-OWNER; file the record where the assessor already reads
- SUCCESS MEASURE
- zero approved AI systems whose record lacks a named acceptor, a version boundary, and a valid-through date - the finding avoided at the first assessment