
Most open projects change financial terms whenever they want, and apply them to work you've already done. The Nano Collective charter does the opposite: 30 days public notice, new work only. Today's terms protect tomorrow's contributor.



Open source projects usually die when their proposer quits. The Nano Collective plans for it instead: a 60-day clock on the whitepaper, anyone can pick it up, otherwise Paused, not Deleted.


A 1000-page batch can survive a dead LLM call. get-md's local model takes 5-10s per page and will fail, but the fallback to Turndown is on by default. A bad conversion hands off cleanly, the crawl keeps moving.



A migration is a refactor you're shipping to your own users. If the chain breaks in production, the data is gone. json-up types each step's up against the previous version's Zod schema, so the compiler fails the build before it ships.


Default cron lives inside your editor. If the TUI isn't open, the run doesn't happen. Nanocoder's daemon is a separate process, so a schedule.cron subscription fires the Skill headless with the terminal closed.


The match mode in tests.json is the only assertion you write. Pick semantic, startsWith, contains, exact, or llm-judge with criteria and a passThreshold, and that is how your fine-tune gets graded. Swap the dataset and you change what the model is being asked to be.