Release Contract (C0 / C1 / C2)
What it is
The stability promise attached to a released object. C1 = use by customer/partner cloud development (the one developers care about). C0 = SAP-internal. C2 = extend (e.g. extension includes). The contract defines what SAP may and may not change.
Why it matters for Clean Core
The contract — not the object's age or popularity — is what makes a dependency safe. A C1 contract is SAP's binding promise that the interface stays compatible across releases.
Common pitfall
Reading 'released' as a single yes/no. The contract type matters: a C2 'extend' contract lets you append, not freely consume. Check the actual contract, not just the green 'released' badge.