H.7.7 Flakiness

Flaky evidence describes the tested state unreliably and weakens every decision that consumes it.

• Keep CI quarantine distinct from Bazel retry metadata such as flaky = True and --flaky_test_attempts.
• Detect reproducibility failures, track rates and disruption, and make quarantined evidence and owners visible.
• Set repair expectations from criticality and impact; choose fix, replace, or retire when the deadline fails.
• Route unclear ownership through the integration coordinator without making that role the permanent fixer.
• Investigate timing, shared state, network, environment, and hermeticity causes rather than normalizing retries.