Put the contract in the background.
All strategy · 04 / 08
Shared contracts should exist early and support the community story from the background.
Identity, policy, audit, events, and portability enter the story as protections for memory, trust, and autonomy. The headline stays with the community.
The public contract
The public contract should be small, understandable, and useful before it becomes ambitious.
Never ask people to care about a protocol before they can see what it protects. Start with the contract that preserves a real community record.
The order
The community sees the problem: its record is scattered, its authority unclear, its exit uncertain.
The product solves that problem in a narrow, complete experience.
The contract underneath is revealed as the reason the experience works, and the reason it will keep working.
The contract is the foundation. The community is the reason for the foundation.