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

feat(bootstrap): finish FEATURE-WP-0001 State Hub integration workstream

Browse Source 
- T01 (Review Generated Integration Files): Reviewed INTENT.md, SCOPE.md, AGENTS.md, .custodian-brief.md. Refined SCOPE.md (removed generic generated placeholder, added repo-specific In/Out Scope, Current State noting completion of WP-0001 and WP-0002, canon alignment). Refined README.md with links to canon-mapping and workplans. Confirmed INTENT and AGENTS already specific.
- T02 (Verify Local Developer Workflow): Confirmed pure-docs repo (no build/test files). Added 'Local Developer Workflow' section to AGENTS.md documenting verification commands (cat/ls for review, hub curls, make fix-consistency from state-hub, progress POSTs) and extension guidance.
- Updated FEATURE-WP-0001 workplan: T01/T02 marked done with detailed notes; frontmatter status set to finished.
- Includes completion of FEATURE-WP-0002 (canon alignment for PRD/UCC, docs/canon-mapping.md + interface card stub, terminology updates with EvaluationScope and ITC mappings).
- Ran make fix-consistency REPO=feature-control after changes (synced hub, set workstreams to finished).

All per AGENTS.md session protocol, workplan instructions, and custodian brief.

Bootstrap workstream now 3/3 complete; no active workstreams remaining.
This commit is contained in:
Bernd Worsch
2026-06-14 21:24:46 +02:00
parent e1eca7f045
commit 571e2f7127
10 changed files with 2929 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
SCOPE.md Normal file
View File

@@ -0,0 +1,36 @@
# SCOPE
## One-liner
Open feature based multi-vendor, multi-tenant, multi-scope feature availability and provisioning engine.
## Core Idea
feature-control exists to provide the capability described in INTENT.md (canonical feature availability control plane using OpenFeature for repos, with multi-scope governance, compute control, agent capabilities, and InfoTechCanon alignment).
## In Scope
- Maintain INTENT.md, specs/ProductRequirementsDocument.md (PRD), specs/UseCaseCatalog.md (UCC), docs/canon-mapping.md, docs/canon-interface-card.md (stub), workplans/ (FEATURE-WP-0001 bootstrap + FEATURE-WP-0002 canon alignment).
- Keep docs, operational metadata, and hub integration current.
- Execute workplans per AGENTS.md session protocol (orientation, task status updates in files, progress events, fix-consistency).
- Refine terminology and models for canon compatibility (EvaluationScope, ITC-ORG/ACCESS/LAND/GOV consumption, ProducerCapability/Feature extensions).
## Out of Scope
- Own unrelated adjacent systems (e.g. core entitlement, full authorization, billing).
- Make irreversible operational decisions without human approval.
- Implement backend providers, SDKs, or control plane code (documentation and planning phase only).
## Current State
- Bootstrap State Hub integration (FEATURE-WP-0001) complete (T01-T03 done).
- Canon terminology alignment and PRD/UCC improvements (FEATURE-WP-0002) complete (T01-T10 done; 10/10 progress).
- Status: active; docs and workplans stabilized. Future implementation work (e.g. pilots) may use new workplans.
## Getting Oriented
- Start with: INTENT.md
- Agent instructions: AGENTS.md
- Workplans: workplans/
- Canon mapping: docs/canon-mapping.md
- Verify: cat .custodian-brief.md ; ls workplans/ ; from ~/state-hub: make fix-consistency REPO=feature-control