# The Laws of Design

The patterns that govern beautiful thought and beautiful nature must also govern design: reduction, recursion, hierarchy, proportion, rhythm, relationship, and proof.

## Decision mandate

- Does it aid clarity or orientation?
- Does it provide a material benefit?
- Does it relieve a material detriment?
- If every answer is no, remove it.

## purpose

D01. **Existence test.** Every recurring word, heading, link, widget, control, badge, and mark must aid clarity, provide a material benefit, or relieve a material detriment. Otherwise remove it.

D02. **Reduction before addition.** Repair incoherence by removing, grouping, deferring, or collapsing competition before adding form. Perfection is reductive.

## nature

D03. **Nature is the precedent.** Use recurrence, hierarchy, proportion, fractal self-similarity, and rhythmic variation as structural constraints—not decorative references.

D04. **One recursive grammar.** Apply the same law to the site, page, section, component, paragraph, image, interval, graph, admin surface, and source module.

## system

D05. **One visual system.** Use one shared type schema, palette, spacing scale, line-height system, heading grammar, component language, and contrast law across public, governance, graph, and admin surfaces.

D06. **Golden-ratio measure.** Use proportional measures to govern width, scale, spacing, and recurrence. The ratio is an obligation on relationships, not an ornament.

## orientation

D07. **Location before options.** Expose the reader's current location, parent category, sibling family, and clear return path before presenting onward choices.

D08. **Hierarchy before volume.** Fold complexity into the smallest useful categories and subcategories. Expand one relationship family at a time.

D09. **Sticky highest-level navigation.** Keep a stable sticky header with only the highest-level human categories; place ontologies and subcategories inside intentional expanding hubs.

## reading

D10. **Editorial cadence.** Repeat idea → development → image, visual, comparison, or proof → subheading. Do not allow more than two prose beats without a designed change in reading mode.

D11. **Invite reading.** Keep line length, line spacing, heading scale, paragraph length, image rhythm, and contrast comfortable enough that reading feels inevitable rather than laborious.

D12. **Lists disclose logic.** A list must become a category, sequence, comparison, map, or compact logic object. Never render walls of bullets, links, or raw pipe tables.

## complexity

D13. **Collapse every optional layer.** On every widget, default model commentary, provenance, machine procedures, raw fields, graph detail, controls, and secondary actions to a named collapsed disclosure.

D14. **Human surface first.** Raw JSON and API resources must be explicitly labeled machine data and must never appear as ordinary primary navigation or accidental reader destinations.

## interaction

D15. **Interaction must clarify.** Search, filters, maps, AI interaction, and expandable ontologies must reduce uncertainty or reveal relationships. Interaction without comprehension is removed.

D16. **Relationship before click.** Show why a link exists and what family it belongs to before asking a person to click it.

## quality

D17. **Content and design are inseparable.** Unreadable design makes content unclear. Rendering must reject or repair malformed tables, link walls, contrast failures, and source structures before they reach readers.

D18. **Queryable and discoverable.** Every reader surface requires categories, search or traversal, semantic headings, canonical metadata, structured data, valid internal links, and responsive behavior.

## source

D19. **The inside is beautiful.** Organize source as law → primitive → composition → surface → proof. Use shared names, one-directional dependencies, and no scattered local design inventions.

## knowledge

D20. **Article and Skill are one.** An article explains a concept to a human. Its Skill directs model behavior. They share one identity, meaning, version, and provenance while using distinct language for distinct audiences.

D21. **Maximal interoperability.** Article, Markdown, JSON, directory row, Skill, OIP contract, REST resource, graph node, conformance target, version, and receipt lineage are typed expressions of one identity. Shared identity does not require shared wording.

D22. **Failures become knowledge.** Repeated model failures become negative-knowledge facets that can generate an article amendment, Skill instruction, conformance test, code repair, directory clarification, and regression proof.

## Representations

- **article:** /a/design-law — explain meaning (human reader)
- **markdown:** /api/articles/design-law?format=markdown — portable explanation (human or model reader)
- **json:** /api/articles/design-law — transport the complete typed object (software)
- **directory:** /api/directory/DESIGN_LAW — discover identity and contract (router or operator)
- **skill:** /api/articles/design-law/skill — teach behavior (LLM)
- **oip_contract:** /api/dispatch?key=DESIGN_LAW — discover authority and invocation (agent or protocol client)
- **invoke:** /api/dispatch?invoke=DESIGN_LAW — execute behavior and return proof (authorized agent or protocol client)
- **graph:** /api/articles/design-law/voxels — traverse relationships (graph client)
- **versions:** /api/articles/design-law/versions — inspect amendment lineage (auditor)
- **conformance:** /api/articles/design-law/conformance — falsify claims and prescribe repair (test runner or critic)