Summary: For teams integrating features sources from multiple projects, currently they must call separate API endpoints per project and manually manage flag state dependencies across project boundaries. This RFE is the ability to: (1) replicate a flag definition from one project to another, and (2) define cascade rules so that when a flag in Project A is killed or turned off, dependent flags in Project B automatically update accordingly.

Current workaround: Manual replication via Admin API (GET /splits → POST /splits across projects). No native cascade logic exists. A custom orchestration layer (webhook listener + Admin API writes) could approximate cascading but requires significant engineering effort from the customer and has no platform-level guarantees.

Why this matters: Multi-team organizations with separate FME projects for each product area hit this ceiling when building integrated surfaces. The current hard-boundary model between projects forces either (a) consolidating everything into one project (losing isolation) or (b) manual cross-project coordination (error-prone, not scalable).