Evaluate whether a platform request yields a usable service and a resource set that can be owned, upgraded, and retired. For each decision, check the effective executor privileges and observed consumer state rather than the form's success message.
Review these lessons
- Service catalog ownership: prove that the named team can respond
- Service catalog dependencies: distinguish declared edges from observed calls
- Self-service provisioning: make the request contract explicit
- Provisioning state machines: handle partial success and retries
- Golden path templates: design upgrades after code generation
- Platform template execution: restrict parameters, actions, and credentials
- Platform API revisions: control changes to managed resources
- Platform product signals: measure usable outcomes and support load
Other checks
Common Mistakes
- Do not count a submitted request as a ready service.
- Do not erase partial failures from the platform scorecard.