Skip to main content

​
Feature Flags

The current repository contains a lightweight inherited flag scaffold. The recommended target for this platform is stricter:
  • typed flag catalog in code
  • Supabase-backed runtime values
  • workspace-scoped overrides
  • explicit kill switches
  • migration flags for Charles cutover
  • one shared resolver across app, api, and worker

​
Why this matters

This repo is not just a frontend product surface. It needs flags that can safely control:
  • compatibility cutover
  • provider write paths
  • worker dispatch behavior
  • per-workspace migration state
  1. surface.* for UI exposure
  2. runtime.* for backend capabilities
  3. kill.* for emergency stops
  4. migration.* for workspace cutover control

​
Current implementation gap

The docs already assume a stronger operational flag model than the code currently provides. The next sequence should close that gap before broader rollout work continues.

​
Active flags