Week 12 — The System You Are Willing to Defend

Studio critique of the systems you have built, and the failure boundaries you declare for them.

Week 12 · declared-boundary · 12 October 2026

A defensible design names the event it survives and the event that beats it.

Property

declared-boundary

Stance

Advances the claim

How

The configuration you nominated in week 1, brought back for critique.

Studio activity

Studio critique. There is deliberately no correct system.

The semester closes where it began, with the configuration you nominated in week 1 — now with eleven weeks of reasons to change it, and an obligation to say what it still cannot survive.

How this advances the thesis#

This is the thesis, stated as a deliverable. A design that names only what it survives has answered half the question, and the half it skipped is the half that tells a reader whether to trust the first. Week 12 treats the declared failure boundary as the primary engineering output rather than a caveat attached to one.

In the session#

Studio critique. You present a system, the event it survives, and the event that beats it. The room’s job is to test whether those three statements are consistent with each other and precise enough to be checked.

There is deliberately no correct system. There are systems whose limits are stated, and systems whose limits will be discovered by someone else later.

Its relationship to the canonical event#

The event gave the cohort a shared starting definition so that twelve weeks of argument could be about systems rather than vocabulary. By now you should be able to say precisely how your own definition differs from it, and why.