Peer-edge governance
Govern the sideways pathways — operator-to-operator forwarding and store-to-store replication — that multiply everything else.
What it changes
Who can pull it
What it looks like institutionally
Errors don't only flow down the pipeline; they flow sideways. An agent's output forwarded into a colleague's workflow, a contaminated cache replicated into a knowledge base — peer edges couple parts of the system that governance treated as separate, so one team's lax practice becomes everyone's ambient risk.
Peer-edge governance names these pathways and applies the same controls as anywhere else: provenance survives forwarding, replication requires authorization, shared stores get the strictest write rules because they have the widest read audience.
The scaling warning: peer pathways multiply with headcount and integrations. A deployment that was self-limiting as a pilot can cross the sustainability threshold purely through growth in sideways connections.
Addresses: Peer contagion · Cross-store contamination. Test a version of this lever in the PAN Lab.