Governance: variants, baselines, exemptions, ownership
What you'll learn
Name an owner for the rulebook and the baseline, make every exemption carry a reason, an expiry, and an approver, and treat new high-priority findings as build-breakers.
- The check variant is the agreed rulebook; it needs one named owner.
- A baseline is a dated snapshot of accepted existing debt — new issues still get flagged.
- Every exemption carries a reason, a validity date, and an approver — an audit trail.
Clean Core is enforced by an automated quality check SAP calls the ABAP Test Cockpit (ATC). The set of rules it applies is bundled into a named 'check variant' — think of it as the agreed rulebook. Someone must own that rulebook, because if everyone can change the rules, the standard means nothing.
Existing systems start with years of accumulated issues, so teams take a 'baseline': a dated snapshot that says 'this is the debt we already have — only flag us for anything new.' A named owner also holds the baseline. Where a genuinely unavoidable issue remains, the team files an exemption, and a good exemption always carries three things: a reason, a validity date (when it expires), and an approver. Together those form an audit trail you can defend.
The governance posture that actually works is to treat any new high-priority finding as a build-breaker — the change does not ship until it is fixed or formally exempted. Naming the owners of the variant, the baseline, and the exemption process is the single most important governance decision leadership makes.
Key points
- The check variant is the agreed rulebook; it needs one named owner.
- A baseline is a dated snapshot of accepted existing debt — new issues still get flagged.
- Every exemption carries a reason, a validity date, and an approver — an audit trail.
- Treat new high-priority findings as build-breakers, not suggestions.
Examples
A finding is exempted with: reason ('legacy interface, rewrite scheduled Q4'), validity ('expires 31 Dec'), and approver (the named architecture lead). An auditor can see exactly who accepted what, and until when.
Source notes: clean-core-curriculum (business synthesis)
Ask Claude
Build a prompt from this lesson + your question and open a fresh Claude chat with it pre-filled — handy for adapting a before/after pattern to your own object.