Lint rules engineers do not bypass on day three

Governance programs die when lint rules feel punitive or vague. We draft starter CI gates with messages that point to decision logs and owners, not anonymous policy PDFs. Engineers tolerate friction when they understand which customer promise or incident motivated the gate. We also train reviewers to treat exceptions as product features: if an exception repeats monthly, the lint rule or documentation—not the engineer—is wrong. That mindset shifts councils from courtroom dynamics to backlog grooming. Documentation receives the same care as code: examples use your service names, sample payloads resemble staging—not generic Lorem Ipsum contracts. When teams recognize themselves in the guidance, adoption stops being a memo exercise.