Sand sorter
Learn material names, safety limits and source uncertainty without pretending a sample is permission.
Story quests without pressure
Quests are not shame loops. They are friendly ways to turn a large idea into a small, chosen action with boundaries, receipts and a handoff.
Quest lanes.
Each lane gives people more choice and clearer next steps. They can try one role, pause, switch roles, or bring the note to someone better placed to continue.
Maker helper
Repair, reuse or prototype something small enough to check and improve.
OpenFerry mapper
Turn observations near the Gumpi gateway into evidence notes and respectful data asks.
OpenCare steward
Ask who needs rest, translation, access, consent and protection before the project gets bigger.
AI helper
Use AI for summaries, options and source trails while keeping human review central.
OpenStory guide
Make big systems understandable through scenes, rooms, handoffs and plain language.
Capability levels are learning stages.
A level should never say one person is worth more than another. It simply names what someone can try next, what support they need, and what boundary keeps the work safe.
- Notice: observe and write a simple note.
- Prepare: check permission, source and safety.
- Try: do a small lawful action.
- Handoff: leave clean Markdown for the next person.
Leaderboards need a ledger spine.
A leaderboard can be useful when it is really a public honour board: opt-in, receipt-backed, correction-friendly and careful about privacy. It should show support, contribution trails and useful handoffs, not pressure people into a score.
Receipts first
Show what happened, what source or receipt supports it, and who agreed it can be public.
OpenConsent first
Names, amounts, wallet details, youth details and sensitive context stay private unless explicitly released.
OpenCorrections first
Every public entry needs a way to amend, remove, challenge or add context.
Open