coulomb/feature-control
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

First implementation

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-15 00:42:14 +02:00
parent 542d7c22be
commit fa39883aec
18 changed files with 1352 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files

63
specs/UseCaseCatalog.md
View File

@@ -41,6 +41,69 @@ A canon interface card stub is at `docs/canon-interface-card.md`.**
---
## 2.5 Scored Use Case Summary (helix-forge UseCaseScoringStandard.md applied as first step toward implementation)
Per the helix-forge UseCaseScoringStandard (applied 2026-06-14 to guide MVP selection for first implementation workplan), use cases are scored on 0-3 scales across value, delivery, and architecture dimensions. Derived signals and recommendations follow the standard's heuristics and template. Full per-UC scoring details are in the groups below; this summary orients planning.
| ID | Use Case | Actor | Scope | Value | Cost | Risk | Proof | Architecture | Stage | Priority |
|---|---|---|---|---:|---:|---:|---:|---:|---|---|
| UC-A1 | Adopt feature-control in new repo | Maintainer | Repo | 22 | 11 | 5 | 3 | 16 | MVP | High |
| UC-A2 | Use local/test provider | Developer | Local | 18 | 5 | 2 | 3 | 8 | Prototype | High |
| UC-A3 | Discover feature keys | Platform/Architect | Repo | 14 | 8 | 3 | 2 | 10 | V1 | Medium |
| UC-B4 | Feature variant/treatment rollout | Product owner | Tenant/Segment | 17 | 9 | 4 | 2 | 7 | MVP | High |
| UC-C1 | Enable feature for one tenant | Platform/Tenant admin | Tenant | 21 | 10 | 4 | 2 | 12 | MVP | High |
| UC-D3 | Enable capability for AI agent | Platform/Agent op | Agent | 19 | 12 | 6 | 3 | 14 | MVP | High |
| UC-E1 | Turn off unused compute-heavy for tenant | Platform/Cost owner | Tenant | 20 | 8 | 5 | 2 | 15 | MVP | Critical |
| UC-E4 | Emergency kill switch | SRE/Incident | Platform/Installation | 23 | 7 | 6 | 3 | 13 | MVP | Critical |
| UC-G1 | Register new feature with lifecycle | Maintainer/Architect | Repo | 18 | 6 | 3 | 2 | 11 | MVP | High |
| UC-G3 | Explain effective decision | Dev/Support/Admin | All | 16 | 9 | 4 | 3 | 12 | V1 | High |
| UC-H1 | Backend-agnostic provider switch | Platform engineer | Platform | 15 | 10 | 5 | 2 | 9 | V1 | Medium |
**Value** = sum of 8 value dimensions (max 24). **Cost** = sum of 7 delivery cost dims (max 21). **Risk** approx highest risk dim. **Proof** = Proof Value. **Architecture** = sum of 6 arch dims (max 18).
### 2.5.1 Prototype Candidates
High learning/proof, low-moderate effort/risk.
| ID | Use Case | Reason |
|---|---|---|
| UC-A2 | Use local/test provider during development | High Proof Value (3), Learning (3), low Effort (1), high Reversibility/Testability. Validates resolver and context without backend. |
### 2.5.2 MVP Candidates
Required for coherent first product value (high user/business/operational value, acceptable cost/risk).
| ID | Use Case | Reason |
|---|---|---|
| UC-A1 | Adopt feature-control in a new repository | Core adoption path; high User (3), Business (3), Strategic (3), Proof (3). Thin wrapper + canonical keys + safe defaults. |
| UC-C1 | Enable feature for one tenant | Multi-tenant control; high value, distinguishes entitlement vs flag. |
| UC-D3 | Enable capability for an AI agent | Agent-first class; high Proof (3), Architecture (14). |
| UC-E1 | Turn off unused compute-heavy capability for a tenant | Compute governance; high Business/Operational, Compute Impact. |
| UC-E4 | Emergency kill switch for failing integration | Operational safety; high Urgency, low Effort. |
| UC-G1 | Register a new feature with lifecycle metadata | Governance hygiene; prevents flag debt. |
### 2.5.3 V1 Candidates
Strong first production-grade but not MVP blocking.
| ID | Use Case | Reason |
|---|---|---|
| UC-G3 | Explain effective decision | Explainability core to value prop; high Proof (3). |
| UC-H1 | Backend-agnostic provider switch | Reversibility; reduces lock-in. |
### 2.5.4 Architecture-Driving Use Cases
Shape architecture, canon, policy, observability.
| ID | Use Case | Architecture Driver |
|---|---|---|
| UC-A1 | Adopt... | Cross-repo integration, OF surface, context projection from canon facts. |
| UC-E1 | Compute off... | Compute metadata, resolver composition, cost signals. |
| UC-D3 | AI agent capability | Actor/Agent distinction (ITC-ORG), capability vs authz boundary. |
| UC-G1 | Register... | Lifecycle, ownership (ITC-ORG), tagging categories, Task spawning. |
| UC-E4 | Kill switch | High-precedence controls (ITC-GOV), propagation, audit. |
### 2.5.5 Research-Only / Later
Useful for understanding but deferred (e.g. full experimentation analytics, tenant self-service deep).
---
## 3. Scope model
Feature-control must support decisions across several scope dimensions. These dimensions may be hierarchical, associative, or both.