Exceptions
An admin can except a finding with a reason and an expiry. The check turns green, the exception is logged, and the merge ledger records the merge as excepted, not clean.
Exceptions in Cloud
The exception is scoped, reasoned, and expiring. When it lapses, the next evaluation of that head is a block again if the finding is still present. Members cannot grant one.
Merge ledger
One row per repository and head that merged: the receipt, the verdict, the outcome. clean, excepted, bypassed (merged with no passing verdict and no exception), unresolved (merged on an indeterminate head). Bypasses are recorded, never hidden. The Adoption page is a projection over this ledger.
In-source exceptions
Put the directive immediately before the statement it applies to. Name the exact FUI code and record a reason; use a real calendar expiry when the exception is temporary. These are narrow, auditable exceptions — not a substitute for changing the contract through govern.canonicalBridges or another documented config field.
// fragments-allow FUI2005: vendor-owned color, tracked in DS-482 expires="2026-12-31"
const Banner = () => <div style={{ color: "#39594d" }} />;// @fragments-expect-error FUI1003 reason="legacy import migration tracked in DS-611" expires="2026-12-31"
import { Button } from "@mui/material";For import-path findings, see FUI1003.