Arc 3 Study Guide 2.3.0-1

Design-Pattern-to-Level Map

The table below shows which RO design patterns carry primary structural load at each application level. A design pattern appears at the level where it does its most concentrated work. Some design patterns appear at multiple levels because their structural function shifts as the context scales.

Table 2.3.0-1 — Design Pattern Clustering by Application Level

Each design pattern is listed at the level(s) where it carries primary load. Unit references link the Phase I construction unit to the Phase II application unit.

Resilience is not a standalone pattern — its correction-channel content is carried by epistemic integrity (row above). It surfaces as a downstream application in (2.3A.3), (2.3C.4), and (2.3D.3), each of which is tracked under its own primary pattern in this table.

Reading by Level

A reader who needs to work at a specific application level can focus on the corresponding sub-arc while drawing on earlier levels as prerequisites.

Individual (Sub-Arc 3A) builds the personal structural disciplines: verifying claims and managing keys (2.3A.1), defending data sovereignty (2.3A.2), limiting commitments and absorbing disruption (2.3A.3), and reading aesthetic response as structural diagnostic (2.3A.4). Prerequisites: Arc 1 individual TO practice and Arc 2 individual OO method.

Team (Sub-Arc 3B) builds the cooperation architecture: designing interdependence with clean entry, exit, and restraint as cooperation boundary (2.3B.1), encoding enforcement and selective transparency with dispute resolution (2.3B.2), and detecting perverse incentives through hazard scanning and cultural signal auditing (2.3B.3). Prerequisites: Individual disciplines plus Arc 1 team TO practice and Arc 2 team OO method.

Organization (Sub-Arc 3C) builds the institutional architecture: treating answerability as a moral act (2.3C.1), applying restraint to prevent mandate and policy accumulation (2.3C.2), deciding what to hard-encode versus leave to judgment (2.3C.3), and maintaining hazard detection and crisis recovery capacity (2.3C.4). Prerequisites: Team disciplines plus Arc 1 organizational TO practice and Arc 2 organizational OO method.

Enterprise (Sub-Arc 3D) builds the civic-scale architecture: polycentric governance with real exit rights (2.3D.1), encoded objective law embedded in infrastructure (2.3D.2), crisis governance under adversarial conditions (2.3D.3), and the evidence-pack synthesis proving practice across all levels (2.3D.4). Prerequisites: Organizational disciplines plus Arc 1 enterprise TO practice and Arc 2 enterprise OO method.

Cross-Cutting Threads

Two threads run across all four levels:

Toolkits. Every unit ships a concrete, auditable deliverable. The toolkit is not a supplement — it is the point. A principle that remains in argument has not entered the world it claims to govern.

Evidence packs. Each level's final unit addresses how to prove practice without performative exposure. The evidence pack assembles private artifacts (logs, ledgers, self-assessments) and public attestations (signed commitments, audit results) into a minimal packet. The closing synthesis (2.3D.4) pulls the concept together across all four levels.