OPA precedent — three-in-a-row water-carrier tap, not single-event hero pay

Situation

In 5/14 Nathan 1:1, with Nathan in middle of CVE response (third consecutive: dirty frag → copy-fail → current embargo), Peter declined to set the precedent of OPA/bonus payouts for single-event heroics. Maple — who carried water across all three events via consistent handoffs and status updates — is THE OPA candidate. David (took over secure-boot kernel build during Tate's absence) is growing into the role you'd want him to grow into normally → no OPA. Sultan (great dirty-frag work, up-late nights) → no OPA this round despite the effort. Nathan retained decision authority (Peter: I'm going to support whatever you decide. But, be cautious.) but the framework was set explicitly.

Reasoning

Pre-empting the CVE-response-equals-bonus-event precedent — because if you reward every event, the 17th one (when this is permanently the new normal) becomes either unaffordable or meaningless. By tying recognition to pattern-of-carrying-water rather than single-event-heroics, Peter rewards the behavior that scales (Maple's handoffs, hourly status updates, taking over when Nathan stepped out Thursday) rather than the behavior that doesn't (one weekend of late-nights). Subtly de-incentivizes the stack-bodies pattern Peter later flagged with Bjorn 3 days later — same value applied to comp.

Additional Context

Same 1:1 covered Rakuten sizing ($2M not $500k), Nathan's push-back-hard mode on Nutanix custom-engineering asks, the Fathom-Indian-dev inflation comp-adjustment ask (Peter asked is-he-different-from-everyone-else not just is-inflation-real), and the $750 Anthropic Sultan exploit bill (fine, expected). The OPA conversation was bounded — Nathan brought it up, Peter coached the framework.

Observed Evidence

Full ~2-minute exchange at 8:31-11:00 of Nathan 1:1 transcript. Peter explicitly named the three-in-a-row standard, named the seventeen-into-this future scenario as the reason to be cautious, and explicitly tied recognition to consistent water-carrying rather than late-night heroics. Nathan's I-understand-and-I'd-probably-wait-to-make-sure-we're-not-on-week-four close signals adoption of the framework.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis