Guides and playbooks
Governance Checklist
Keep feature flags controlled, reviewable, and removable so your delivery tooling stays an asset instead of becoming debt.
Naming and ownership
- Name flags after the decision they control, not after a temporary implementation detail.
- Keep keys stable once they are in code.
- Assign an owning team or service for every production flag.
Access and review
- Restrict production environment access to the people who actually need it.
- Review rule and target changes the same way you review application changes: with clear intent and incident awareness.
- Use service status and incident notes as part of release readiness.
Lifecycle hygiene
- Review the last evaluation date report regularly.
- Set a cleanup date when you create a temporary rollout flag.
- Remove flags that no longer affect behavior, not just those that are currently off.
Pair this checklist with the analytics and reporting guide so cleanup decisions are based on real usage, not intuition.
Next step
Take the next integration step in your own stack.
Start with the quickstart that matches your runtime, then return to the reference pages when you need exact request and payload details.