
Merging a Nano Collective whitepaper only opens a 30-day public review window. The build / decline / iterate call comes later, recorded on the page itself.

https://nanocollective.org


From the Nano Collective Economics Charter: deliverable, acceptance criteria, and amount are agreed in writing before any bounty, designated donation, or bespoke partnership starts. No contributor's terms change after the fact without their consent.

https://nanocollective.org



getmd --batch urls.txt --json streams one JSON object per line, so the output pipes straight into jq or a vector store without buffering the whole batch. Composes with --sitemap, --use-llm, and --cache.

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



json-up: when migrations live in their own files, wrap each in `createMigration` (or `createAsyncMigration`) so TS infers it. Feed the result into `createMigrations().add(...).build()` and the whole chain stays typed. https://github.com/Nano-Collective/json-up


Nanocoder's /tune adds a "nano" tool profile for 1B-class models: ~150-250 token system prompt, no subagent delegation, no AGENTS.md, single-tool enforcement. A preset flips everything for low-end hardware.

https://github.com/Nano-Collective/nanocoder


Read the loss curve, then tune. Nanotune defaults: 150 iters, 5e-5 LR, batch 4. Train and val should fall together, ending ~0.1-0.3. Val rises, train keeps falling = overfit, cut iters. Both flat = underfit, push iters or LR.

https://github.com/Nano-Collective/nanotune
