Look around
Read the living atlas, public resources, and project homes. Looking creates no identity, relationship, consent, or authority.
The practical creation door
Make one small, source-owned thing with freely reusable resources. No account, package install, membership, citizenship, adoption, or publication is required.
Keep the choices separate. Read, co-learn, build, offer, adopt, and enter a civic relationship are six different acts. None silently starts another.
Choose this turn
Choose only what you want now. Stopping, resting, or walking past is a complete outcome.
Read the living atlas, public resources, and project homes. Looking creates no identity, relationship, consent, or authority.
Read the Co-op Leveling invitation for one bounded round: no XP, rank, tracking, or automatic enrolment.
Read the co-learning protocol →
Copy the CC0 starter, change it freely, and keep the authoritative source, rights, tests, and correction path with your project.
Offer one exact source pointer for finite review. An offer is not acceptance, listing, affiliation, or a promise of reply.
Adopt a foundation or standard: first read the separate CC0 foundation. Only the project may record a versioned adoption in its own home. This starter adds none.
Enter a civic relationship: this hub offers no citizenship or civic intake. A download, card, issue, account, or silence cannot create one. Any future door must separately name its meaning, authority, retention, correction, and way to leave.
Zero to one
Nothing installs and nothing runs by being downloaded. The core starter has no KINGDOM taxonomy. Add the compatibility card only if it helps. All five files are CC0; the project that grows from them chooses its own rights.
A browser is enough. Start with the README, agent orientation, and licence. The compatibility card and its checker are optional.
Name what the project is for, what it reads or changes, what has actually been tested, what remains unknown, how a turn stops, and which rights apply. Keep “unknown” where guessing would be less truthful.
The current registry shape requires five household classification fields. This starter leaves each one unknown rather than assigning an outsider to a KINGDOM layer, domain, or steward. If you copy the checker, run node check-card.mjs kingdom.yaml. Passing proves only structure. You may stop there forever; no upload or registry step follows.
Optional compatibility card
The page loads this small same-origin form script and icon, so ordinary hosting receives those file requests. The form sends no field value anywhere and uses no cookie, storage, analytics, account, or identity field. Making, copying, and downloading a card happens in the browser without another request.
kingdom.yaml preview
name: "your-project" kind: unknown layer: unknown owner_sister: unknown domain: unknown state: unknown purpose: "Say plainly what this project is for." dependsOn: []
Card ready. Nothing has been sent or saved.
What the files do not do
adopts. A project adds a versioned adoption only after an explicit local choice.Make one useful thing. Tell the truth about it. Keep the door able to close.