48 lines
1.3 KiB
Markdown
48 lines
1.3 KiB
Markdown
---
|
|
type: system
|
|
project: fidelity
|
|
status: active
|
|
systems: []
|
|
workstreams: []
|
|
people: []
|
|
related: []
|
|
tags:
|
|
- system
|
|
- fidelity
|
|
updated: 2026-04-20
|
|
---
|
|
|
|
# LaunchDarkly
|
|
|
|
## Role
|
|
|
|
- LaunchDarkly is the feature-flag platform used broadly in the Fidelity workflow.
|
|
- It is part of the normal delivery path for controlled rollout, environment-specific behavior, and gradual activation of changes.
|
|
|
|
---
|
|
|
|
## Stable Patterns
|
|
|
|
- LaunchDarkly can affect behavior by environment, context, targeting, timing, and cached flag state.
|
|
- When a bug appears only on certain builds or devices, LaunchDarkly evaluation is a valid investigation path even if local simulator checks look correct.
|
|
- Missing direct dashboard access does not remove LaunchDarkly from consideration; code-side evidence, payload inspection, and runtime evaluation still matter.
|
|
|
|
---
|
|
|
|
## Current Example
|
|
|
|
- During the April 20, 2026 REST migration investigation, LaunchDarkly was a central part of the debugging path because the behavior differed between local validation and consumer real-device reports.
|
|
|
|
---
|
|
|
|
## Risks
|
|
|
|
- Do not assume a simulator result fully represents real-device LaunchDarkly behavior.
|
|
- Do not treat missing direct Flagship dashboard access as proof that LaunchDarkly is not involved; indirect evidence still matters.
|
|
|
|
---
|
|
|
|
## Related Context
|
|
|
|
- `project-knowledge/02-work-items/pdiap-15838.md`
|