A service catalog that is only an inventory becomes a wiki nobody updates. What makes one load-bearing is that every entry is continuously evaluated against checks, and that those checks roll into levels a team can actually be held to. The design constraint is subtler than it looks: a rubric that fails everything on day one gets switched off, so levels have to be cumulative and reachable, and checks have to know when they do not apply.