Phrased as the person holding the job would phrase it, with where in the product it happens — so the mapping is checkable rather than aspirational.
- “Onboard a new customer the same way every time, so a colleague can pick it up”
- Tenant provisioning, entitlement configuration, the onboarding runbook
- “Set what the platform may do on its own, per customer, and get that in writing”
- Per-rule autonomy tiers, per-action-class opt-in, and the handover document
- “Look at fifty tenants on a Monday morning and know which three need me”
- Cross-tenant posture and incident review, and what is not aggregated for you
- “Work out whether a customer's complaint is a bug, a licence limit or correct behaviour”
- The four diagnostic paths: entitlement, permission, rule validation, rotation state
- “Keep the operator identity that spans customers separate from any one customer's identity”
- The control-plane operator identity boundary and why it refuses to share a signing key
- “Roll a sensor version across a fleet I do not own, and prove which hosts the update channel does not reach”
- The signed sensor update channel, what it verifies before applying, and the manual distribution it does not replace
- “Hand a customer's tenant back when they leave, or take it over when they arrive”
- Export, offboarding, and what does not export