Status: Established Created: December 27, 2025 (Pattern Sweep 2.0) Ratified: December 27, 2025 (Chief Architect)
Meta-patterns are patterns about patterns - higher-order observations about how patterns emerge, evolve, and interact within the Piper Morgan project. They serve as diagnostic and predictive tools for understanding pattern dynamics.
This document consolidates the 5 meta-patterns identified through Pattern Sweep 2.0’s retrospective analysis of 7 months of project history.
Every significant crisis becomes a documented pattern, typically within 2-4 weeks of the crisis event.
| Crisis | Date | Pattern Response | Time to Pattern | |——–|——|——————|—————–| | Runaway Copilot | June 17 | “Complexity requires MORE discipline” | ~2 weeks | | Cascade Failure | June 22 | Swiss Cheese Model recognition | ~2 weeks | | Evidence Crisis | Sept 23 | Triple-enforcement philosophy | ~3 weeks | | Methodology Amnesia | July 25-26 | Excellence Flywheel crystallization | 1 day |
After any major incident, proactively schedule pattern documentation rather than waiting for organic emergence.
Patterns emerge in stages: informal practice → naming → documentation → formalization. The lag between practice emergence and formal documentation is typically 2-5 months.
Stage 1: INFORMAL PRACTICE (6-7 weeks)
↓ Ad-hoc application, not yet named
Stage 2: CRYSTALLIZATION (1-2 days, often crisis-triggered)
↓ Practice gets named, documented urgently
Stage 3: REFINEMENT (6-8 weeks)
↓ Continued practice, pattern recognition
Stage 4: FORMALIZATION (2-3 months)
↓ Pattern file created with formal structure
The current pattern library represents what we knew 2-5 months ago, not what we practice today. Proto-pattern tracking should be explicit.
Mature patterns stop being discussed because they work so well they become invisible. Silence about a pattern can indicate either:
Scan recent logs for pattern mentions. Missing patterns are either successes or problems - worth investigating which.
Pattern usage analysis should distinguish between “not mentioned because working” vs. “not mentioned because abandoned.”
Also known as: Completion Discipline Reinforcement Loop
Patterns 045, 046, and 047 document different manifestations of the same underlying failure: Completion Theater - declaring work “done” before achieving actual user value.
| Pattern | Failure Mode | Signal |
|---|---|---|
| 045: Green Tests, Red User | Tests pass but feature doesn’t work for users | QA pass + user complaints |
| 046: Beads Completion Discipline | Multiple items at 80% instead of one at 100% | Scattered partial progress |
| 047: Time Lord Alert | Time pressure causes verification shortcuts | Deadline proximity + skipped steps |
Root cause: Completion bias - the human (and LLM) tendency to seek closure prematurely.
These patterns form a reinforcing system that prevents premature closure:
Pattern-045: Green Tests, Red User
↓ Reveals the gap (tests pass, users fail)
Pattern-046: Beads Completion Discipline
↓ Prevents premature closure (enforces 100% criteria)
Pattern-047: Time Lord Alert
↓ Enables pause when uncertain
→ Completion without cutting corners
Pattern-049 (Audit Cascade) addresses Completion Theater systematically: mandatory audit gates between every phase catch drift before it compounds. LLMs struggle to follow templates during creation but excel at auditing against templates afterward.
These three patterns emerged within 6 weeks of each other (November-December 2025) because they solve connected problems. Pattern-049 (Audit Cascade) emerged January 2026 as the methodology response.
These patterns should be understood and taught as a system, not isolated practices. When Completion Theater is suspected, apply the Audit Cascade.
Three independent verification tools reinforce each other to create objective completion verification:
Serena MCP (Code Truth)
+ Beads CLI (Issue Truth)
+ STOP Conditions (Process Truth)
= Objective Verification
Verification should be multi-source. Single-source verification (e.g., “tests pass”) is insufficient.
Created through Pattern Sweep 2.0 (#524) Ratified by Chief Architect: December 27, 2025 Updated: January 16, 2026 (Completion Theater framing, Pattern-049 connection)