Stack 3 · MC7–MC9 · Team
Synthesis: Orchestration, Governance, and Shared Value in Public Performance
How a value-generating ecosystem is designed to sustain itself — and how that design is defended before external scrutiny. Stack 3 synthesizes production (Stack 1) and diagnosis (Stack 2) into governance-capable orchestration. MC9 proves whether you can perform.
From Institutional Diagnosis to Systemic Orchestration
MC7 marks the transition from institutional diagnosis to systemic orchestration. Students formally design an AI-augmented branding and activation studio capable of coordinating cultural production, institutional resources, sponsor ecosystems, and public-facing value propositions simultaneously.
The studio is not hypothetical. It is constructed as the operational system that will generate the MC9 capstone: a fully designed and defended charity fundraiser activation concept of the team's own choosing.
Before designing their studios, students engage Ways of Seeing Episode 2 (BBC, 1973) — Berger's examination of the European nude tradition and the grammar of the male gaze. The episode's core question becomes the foundational design question of Stack 3:
In whatever ecosystem you are designing — who is the spectator-owner? Who is arranged for their gaze? And do you know you are making that choice?
Leni Riefenstahl deploys the surveyor/surveyed grammar from both sides simultaneously — as filmmaker arranging bodies for spectator-owners, and as subject who has so completely internalized the spectator that she cannot stop performing. Her Nuba photographs reproduce the same colonial gaze she claims was pure beauty. Eco's beautiful soul at its most consequential: the consciousness that refuses to see what its own grammar is producing.
John Parker's Dementia (1955) structurally refuses the nude grammar: the Gamin is the perceiving subject, not the displayed object. The studio's rerelease as Daughter of Horror (1957) adds Ed McMahon's voiceover only at the bookends — sufficient to install a spectator-owner frame that colonizes everything in between. The reframe is not everywhere. It only needs to be at the threshold.
Orchestration requires structured differentiation of responsibility. MC7 makes Division of Labour explicit through the Hipster / Hacker / Hustler triad, aligned with Wartofsky's three artifact levels and RPV:
In MC3 students built a standalone Claude Skill for a single practitioner task. MC7 escalates: teams build a three-skill architecture — one skill per studio role — that collectively operationalizes the studio's full production, process, and governance capacity.
| Role | Skill Category | Wartofsky Level | S/E/E/D Failure Mode |
|---|---|---|---|
| Hacker | Category 1 — Asset Creation | Primary / Resources | Visible and concrete — wrong format, wrong dimensions. Fix: revise style guide or template. |
| Hipster | Category 2 — Workflow Automation | Secondary / Processes | Process-level — wrong step sequence, skipped governance checkpoint. Fix: revise step sequencing or validation gates. |
| Hustler | Category 3 — MCP / Governance | Tertiary / Values | Governance-level, potentially invisible until pressure. Skill must be tested against adversarial cases — sponsor requests that push against the boundary — not just typical use. |
The three skills must work as a system: Hacker assets feed Hipster workflows; Hustler governance boundaries constrain what Hacker may produce and Hipster may schedule. When aligned — same production standards, workflow sequences, and governance boundaries — the architecture is autopoietic: it sustains and reproduces itself.
One structural constraint applies to all studio designs: the sponsor and partner ecosystem must comprise between five and nine entities. This is not an arbitrary commercial cap. It is Miller's Law applied as a perceptual architecture constraint: the cognitive sweet spot in which each sponsor registers as a distinct, meaningful presence that an audience can hold in working memory simultaneously.
Fewer than five reads as underfunded. More than nine and individual sponsors lose perceptual distinctiveness — visual noise exceeds the audience's chunking capacity, sponsor value diminishes through dilution, and the charity's centrality risks burial.
Scorsese's The Last Waltz (1978) is the framing case: extensive orchestral preparation met the improvisational chaos of a live performance. Equipment failed. Camera operators had to respond instinctively. The production team found the right mistake — and it worked. Not all deviations from plan are failures. Some become structurally necessary. A viable studio must be designed to know the difference.
Students must explicitly position their studio on the orchestra/jazz spectrum. The positioning is not aesthetic preference. It is a governance decision with consequences for how the system responds under pressure.
Permission as Orchestrated Constraint
MC8 formalizes the governance layer of orchestration. If MC7 required teams to design a studio capable of coordinating shared value, MC8 asks: who is authorized to act within that system — and under what conditions?
Licensing is reframed as calibrated constraint. Too little permission structure destabilizes trust. Too much suppresses emergence. The design challenge is sustainability without suffocation.
The certificate's foundational contribution: an extension of Benjamin's two-term exhibition/cult value dialectic into a three-term system. This is a structural isomorphism — three disciplinary frameworks describing the same underlying architecture at different analytic resolutions.
| Wartofsky | RPV | Economic Form | Benjamin | Functional Expression |
|---|---|---|---|---|
| Primary Artifact | Resources | Products | Exhibition Value | Tangible asset or tool; the technological layer. Ownership is possession-based. |
| Secondary Artifact | Processes | Services | Cult Value | Structured activity performed; the social/relational layer. The irreproducible encounter. |
| Tertiary Artifact | Values | Licences | Economic/Governance | Permission structure; the governance layer. Determines whose exhibition value circulates and in whose interest. |
Benjamin's original essay held exhibition and cult value in tension. It did not fully articulate the third term: the economic and governance layer that determines whose exhibition value gets distributed, whose cult value gets protected, and who controls the conditions under which the first two layers operate. That third term is the Licences layer. It is where the political stakes of the entire framework are decided.
The tertiary layer's most consequential operation is not preventing access — it is shaping the imaginative space within which access is sought. The thought police problem is not that someone stops you from thinking a forbidden thought. It is that the conditions under which that thought would have been thinkable are never established.
The filmmaker who couldn't clear the rights never makes the film. The studio that would have served the cause rather than aestheticized it is never conceived — because the permission architecture was set before the imagination entered the room. This is why Benjamin insisted his essay be fundamentally unusable for fascist purposes: he understood that the tertiary artifact either opens or forecloses imaginative space at the levels below it.
| Model | Control | Permission | AI Destabilization |
|---|---|---|---|
| Proprietary e.g. Strategyzer / BMC |
Centralized in originating institution | Explicit, negotiated, fee-based | AI reproduces methodology structure without license — output ownership unclear |
| Transactional e.g. cover song licensing |
Distributed by statutory mechanism | Automatic per reproduction event | AI-generated covers collapse trigger, attribution, and definition of "original" simultaneously |
| Graduated Open e.g. Creative Commons |
Distributed by design; creator signals intent | Built into the object; users self-govern | AI training on CC corpus — is the output a derivative? Does share-alike propagate? Legally contested. |
Does the permission architecture you design serve the people the activation is for — or does it serve the spectator-owners who fund it? That question cannot be answered in a contract. But it can be encoded into one.
Benjamin wrote his essay to be fundamentally unusable for fascist purposes. The permission architecture students design in MC8 is their own tertiary artifact. It encodes, at the governance layer, whose interests are served, whose voice is protected, and whose imagination is foreclosed.
The question is not whether the architecture encodes values — every architecture does. The question is whether the values it encodes are the ones the studio claims, and whether the people governed by it can see clearly enough to hold it to account.
Shared Values in Public Performance
MC9 is the culminating performance of the ARIES Certificate. Students publicly present and defend their AI-augmented design studio architecture (MC7) and licensing/transparency framework (MC8) through a shared-value boundary object: a fully designed charity fundraiser activation concept of the team's own choosing.
This is not simply a pitch. It is a live orchestration test — the moment where production (Stack 1), institutional diagnosis (Stack 2), and systemic orchestration (Stack 3) converge in a single public performance.
The capstone deliverable is an AI-augmented, sponsor-integrated, cause-aligned activation concept designed for real-world deployment. It is a boundary object because it operates at the intersection of multiple activity systems simultaneously — and its success depends on systemic coherence: every activity system it intersects must be able to find its own interests legibly represented within the same architecture.
Teams choose their own activation context, satisfying three conditions: a cause with genuine community embeddedness, a viable sponsor ecosystem within the Rule of Seven, and a real or plausibly real venue and event context.
The pitch backbone is a set of pro forma financial statements that make shared value visible, quantifiable, and defensible across all stakeholder positions. These are architectural rather than actuarial — the emphasis is on the logic of value flows, not the precision of figures. All assumptions must be explicitly labelled. Reviewers will probe the architecture, not audit the arithmetic.
| Statement | PSL Layer | Key Architectural Question |
|---|---|---|
| 1 — Event P&L | All three layers | Is the event surplus / breakeven / deficit a governance choice — or a miscalculation? |
| 2 — Donation Flow | Licences layer | Is the charity genuinely central — measurably, structurally — or aesthetically central and financially peripheral? The Berger question made numerical. |
| 3 — Sponsor Value (×7) | Licences + Services | Does each sponsor statement show genuine shared value — or value extraction with charitable alibi? |
| 4 — Charity Impact | Services + Licences | Economic, reputational, and community value generated. Does the sponsor ecosystem reinforce or complicate the cause's credibility? |
| 5 — Studio Sustainability | All three layers | Do resources regenerate? Do processes stabilize? Do stakeholders re-engage? Does trust compound? |
| 6 — Shared Value Reconciliation | Values layer | One statement all stakeholders can read from their own position and find their interests represented. The boundary object's financial expression. |
Do resources regenerate — can the studio fund its next activation from this one? Do processes stabilize — can the workflow be repeated without rebuilding from scratch? Do stakeholders re-engage — would sponsors, the cause, and the venue return? Does trust compound — does the activation leave all stakeholders more committed than before? Does legitimacy endure — would the public trust the studio to do it again?
If yes: orchestration succeeds. If not: it was a presentation, not a system. A system that can only defend itself when conditions are ideal is not autopoietic. It is fragile.
The reviewer dialogue is where the system is genuinely tested. External reviewers will probe the Permission Architecture Dossier directly, challenge the governance boundaries, question whose interests the architecture actually serves, and introduce conditions the team did not anticipate. A studio architecture that holds only in a presentation room was never a viable studio.
The Berger question — asked in MC7, deepened in MC8, and now reflected back at the team performing in MC9 — remains open: Do you know what you are making? And do you take responsibility for it? The certificate does not answer that question for you. It gives you the frameworks to answer it yourself.
MC4–MC6 taught you to diagnose institutional systems under intervention. Change Laboratory identified precisely what the system cannot accommodate. Stack 3 builds systems that can.
The full program architecture — theoretical spine, five original contributions, institutional pathway, and the complete PRV dialectic from thesis through antithesis to synthesis.
Completion of all nine microcredentials (MC1–MC9) across the Processes, Resources, and Values sub-certificates earns the integrated ARIES Certificate — the credential that certifies not just production, not just diagnosis, not just governance, but the coordinated capacity to sustain shared value across competing interests in real institutional, commercial, and community conditions.