Proto Patterns capture real, recurring institutional needs but do not yet meet First Foundation’s standards for deployability.
They may be:
- incomplete in enforcement
- dependent on other patterns
- sensitive to leadership judgment or culture
- insufficiently validated under failure conditions
Mandatory Reading Rule
All Proto Patterns must begin with the following warning block, placed before any descriptive content:
Proto Status — Read First
Followed immediately by:
Why This Is a Proto Pattern
This warning functions as a safety label, ensuring Proto Patterns are not misread as deployable solutions.
The Read First section is static text and always contains the following:
This pattern is classified as Proto because it identifies a recurring institutional need but does not yet meet First Foundation’s requirements for enforceability, failure containment, or independent validation.
It should be treated as a design direction, not a deployable prescription. Applying it without supporting patterns or institutional safeguards may produce instability or false confidence.
This text is intentionally identical across all Proto Patterns and is not customized per entry.
Proto Patterns should be treated as design directions, not prescriptions. Applying them without supporting structures may create false confidence or institutional instability.
Proto-Pattern Tracking Rule
Proto-Patterns are not static placeholders. They are tracked as provisional structural concepts under active observation.
Whenever a Proto-Pattern is used in analysis, note:
- where it appeared
- what domain or context it appeared in
- whether its mechanism was clear
- whether it appeared alone or as part of a Pattern Sequence
- whether the instance strengthens the case for promotion to Full Pattern status
A Proto-Pattern should be reconsidered for promotion when it has:
- appeared in multiple analyses
- shown cross-domain or cross-context recurrence
- demonstrated a stable and distinct mechanism
- improved diagnosis, forensics, or structural interpretation
- remained meaningfully separate from existing Patterns or Anti-Patterns
Proto-Patterns that do not accumulate supporting use over time should remain provisional, be revised, or be retired.
The purpose of Proto-Pattern tracking is to ensure that the library evolves through observed structural recurrence rather than intuition, novelty, or preference.
- After the Gates Open Proto-Pattern
- Authority Substitution Cascade Proto-Pattern
- Chokepoint Dependency Proto-Pattern
- Civic Rites of Mischief Proto-Pattern
- Comparative Baseline Protection Proto-Pattern
- Emergency Delay Protocols Proto Pattern
- Intergenerational Feedback Loops Proto Pattern
- Labor Bottleneck Erosion Proto-Pattern
- Moral Compass Reinstatement Proto-Pattern
- Protective Decision Friction Proto-Pattern
- Representation Without Remedy
- Safe Containers for Belonging and Dissent Proto Pattern
- Thin Buffers Proto-Pattern
- Threshold-Governed Rollout Proto-Pattern