Service Scaffolding
Generating a new service with observability, CI, security and ownership already wired in, so the standard is the default rather than a checklist.
Every organisation has a list of things a service should have: structured logging, trace propagation, a health endpoint, a CI pipeline, dependency scanning, a catalogue entry, an on-call rota, a dashboard. Left as documentation, each new service implements some subset, and the subset varies.
Scaffolding makes the list executable. A generator produces the repository with all of it present and working, which changes compliance from an audit problem into a starting condition.
The hard part is not generation but the day after. Templates evolve; services generated from last year's template diverge, and there is no mechanism to pull improvements forward. Two approaches work: keep the shared behaviour in versioned libraries and base images that the template merely wires up, so upgrading is a dependency bump; or support re-templating, which is harder. Choosing neither produces a fleet of services that were compliant on their first day and have been drifting ever since, which is the common outcome.