Design Patterns

@@ -0,0 +1,27 @@
---
schema: foundry-doc-v1
title: "Design Patterns"
slug: patterns-index
category: patterns
type: topic
quality: complete
short_description: "The patterns category collects named design patterns realised across the platform — the editorial reverse funnel, the source-of-truth inversion, pairing-as-permission, the article-shell leapfrog, the Wikipedia-leapfrog chrome — each a recurring shape applied at the editorial, interface, or coordination layer."
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-05-09
editor: pointsav-engineering
paired_with: _index.es.md
---

The **patterns** category collects named design patterns realised across the platform. A pattern in this category is a recurring shape — applied at the editorial, interface, or coordination layer — that solves a structural problem in a way other parts of the platform reuse.

Patterns differ from substrates: a substrate is a load-bearing mechanism the platform depends on (and that compounds over time); a pattern is a design choice that can be applied or not. Patterns differ from architecture: an architecture article describes how a specific system is composed; a pattern describes a shape that recurs across systems.

## Reading order

[[source-of-truth-inversion]] (the canonical / view / ephemeral split) and [[pairing-as-permission]] (capability-based access control) are the most foundational patterns — read first. [[reverse-funnel-editorial-pattern]] explains the editorial pipeline used to refine drafts at scale. [[wikipedia-leapfrog-design]] and [[article-shell-leapfrog]] explain the wiki chrome's contract with reader muscle memory. [[collab-via-passthrough-relay]] documents the real-time-collab mechanism that holds no document state.

## See also

- [[substrate]] — foundational mechanisms patterns build on
- [[architecture]] — concrete platform architecture