Development

Design Traditions

18 traditions. All can change.

Traditions aren't rules—they're working agreements that proved useful. When they stop working, they change through demonstrated value.

Established
Provisional
Experimental
TR-001

Attribution Immutability

Creator + timestamp in content hash. Cannot be removed.

TR-002

Freeform Preservation

Freeform always available. Protocols are options, not mandates.

TR-003

Track Records Over Credentials

Demonstrated work, witnessed by collaborators.

TR-004

Witness Validation

Named witnesses making specific attestations.

TR-005

Temporal Authority

Standing decays without renewal. Recent work matters more.

TR-006

Workshop/Commons Separation

Private process, public output. Permission boundary.

TR-007

Local-First Data

Your archive on your machine. Sync on your terms.

TR-008

Export Freedom

Standard formats. Take everything. No lock-in.

TR-009

Living Governance

All traditions can change through demonstrated value.

TR-010

Graduated Trust

Dialogue before dispute. Grace before sanctions.

TR-011

Challenge Requires Alternative

Can't just disagree. Must propose solution.

TR-012

Many Centers

Local authority, shared infrastructure. Not one center.

TR-013

Fork With Dignity

Take your data, your reputation. No hostage situations.

TR-014

Configuration as Relationship

"I work like Sarah" not 847 preferences.

TR-015

Beta Testing Required

Features earn their way to stable.

TR-016

Sunset Paths Exist

Features can be deprecated, retired, rolled back.

TR-017

Community Votes

Major changes require community approval.

TR-018

Accessibility Audit

Features must pass accessibility check before stable.

Tradition Lifecycle

Experimental Provisional Established Challenged Changed

Nothing is permanent. Everything earns its place.