R7-11 Release Owner’s Gate file

Supports slides 40 and 44.

The whole arc of the gate: my misjudgement, the method, a public post, adoption by the Secure Controls Framework (SCF), and use in our own stack.

Date	Event	Source
31 May to 1 Jun 2026	The [V]/[S]/[F] discipline and the Release Owner’s Gate. A named human signs before anything ships	Capstone Facts Reconciled
1 Jun 2026	I tell Michael I can’t tell how much of an AI-generated marketing plan is understood and how much is “a polished turd”	Slack DM to Michael
17 Jun 2026	I post the story on LinkedIn. 731 impressions by 26 Jun	LinkedIn post analytics
18 Jun 2026	SCF founder Tom Cornelius reacts, and the SCF page publicly proposes it as a new control in the AAT domain	LinkedIn comments
8 Jul 2026	SCF 2026.2 ships AAT-33, “Release Owner Gate (ROG) For AI-Augmented Content”, among 65 new controls. Three weeks after the post	github.com/securecontrolsframework/securecontrolsframework/releases/tag/2026.2 (verified 17 Oct 2026)
18 Aug 2026	The gate is a named stage in the OpenControls CKI glossary pipeline	MoxyWolf Vault, OpenControls Index
25 Sep 2026	Commits in the gstack plugins record test runs captured on “the Release Owner’s Mac”	moxywolf-plugins commits d82b60f, c1e8f75
29 Sep 2026	The pre-merge gate moves to GitHub: an approving review from code owners required; CODEOWNERS names me for every path	moxywolf-plugins commits b6fbf90, f07f22e

What I claim, and what I don’t

I claim the proposal and the trail. I don’t claim authorship of the AAT-33 control text; the SCF wrote it.

Not yet evidenced: a single commit dated 25 Sep that switches the gate on for every merge. The repo shows the Release Owner role in use on 25 Sep and the GitHub merge gate designed on 29 Sep.

Sources:

• Capstone Facts Reconciled (16 and 17 Oct 2026): Release Owner’s Gate
• SCF 2026.2 release notes on GitHub
• moxywolf-plugins git history
• MoxyWolf Vault, Projects/OpenControls/00-Hub/OpenControls Index.md