Week 7 Audit: The tier the pitch didn't touch
The first post-break audit --- checking a rollback plan's claim that the untouched tier is actually safe
19 April 2027
This week’s rollback plan makes a move worth naming: “the high-stakes tier still requires a human” sounds like safety, but the notice itself argues that tier depends on a practice pipeline the routine-tier automation is quietly cutting off. The audit skill is catching a rollback plan’s reassurance and checking it against the rest of the same document.
Before the session#
Bring the sentence in this week’s rollback plan that sounds most reassuring, and check it against the breaking-changes section directly.
In the session#
File Your Own Notice is due today. We spend the session in peer-audit pairs: trade notices, and apply this week’s “check the reassurance against the rest of the document” habit to each other’s work before submission.
Afterwards#
Keep your peer’s audit notes — the Sunset Review Board in week 12 revisits this kind of peer-checked claim.
The spec
What you bring to the session. Written so a reader can tell whether it has been met without asking you.
- you can state the practice-pipeline mechanism connecting the routine tier's automation to the high-stakes tier's future
- you have submitted File Your Own Notice, and can say which part of it you're least confident holds up under this kind of audit
Teaching team
- Marisol Quaye — convenor