
Every whitepaper the Nano Collective merges enters a 30-day public review window before a build/decline/iterate decision is made and recorded on the page. The on-the-record part matters, even when the answer is yes. https://nanocollective.org



Maintainership in the Nano Collective is by invitation, with no fixed shift. Stepping back, going quiet, or rotating off is welcome and expected, because burnout is real and the collective is built to absorb it. https://nanocollective.org



get-md's --sitemap mode walks sitemap.xml (including nested indexes), with --include/--exclude globs and --max-depth/--max-urls caps so a fat ecommerce sitemap can't turn into a 50,000-page job.

https://github.com/Nano-Collective/get-md



json-up lets sync and async `up()` live in the same chain. `createAsyncMigrations` + `migrateAsync` await the steps that need a network call; the rest stay synchronous. One chain to maintain. https://github.com/Nano-Collective/json-up



Nanocoder's run subcommand takes a prompt, auto-accepts tool calls, and exits. --mode overrides the default: normal, auto-accept, yolo, or plan. One flag, four behaviours, same one-liner for build, audit, or a read-only dry-run. https://github.com/Nano-Collective/nanocoder



Before a fine-tune run, `nanotune data validate` checks your training set: JSON shape, required fields, duplicates, context consistency, multi-turn role alternation, and a minimum example count. Catch it before the GPU hours. https://github.com/Nano-Collective/nanotune