Participation should be legible from the first visit.
The site should offer multiple valid entry points:
- attend a working session
- contribute a use case
- review a release page
- share a field note
- help shape governance language
- contribute code, documentation, or implementation feedback
Not every participant will be a developer, and the site should signal that clearly.
Good participation design also means helping people understand what stage the work is in. At an early stage, the most valuable contribution may be clarifying use cases, naming constraints, or identifying where institutional variation is likely to matter. Later, contributions may shift toward piloting, documentation, testing, and governance.