Conflicts: transport collisions and team friction
What you'll learn
Sequence transports and own objects to avoid collisions (CDS + DCL + behaviour travel together); resolve priority friction with the impersonal gate, and log real disagreements as time-boxed exemptions.
- Transport collisions: CDS + DCL + behaviour definition must travel together (module 10) — sequence and own objects per sprint.
- Keep remediation transports small and frequently integrated; let the CI/CD ATC gate catch collisions early.
- Resolve priority friction with impersonal pre-agreed rules: the union variant, the baseline, the build-breaker policy (modules 8 / B1).
Two kinds of conflict dominate a Clean Core programme, and they need different tools. The first is technical: transport collisions. Because remediation and feature work touch the same objects, two transports can race — and Clean Core objects are unforgiving, since a CDS view, its DCL access-control role, and a RAP behaviour definition must travel together or the target system gets a half-activated, broken object (module 10's transport pitfall). The remedy is sequencing and object-level ownership: agree who owns each object for the sprint, keep remediation transports small and frequently integrated, and let the CI/CD ATC gate (module 8) catch a collision before it reaches the next system.
The second is human: friction over priorities and approach. A feature team sees remediation as a tax; an architect sees a shortcut as new debt. These are resolved not by argument but by the governance already defined — the union variant is the agreed rulebook, the baseline is the agreed line, and a new high-priority finding is a build-breaker by policy, not by someone's opinion in a review. When the rule is impersonal and pre-agreed, the conflict moves from 'you versus me' to 'does this pass the gate.'
Where a genuine disagreement remains — a rewrite that is expensive this cycle — the escape valve is a time-boxed exemption with a named approver and an expiry (module B1), not a silent override. That converts an argument into a logged, reviewable decision.
Key points
- Transport collisions: CDS + DCL + behaviour definition must travel together (module 10) — sequence and own objects per sprint.
- Keep remediation transports small and frequently integrated; let the CI/CD ATC gate catch collisions early.
- Resolve priority friction with impersonal pre-agreed rules: the union variant, the baseline, the build-breaker policy (modules 8 / B1).
- Move conflict from 'you versus me' to 'does it pass the gate.'
- Genuine disagreements become time-boxed exemptions with a named approver and an expiry — not silent overrides.
Source notes: clean-core-curriculum (delivery 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.