# 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