Week 9 Session: Week 9: Who Actually Decides

Decision rights and sign-off chains, and the difference between holding a veto and using one.

19 April 2027

Before the session#

Read the Alignment Lab page in full, including the worked example. This week’s session assigns roles and opens the pre-meeting contact window for the assessment.

In the session#

A veto that is never used leaves no trace in a normal record — which means a decision can look fully consensual on paper while one person’s unspoken capacity to block it shaped every option that was ever seriously put forward. This week’s short lecture segment separates “who signs the document” from “who could have stopped this and didn’t,” using the Engagement Signal Pilot’s own sign-off chain, traced below rather than only promised for later.

Reading down that chain, resist three shortcuts the raw documents invite but don’t support. First, step 1 is not a vote just because it decided something — the memo carries one named signature, not a ballot; calling it a “vote” the way step 2 genuinely is one would erase a real difference between a single signature and “several named people each had a recorded say.” Second, and separately, the memo’s single signature does not by itself let you infer the complete approval structure behind it: the document proves the figure and that Oyelaran signed it, dated and initialled — it does not prove she was the only participant in reaching that figure, that no other approval step happened elsewhere and simply went unrecorded here, or that a lone signature amounts to complete, validly delegated spending authority rather than one step in a chain the memo doesn’t show. None of this is a claim that a missing policy or delegation document exists somewhere to fill the gap — the honest position is that the memo alone cannot settle it either way, and treating “she signed alone with full authority” as documented fact would be exactly the kind of unsupported inference this course keeps asking you to label as one. Third, a calendar invite is a record that a meeting was scheduled and what its agenda said — it is not, by itself, a record of what authority the attendees held or exercised once they were in the room. Reading step 3 as having “authorised implementation” would be an inference the invite alone cannot carry; the honestly documented fact is narrower — the meeting happened, for the stated purpose, and nothing public records what was actually settled in it. Step 4 is where the sequence became official on paper, and Weeks 6 and 7 show a question on that same record going unanswered — but whether step 4 was a fresh decision or a ratification of something step 3 had already fixed is Week 4’s “stacking” inference, not a proven fact: a working group genuinely free to reconsider the sequence is an equally available reading of the same two documents. Naming which step in your own Alignment Lab decision record is a genuine approval, which is spending or implementation authority, and which is only an acknowledgement or a sign-off — and being explicit about which of your claims are documented fact versus your own reasonable inference versus still unknown — is exactly the distinction this week’s lecture segment asks you to carry into the role you’re about to be assigned.

The bulk of the session hands out the four Alignment Lab role cards and opens the strategy-memo and pre-meeting-contact stage of the assessment, using the templates and the contact rules described on the Lab page.

After the session#

Everything else happens this week, not next. Submit your strategy memo before making any contact. The pre-meeting contact window described on the Alignment Lab page runs 48–72 hours from today, subject to the contact limit described there, and your group arranges and holds its own decision meeting within that same window — it does not wait for the next scheduled class. Week 10’s session is the reveal, after your group’s decision record already exists.