2 min lesson
Why each domain is first-order, not back-office
Use "Why each domain is first-order, not back-office" to explain each part and the role it plays.
Step 1 of 2
- Auth
- Runs on every request; a failure is a security incident or a full lockout.
- Agent backend
- Powers the headline feature; slow or flaky here means the product feels broken.
- Webhooks
- At-least-once event delivery to customers; lost or duplicated events erode trust quietly.
- SCM
- The bridge to users' actual code; provider outages must degrade gracefully, not cascade.
Because this is shared infrastructure, the metric that governs it is blast radiusHow much breaks if a change goes wrong; the scope of potential damage. Press Enter for the full definition.. A bug in one product feature annoys the users of that feature. A bug in the auth path or the webhook dispatcher can take down everyone at once. That asymmetry is why clean contracts and reliability bars matter here more than raw feature velocity.
On a product team the question is "can we ship this faster." On Core Services the question is "what is the blast radiusHow much breaks if a change goes wrong; the scope of potential damage. Press Enter for the full definition. if this is wrong," because every product team depends on you. The job is to make the foundation boring and dependable so the floors above it can be exciting. Walk into the loop optimizing for blast-radius containment and clean boundaries and you'll sound like someone who has actually owned shared infrastructure.
When asked what this team owns, don't just list four nouns. Name the four domains, then say the one sentence that ties them together: "They're the shared layer between product surfaces and infrastructure, so blast radiusHow much breaks if a change goes wrong; the scope of potential damage. Press Enter for the full definition. and clean contracts outrank feature velocity." That framing shows you understand why the charter exists, not just what's in it.