Table of contents
Is the handoff ready?
Use these checks before access expands or the first ticket begins.
Question
Ready: One observable feature flag precedence outcome
Needs work: A request to inspect the whole system
Fixture
Ready: synthetic identities that match no rule, one rule, several rules, a percentage split, and a stale rule set
Needs work: Customer data or shared credentials
Evidence
Ready: identity label, rule version, matching rules, evaluation order, returned variation, cache age, and reason
Needs work: A pass label without observed values
Approval
Ready: Product and release owners choose targeting intent, exposure, kill switch, and production timing.
Needs work: The contractor changes production alone
Reproduce the feature flag precedence failure safely
Two targeting rules match the same identity and different services evaluate them in a different order. Start with one case that can fail without touching customer records or production infrastructure. Write the expected result, stop condition, and reviewer beside the fixture.
Use synthetic identities that match no rule, one rule, several rules, a percentage split, and a stale rule set. Label every identity and artifact so a reviewer can distinguish test evidence from a live record.
Leave enough evidence for a second person , September 11 review
Capture identity label, rule version, matching rules, evaluation order, returned variation, cache age, and reason. Include the source revision and test time. If behavior changes between runs, retain both results.
Product and release owners choose targeting intent, exposure, kill switch, and production timing. A remote programmer can prepare the fixture, run bounded checks, and explain the result. New policy, privileged access, and release approval stay with the named owner.
Copy-ready brief
Put the operating agreement in writing.
Test one bounded feature flag precedence case against written acceptance rules.
synthetic identities that match no rule, one rule, several rules, a percentage split, and a stale rule set
Record identity label, rule version, matching rules, evaluation order, returned variation, cache age, and reason.
Product and release owners choose targeting intent, exposure, kill switch, and production timing.
Frequently asked questions
What should the first run prove?
It should show the expected feature flag precedence result for one controlled fixture.
What belongs in the handoff?
Include identity label, rule version, matching rules, evaluation order, returned variation, cache age, and reason, the source revision, and any untested condition.
Who approves a production change?
Product and release owners choose targeting intent, exposure, kill switch, and production timing.
Sources
- NIST Secure Software Development Framework
NIST guidance for managing software development risk.
- GitHub pull request reviews
First-party documentation for review and approval.
