Separate shared readiness from cohort readiness
Synthetic rollout N-276 has a shared configuration test G and separate training records for cohorts A and B. G and A training are complete; B training is pending. The agreed policy permits A-only activation if A’s support contact is available and the customer-facing scope says B is pending. Do not call the whole customer active or use A’s training as evidence for B.
| Gate | Cohort A | Cohort B | Activation result |
|---|---|---|---|
| Shared configuration G | Passed | Passed shared gate | Supports both groups |
| Training | Complete | Pending | A eligible; B blocked |
| Support and stated scope | Contact available; A-only scope stated | B pending disclosed | Activate A only |
Publish the actual enabled scope
- Check shared prerequisites
- Check each cohort separately
- Confirm support for enabled group
- Record partial activation explicitly
If the shared configuration fails, no cohort passes by its training record alone.
B training completes but B support is unavailable. Can the fixture now mark both active?
Show the worked answer
No. A remains active and B waits for its support coverage. Completing one gate does not resolve every cohort requirement.
Cohorts, gating and support rules are synthetic. This is customer onboarding scope, not a claim of feature flags or a provider rollout function.