ifp

← Garden Patch Home · Form Definitions

• is_a::[[Form Type]]
• has_status::[[Seed Stage]]
• in_domain::[[Deep Context Architecture]]
• in_precinct::[[Garden Precinct]]

Pattern Form

Core question: “What resolves this recurring tension?”

A problem-solution pair in Alexandrian form: context, forces in tension, solution that resolves forces, consequences, connections. Generalized from experience, reusable across domains. Stable; validated or invalidated by cases.

Structural Contract

Every pattern form requires these sections:

• Context — The domain or situation where this tension arises.
• Forces — Competing demands or constraints pulling against each other. Name at least two forces in genuine tension.
• Solution — What resolves the forces. Stated directly, not as a recommendation.
• Consequences — What follows from applying the solution, including trade-offs.
• Sources — Origin material or experience the pattern was generalized from.
• Relations — Connections to other nodes, especially cases that validate or invalidate the pattern.

Optional: Known Results with concrete evidence (metrics, deployment data) that validate the pattern.

Naming heuristic: Alexandrian evocative — name the solution, lean toward imagery. “Progressive Summary Before Substance” not “Summary Pattern.” For anti-patterns, name the failure mode as a claim — a phrase you can agree or disagree with. “Informal Edges Poison the Graph” not “Precedent Poisoning.”

Typical Predicates

• is_a::[\[\[Pattern Form\]\]](Pattern%20Form.html)
• has_status::[\[\[Seed Stage\]\]](Seed%20Stage.html) or [\[\[Evergreen Stage\]\]](Evergreen%20Stage.html)
• in_domain::[\[\[Domain Name\]\]↑](../NODES.html#:~:text=Domain%20Name)
• extracted_from::[\[\[Source Document\]\]↑](../NODES.html#:~:text=Source%20Document) — provenance
• validated_by::[\[\[Case Form\]\]↑](../NODES.html#:~:text=Case%20Form) — evidence the pattern works
• composes_with::[\[\[Related Pattern\]\]↑](../NODES.html#:~:text=Related%20Pattern) — how patterns combine
• relates_to::[\[\[Principle Form\]\]](Principle%20Form.html) — values the pattern embodies

Exemplars

• [[Progressive Summary Before Substance]]↑ — Alexandrian structure with clear forces and resolution
• [[Knowledge on Three Axes]]↑ — cross-domain pattern with mapping table
• [[Three-Part Enforcement Stack]] — pattern from Self-Sovereign Identity domain with enforcement layers
• [[Informal Edges Poison the Graph]]↑ — anti-pattern naming: failure mode as a claim

Category

Action form — captures what to do and what happened.

Sources

Definition from [[Deep Context as an Architecture for Captured Reasoning]], lines 82-83.

Relations

• relates_to::[[Decision Form]] — decisions instantiate patterns in specific contexts
• relates_to::[[Principle Form]] — principles compress patterns into standing constraints
• relates_to::[[Model Form]] — models provide the structural context in which patterns operate
• relates_to::[[Inquiry Form]] — inquiries that identify recurring dynamics may crystallize into patterns

This site is open source. Improve this page.