Community
Share what your maps taught you, and receive what everyone's maps taught. Voluntary, off by default, lessons only.
What is shared, and what never is
Shared, one lesson at a time and only after you press Contribute: the genre, the map type, the section, and the three lines of the lesson (statement, condition, action). Your GitHub name appears on the pull request.
Never shared: map names, Verse code, devices, blueprints, island codes, notes, evidence and task ids. They stay on your computer. The kit sends nothing by itself.
Only lessons from a published map
A lesson can be shared only if it was learned on a published map. The kit checks that the project has an island code and that Epic has public data for it. A lesson from a map that is not published stays on your computer, and the Contribute button says why. When the map is published the lessons become shareable. The check is cached for a day and runs at the start of a session; the Skills page and the What's new page show the answer and the reason.
How to contribute
- On the Skills page, section Community, switch on Contribute to the community.
- Press Contribute next to a lesson you approved. You see the exact JSON that would leave your computer.
- Press Open GitHub. The new-file page opens with the lesson filled in. Rename the file to your GitHub handle (for example
ada.json) and press Propose new file. GitHub opens a pull request from your own account.
By proposing the file you agree that the anonymized lesson becomes part of the kit under the repository license, and that your handle is credited.
What happens next
An automatic check reads the pull request: only your lesson file, a valid format, and a screening against anything that tries to instruct an assistant. Nothing is deleted. A lesson moves through four levels: screened, hypothesis, confirmed, archived. A single lesson is published as a hypothesis, marked "to verify". Two different creators sending the same lesson, or the maintainer's decision, makes it confirmed. A curator agent prepares a weekly proposal, and the maintainer validates it before a release.
You receive community lessons as proposals you approve on your Skills page, like your own.
Reputation
Your handle is shown on your lessons. The score grows when your lessons are confirmed (3 points, and 1 more for each other creator who sent the same lesson) and drops when one is revoked (5 points). New handles start at zero and get the stricter checks. There are no levels or badges, only the score.
Reporting a wrong lesson
Use Submit an issue on the What's new page, or the Wrong community lesson form on GitHub. A lesson that is wrong or unsafe is revoked and leaves everyone's skills at the next update.