In an AI-driven system, Capabilities (CAP-XX) are the atomic units of value. They replace vague "User Stories" with rigorous, enforceable functional definitions. This standard governs how we define, register, and evolve them.
2. The Standard (The Floor)
[MUST] Atomic Definition: Every feature MUST map to a unique Capability ID (CAP-[DOMAIN]-[ID]) in the Registry.
definition must include: Data Touched, Security Posture (RLS/Authz), and Audit Requirements.
[MUST] Registration First: You MUST register a Capability in generated/capabilities.json (via the CLI or JSON edit) before writing the implementing code.
[MUST] Binary State: A Capability is either Planned, Experimental, Stable, or Deprecated. "Mostly working" is not a valid state.
[MUST] The Roadmap: The "Roadmap" is simply the aggregate list of Planned capabilities with target dates.