Examples
Example Service Catalog Entry
Use this example to show the expected level of service ownership and operational metadata.
Example entry
# Service: Billing API
## Summary
Handles billing account lookup, invoice retrieval, and payment status for
customer-facing applications.
## Ownership
- Owning team: Revenue Platform
- Technical owner: Revenue Platform Lead
- Business owner: Finance Operations
- Support channel: #billing-api-support
- On-call rotation: revenue-platform-primary
## Links
- Repository: github.example.com/acme/billing-api
- Pipeline: ci.example.com/billing-api
- Dashboard: observability.example.com/billing-api
- Logs: logs.example.com/billing-api
- Runbook: docs.example.com/runbooks/billing-api
## Runtime
- Platform: managed containers
- Environments: dev, staging, production
- Regions: us-east-1, us-west-2
- Dependencies: billing database, payment provider, customer API
## Operations
- SLO: 99.9% successful invoice lookup over 30 days
- Rollback: promote previous signed container image
- Escalation: SEV2 for payment status failures above thresholdNotes
Use synthetic examples in public documentation. Real service catalog entries may contain sensitive internal URLs, owners, or architecture information.