Diff: patterns/_index.es
From 1d92e7c to 1d92e7c
+0 / −0 lines
| Before | After |
|---|---|
| --- | --- |
| schema: foundry-doc-v1 | schema: foundry-doc-v1 |
| title: "Design Patterns" | title: "Design Patterns" |
| slug: patterns-index | slug: patterns-index |
| category: patterns | category: patterns |
| type: topic | type: topic |
| quality: complete | 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." | 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 | status: active |
| bcsc_class: public-disclosure-safe | bcsc_class: public-disclosure-safe |
| last_edited: 2026-05-09 | last_edited: 2026-05-09 |
| editor: pointsav-engineering | editor: pointsav-engineering |
| paired_with: _index.es.md | 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. | 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. | 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 | ## 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. [[collab-via-passthrough-relay]] documents the real-time-collab mechanism that holds no document state. | [[source-of-truth-inversion]] (the canonical / view / ephemeral split) and [[pairing-as-permission]] (capability-based access control) are the most foundational patterns — read first. [[collab-via-passthrough-relay]] documents the real-time-collab mechanism that holds no document state. |
| ## See also | ## See also |
| - [Substrate](/substrate/) — foundational mechanisms patterns build on | - [Substrate](/substrate/) — foundational mechanisms patterns build on |
| - [Architecture](/architecture/) — concrete platform architecture | - [Architecture](/architecture/) — concrete platform architecture |