Summary
Introduce a lightweight feature flag mechanism to safely ship and roll back new features without a redeployment.
Scope
- Define a central
FEATURE_FLAGS map (e.g. environment-driven or config-file-driven)
- Each flag is a named boolean:
on | off
- Provide a
isEnabled(flag) helper usable in both server actions and React components
- Flags are user-agnostic — they gate code paths globally, not per user
- Document the convention for wrapping new features behind a flag at PR time
Acceptance criteria
- A feature can be disabled instantly by flipping a flag, with no code change required
- The flag system is decoupled from the user tier / access gating logic
Summary
Introduce a lightweight feature flag mechanism to safely ship and roll back new features without a redeployment.
Scope
FEATURE_FLAGSmap (e.g. environment-driven or config-file-driven)on | offisEnabled(flag)helper usable in both server actions and React componentsAcceptance criteria