---
title: "Patterns"
url: /patterns
description: "Ten patterns shared by three 2026 design systems, each with a copyable example and where it breaks."
---

## §0 · patterns

# Patterns

I found these ten patterns in three of my own projects of 2026. I did not plan them. They came back each time, so I wrote them down.

Ten patterns, found separately in three projects. Each page has the statement, why it works, one copyable example, where it breaks and the cases that use it.

- [Honest gaps](/patterns/honest-gaps.md): Write "not enforced", "n/a" or "to be filled". Never fill a gap with a plausible value.
- [Report, do not block](/patterns/report-do-not-block.md): A validator reports and routes. It does not gate the agent on uncertain findings.
- [Proposal path](/patterns/proposal-path.md): A missing part becomes a proposal. It is never invented.
- [Do-not list](/patterns/do-not-list.md): Name the hallucination and give its replacement.
- [Typed spec, not free HTML](/patterns/typed-spec.md): Restructure the task so the error cannot happen.
- [Evidence, not authority](/patterns/evidence-not-authority.md): A design file or a prototype is evidence. The system is the authority.
- [Deterministic first](/patterns/deterministic-first.md): Code checks first. Model judgment comes second and is advisory.
- [Skills apply rules](/patterns/skills-apply-rules.md): A skill that disagrees with the rule book is a defect in the skill.
- [Authority order](/patterns/authority-order.md): When two files disagree, a declared rank decides.
- [Enforced by](/patterns/enforced-by.md): A decision counts when something checks it. An unchecked rule is a known gap, not coverage.
