Explore flag management/write API for OFREP

Context

At KubeCon EU 2026, the AI workflow integrations discussion (recap) raised the question of whether we can define a standard way for tools to create and manage feature flags programmatically.

Problem

OFREP currently defines a read/evaluation API. There's no standard for creating, updating, or deleting feature flags. This means AI tools (MCP servers, agents, IDE integrations) that want to manage flags have to use vendor-specific APIs.

As AI-assisted development workflows become more common, having a standard write API would enable tools to create and manage flags without being coupled to a specific vendor.

Questions

• Should OFREP define a flag management API (CRUD operations)?
• What is the minimal surface area that would be useful (e.g. create flag, update targeting, toggle on/off)?
• Is this in scope for OFREP or should it be a separate protocol?
• How do we handle authorization and permissions for write operations?

Related

• #39: OFREP 1.0 roadmap

Start by reviewing OFREP's existing read/evaluation API and related issue #39, the OFREP 1.0 roadmap. Investigate whether CRUD flag management belongs in OFREP or a separate protocol, define the minimal useful write surface and authorization concerns, and document a decision or proposal.