Skip to content

Pattern Guidelines

How to Write a First Foundation Pattern

Purpose

This guide defines the writing standards, tone, and workflow for creating institutional, meta-, proto-, and anti-patterns within First Foundation.
Where the Pattern Templates page describes what fields each pattern must include, this page explains how to complete them — ensuring that every contribution is clear, consistent, and aligned with the NeuroSaeculum framework.

The intended audience is researchers, reformers, and civic designers contributing to the pattern library.
These guidelines ensure that each new pattern fits smoothly into the shared body of work.

1. Principles of Pattern Writing

Patterns are not essays or manifestos.
They are reusable design units — concise, structured summaries of how societies have solved recurring governance or institutional problems.

A well-written pattern must:

  • Be descriptive, not ideological.
  • Include both successes and trade-offs.
  • Be written in neutral, professional language suitable for translation and machine reading.
  • Serve as part of a living system, not an isolated idea.

2. Tone and Voice

Use the Professional → Technical tone defined in the Editorial & Design Guide.

✅ Neutral but candid:

“This pattern reduces capture risk through rotating leadership.”
❌ Avoid polemic phrasing:
“This pattern will save democracy from corruption.”

✅ Active voice:

“The council publishes audit data.”
❌ Avoid passive constructions:
“Audit data is published by the council.”

✅ Plain language over jargon:
When specialized terms are necessary (e.g., “polycentric governance”), define them briefly in-line.

✅ Respect the audience’s time:
Patterns are for practitioners and analysts. Write with economy — every sentence should earn its place.

3. Required Components

Every pattern, regardless of maturity, must include:

  1. Problem Statement – What recurring issue this addresses.
  2. Solution Summary – The design or process that resolves it.
  3. Trade-offs – What new tensions the pattern introduces.
  4. Known Uses or Precedents – Brief examples, ancient or modern.
  5. Validation or Testing Plan – How it might be evaluated in practice.

Patterns that lack these cannot be approved for publication.

4. Writing Conventions

Tense:

  • Use present tense for definitions (“This pattern emerges when…”).
  • Use past tense for examples (“In 2015, the government implemented…”).

Clarity:

  • Write for an informed but non-specialist audience.
  • Define acronyms on first use.
  • Use short paragraphs — one concept per block.

Consistency:

  • Treat pattern names as proper nouns.
  • Maintain parallel structure across titles (noun–noun or noun–phrase).
  • Example: Rotating Stewardship Council, Citizen Oversight Panels, Emergency Delay Protocols.

5. Citing Examples

Each pattern must include at least one recent example and one historical precedent.

  • Keep examples brief (2–3 sentences each).
  • Focus on how the structure worked — not the ideology behind it.
  • Use modern parallels to show recurrence and adaptability.

Example:

“Athens’ Council of 500 rotated annually to prevent capture.
Modern analogs include sortition-based citizen juries and rotating NGO boards.”

6. Linking to the Framework

Patterns must interconnect with the wider NeuroSaeculum system.

When drafting, identify how your pattern:

  • Supports one or more Design Goals (Trust, Adaptability, Stewardship, etc.).
  • Relates to the Hidden Circuitry model (dopamine, cortisol, oxytocin).
  • Feeds into the Civic Topology issue network or CivMMI maturity model.

At minimum, each pattern entry must include Related Patterns and Foundations & Inference fields.

7. Avoiding Common Pitfalls

🚫 Over-speculation: Patterns are descriptive, not prophetic.
🚫 Moralizing: Replace “should” or “must” with neutral phrasing (“works best when…”).
🚫 Data overload: Use data to illustrate, not overwhelm.
🚫 Reinventing existing entries: Check the Pattern Library to avoid duplicates.

When in doubt, write your idea as a Proto-Pattern first.

8. Review and Publication Process

  1. Draft using the appropriate Pattern Template.
  2. Peer Review – At least one internal review (AI or human).
  3. Integration Check – Ensure all references (Design Goals, Related Patterns) are live.
  4. Tagging – Assign pattern type (Institutional, Meta, Proto, Anti) and status (Draft, Review, Published).
  5. Publication – Add to the First Foundation Pattern Library and cross-link to related entries.

9. Continuous Improvement

Patterns are living documents.
As evidence accumulates, authors are expected to:

  • Revise data and validation notes.
  • Record failures and redesigns.
  • Document how the pattern performed under real-world stress.

Iteration is not a sign of weakness — it is the heart of resilience.

10. Companion References

Version & Attribution

Pattern Guidelines v1.0
Published November 2025 as part of the NeuroSaeculum consolidation cycle.
Author: Gary Kephart
Category: internal/guides, first-foundation, editorial-standards