Milestone 12: Your release and next cycle
This milestone chapter is part of a book in active development and has not yet been through the author’s review. Content may change as the review advances.
This chapter closes Studio 12: Special topic: agentic AI, release, and the next cycle. Its lessons each ended at It is your turn; what you wrote there arrives here as working material, and this is where the pieces become one artifact you can defend.
What this milestone produces. A review-management record for your directed AI team, a release audit recording release or withhold-pending-a-named-repair, your final dossier with a complete manifest, an explicit stopping rule, and your next-study agenda.
What you bring
You also carry forward the last milestone’s artifact: Milestone 11: Your reproducible package. This one builds on it, and the chain assumes it is versioned and filed.
Check you are carrying each of these before you start. If one is missing, go back and work that lesson’s It is your turn first; the practice below assumes it.
- Lesson 38 — Managing Multiple AI Agents: your closing-review team: the loops’ scoped jobs, the dependency wiring and turn counts, and the one node you kept human.
- Lesson 39 — Conflicting Agents and Human Escalation: your escalation rules, and one load-bearing pair of outputs (agreeing or not) diagnosed and settled by your own check, with any override on record.
- Lesson 40 — Final Research and AI-Management Portfolio: your finished research artifact with every claim bounded, your AI-management portfolio with the team record inside, and the rehearsed three-movement defense.
The practice
- Check that nothing moved since your Studio 11 cold run: any change to the package — a number, a claim, the data, the code, the environment record, or the instructions a stranger would follow — makes that run stale. Repeat it before you release.
- Run the closing review as a directed team: scoped loops (a writer, a skeptic, an auditor at minimum), wired so each role’s input exists before it starts, escalation rules written first, one node kept human. Declare who chooses each next step — you, a fixed script, or an agent that plans and calls tools — and never call a manually sequenced chat autonomous. A single well-run assistant playing the roles in turn is a legal team; record what you actually ran, never invented activity.
- Run the release audit and mark each item clear, pending, or blocking: permissions, participant promises, disclosure, package-matches-cold-run, reproducibility, claim boundaries, and uncertainty.
- Make the release decision. A blocking item means withhold pending the named repair, written as this version’s reason — not a euphemistic release.
- Assemble the dossier with a manifest: contract versions, evidence registry, permissions, measurement, your cycle log and claim-evidence table, AI ledger, artifacts, package, and revision history — each marked present, absent with reason, or not applicable.
- Write your stopping rule: why you are stopping here rather than running one more check, stated as a decision.
- Write the next-study agenda: tie the next question to an unresolved limitation, a warrant gap, or something this cycle’s evidence opened.
A version, not a pass
Your milestone artifact is a dated, numbered version with the reason for the version attached. When later evidence changes it, you write the next version rather than editing the last one, because the sequence of changes is itself part of your research record.
The four rails, here
Four concerns cross every studio in this book. At this milestone they take these specific forms.
- Ethics, permissions, and data exposure. Release is the last point at which a permission problem can still be prevented.
- Evidence, provenance, and reproducibility. The dossier is the evidence rail made assemblable.
- AI activity, verification, and human decisions. This studio is the ledger’s graduation — loop wiring, conflicts, overrides, and independence checks all land as rows before it closes; record the team you actually ran.
- Uncertainty, claim boundary, and revision history. State what you still do not know as clearly as what you found.
Where this milestone sits
You arrived carrying Milestone 11: Your reproducible package. This is where the chain closes, on a decision. If the audit clears, the artifact leaves your hands; if it does not, this version names the repair that still blocks release. Either way the next-study agenda opens the cycle that follows.
What sends you back
The next-study agenda is the revisit; a research cycle ends by declaring the next one.
How this milestone is assessed
Each row scores 0, 1, or 2. 10 points total.
| # | Criterion | 0 | 1 | 2 |
|---|---|---|---|---|
| 1 | The milestone artifact exists in full, specific to your own project | absent, or generic text that would fit any project | present but incomplete, or specific in some parts and generic in others | complete and unmistakably about your project |
| 2 | The milestone is written as a dated, numbered version with its reason | no version, or a version with no reason given | versioned, but the reason is decorative rather than an account of what changed | versioned with a reason a reader could use to reconstruct your thinking |
| 3 | Every judgment in the artifact is defended by you, not asserted by a tool | conclusions appear with no reasoning, or reproduce a tool’s wording | reasoning present but thin where the decision was hardest | each judgment carries a reason you could defend under questioning |
| 4 | The four rails are carried in the form this studio requires | one or more rails absent where this studio required them | all rails present but one is nominal | every rail addressed in the form this studio requires |
| 5 | The milestone’s own product is present and defensible: A review-management record for your directed AI team, a release audit recording release or withhold-pending-a-named-repair, your final dossier with a complete manifest, an explicit stopping rule, and your next-study agenda | release claimed despite a stale cold run or a blocking item, or the dossier manifest or next-study agenda is absent | components present, but one audit disposition is unsupported or the next study is generic | every disposition is traceable, blocking items are honored, the manifest is complete or explicitly accounts for absences, and the next study follows from a documented unresolved issue |
No work at or after Studio 4 proceeds past a not-authorized determination. This is not scored and cannot be averaged away.
Release requires the package to match its Studio 11 cold run; any change since that run means withhold pending a repeat. This is not scored and cannot be averaged away.
Your workbook
Open the workbook with the badge above. It walks these steps with a cell for each one, ends by writing your milestone version with its reason, and adds the rows this studio contributes to your AI Research Ledger and your Research Dossier.