System Archetype Template¶
Reference template — instantiates System Archetype Diagnosis
A reusable pattern card — typical symptoms, loop skeleton, and intervention hints for one named archetype — used as the reference a live map is matched against.
System Archetype Template is not a diagnosis of any live situation; it is the reference a diagnosis is made against. Each template is a reusable card for one named archetype, holding three things: the pattern's typical symptom signature, its canonical loop skeleton (the reinforcing and balancing loops, delays, and the shape of the connections), and its standard intervention hints. Its distinguishing idea is genericity — the template deliberately abstracts away from any particular case so it can serve as the "known archetype" side of a comparison. A named diagnosis then puts a live map next to the relevant template and asks whether the structures align. The template supplies the target of the match and the menu of intervention hints; it never asserts that a real situation is the pattern.
Example¶
A government policy unit keeps a slim deck of archetype template cards on the wall of its analysis room. A recurring frustration lands on the desk: a new regulation aimed at a target group keeps getting quietly neutralized — the group adapts, the intended effect erodes, and a tougher rule follows, which is adapted around in turn. An analyst reaches for the deck and pulls the "policy resistance" template card. It lays out the canonical skeleton — a rule that shifts an actor's behavior, an actor loop that pushes back toward its own goal, and the escalating-rule dynamic — alongside the symptom signature ("compliance decays after each tightening") and the intervention hints ("align the actors' goals rather than raising enforcement"). The card does not tell the analyst that this case is policy resistance; it gives them a precise structure to check the case against, and a starting menu of moves if the match holds. The judgment, and the evidence, come next and elsewhere.
How it works¶
- Store the canonical skeleton. Capture the archetype's loops, delays, and connective shape in a form abstract enough to match many cases.
- Store the symptom signature. Record the typical observable tells so a live symptom pattern can be compared against them.
- Store the intervention hints. Attach the response families that tend to work for this structure, as candidates rather than prescriptions.
- Present for comparison. Offer the card as the reference half of a match — the target a live map is laid against — without applying it.
Tuning parameters¶
- Abstraction level — how generic the template is. More abstract cards match more cases but discriminate less; more specific cards fit fewer situations more tightly.
- Library breadth — how many archetypes the deck holds. A wide library covers more, but a bloated one invites forcing a case into whatever card is nearest.
- Hint specificity — how concrete the intervention hints are. Concrete hints are actionable but tempt recipe-following; abstract hints resist misuse but need translation.
- Revision cadence — how often templates are refreshed against real cases. Stale cards ossify into slogans that no longer describe how the world behaves.
When it helps, and when it misleads¶
Its strength is leverage through reuse: a good template lets a team recognize a structure in minutes that would take days to derive from scratch, and it makes diagnoses comparable across cases and people. It is the artifact that turns hard-won structural insight into something transferable.[1]
Its failure mode is that a template is an attractor: having a card for "Escalation" makes every rivalry look like escalation. A stale library — cards never revised against how the system actually behaves now — quietly encodes yesterday's world. The classic misuse is treating the card's hints as a recipe to apply rather than candidates to test. The guarding discipline is to keep the template as a reference for comparison, never a verdict — the disciplined match and its falsification happen in other mechanisms — and to refresh the deck as real cases accumulate.
How it implements the components¶
archetype_library_reference— the template is an entry in the reusable library, the canonical stored form of one named pattern.archetype_match— it furnishes the reference structure and symptom signature a live map is compared against; it is the "known archetype" half of the match, not the applied judgment.intervention_playbook— it carries the generic response-family hints associated with the pattern, as a starting menu.
It holds no live-case content: the observed symptom_pattern, the drawn causal_loop_map, and the negotiated feedback_loop_boundary are produced by the named diagnoses and Pattern Diagnosis Workshop, and the evidence that a real case fits (pattern_fit_evidence, counterexample_check) is Archetype Fit Checklist's. The template is the generic card; a named diagnosis such as Shifting the Burden Diagnosis applies it to a specific situation.
Related¶
- Instantiates: System Archetype Diagnosis — supplies the reusable reference patterns the diagnostic mechanisms match against.
- Sibling mechanisms: Escalation Archetype Mapping · Fixes That Fail Diagnosis · Limits to Growth Diagnosis · Shifting the Burden Diagnosis · Tragedy of the Commons Diagnosis · Archetype Fit Checklist · Pattern Diagnosis Workshop · Leverage Point Matrix · Causal Loop Diagram
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: System Archetype Template is defined in the frozen evidence as: A reusable pattern card — typical symptoms, loop skeleton, and intervention hints for one named archetype — used as the reference a live map is matched against. Its operative deployed or enacted form is therefore Representation, Specification & Plan.
Nearest alternative: Interface, Display & Cue — Interface, Display & Cue can support this mechanism, but the evidence centers the concrete operation described above rather than the alternative family's defining operation.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Systems Thinking & Cybernetics
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: A reusable description of feedback structure, behavior, and intervention points is native to systems archetype practice.
Related originating lineages:
- Engineering & Design — Engineering design, reliability, and systems-safety practice supplies a parallel or contributing lineage for the mechanism's defining operation: a reusable pattern card — typical symptoms, loop skeleton, and intervention hints for one named archetype — used as the reference a live map is matched against.
- Organizational & Management Science — Organizational design, management, and operational governance supplies a parallel or contributing lineage for the mechanism's defining operation: a reusable pattern card — typical symptoms, loop skeleton, and intervention hints for one named archetype — used as the reference a live map is matched against.
Review resolution: The blind reviewers agree that systems_cybernetics is the primary origin and differ only on alternate origin disagreement, domain reach disagreement, encyclopedia synthesis disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain single_lineage because the combined evidence shows one traceable formative lineage. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
A template is a shared noun the other mechanisms point at: the named diagnoses match against it, the workshop uses its cards as prompts, and the fit checklist tests whether a live case truly earns it. That is why keeping the library small and current matters more than making it comprehensive — an unused or stale card does no harm sitting on the shelf, but a tempting, out-of-date one actively pulls diagnoses toward the wrong structure.
References¶
[1] The systems-archetype catalogue — Limits to Growth, Shifting the Burden, Fixes That Fail, Escalation, Tragedy of the Commons, and others — was popularized for management audiences in Peter Senge's The Fifth Discipline (1990), building on system dynamics work at MIT. Each archetype is precisely this kind of reusable template: a recurring loop structure with characteristic symptoms and intervention leverage. registry ↩