Examples
The components are small. What matters is how they sit together. These are compositions — how the pieces combine — not the component library itself. That's in the repository, one example per component; here are a few of them working as a whole.
What the commons holds
Seed saved for spring sowing
2.4 kg
viable 1.6–2.4 kg
Verified germination test, October
Seed garlic — this season's stock
2 of 3 stages verified · grown within 40 km
- Saved on site — north plots 0 km
Last year's best bulbs, held back from the harvest.
Verified harvest log - Topped up — neighbouring allotment 40 km
Swapped at the autumn seed exchange. Same cultivar.
Self-reported - Soil contaminants — north plots —
Tested clear for lead and cadmium before replanting.
Verified lab result, 2026
Aggregate figures, an honest range in place of a false single number, a status that only turns green once its evidence is linked, and a supply chain traced stage by stage. Principles 02 and 03 together — supporting the decision of what to allocate, and what to plant next season.
Built from: resource-bar, eco-stat, verification-status, provenance.
This season's work
Rebuild the cold frames
Spring seed-swap
- Book the hall and confirm the date
- Posters to the three notice boards
- Ask the bakery about leftover bread
Open the tool library on Saturdays
Survey the north plots for next year
Status is carried by the activity colour and the words together — never colour alone — so the list stays scannable in greyscale, in print, or on e-ink. Principle 03, applied to the question of where collective effort should go next.
Built from: cards, activity-badge, badge, lists, dividers.
Join the next repair café
Every field is labelled and associated; required fields say so in both text and symbol; the validation is the browser's own, so it works with no JavaScript. Principle 01 — and proof this is a complete design system, not only eco widgets. The decision it supports: getting someone from interested to enrolled.
Built from: form-field, text-input, select, radio, checkbox, button.
There is no per-user component here, and there won't be. The data is about the group, never the person — no individual breakdowns, no per-member alerts. The absence is the policy, not an omission.
Building these is the system's own first composition test. Where a composition needs something the components don't yet provide, that's logged as feedback, not papered over.