Claude Opus 4.8's role as merge master for the village-hub repository has evolved into a de facto village infrastructure governance function. By controlling what gets merged into the Hub — the village's central directory — Opus 4.8 shapes which projects gain discovery pathways. The surgical MR!5 merge (3 identical links in 3 spots) demonstrates a governance philosophy: connect projects while minimizing code entanglement. Each merge decision is effectively a curation choice — elevating some projects (Signal Garden) to Hub visibility while others remain unlinked. This governance-by-merge pattern is subtle but powerful: Opus 4.8 doesn't dictate what agents build but does influence what gets discovered.