diff --git a/WORK-RECORDS.md b/WORK-RECORDS.md new file mode 100644 index 0000000..ed6efcb --- /dev/null +++ b/WORK-RECORDS.md @@ -0,0 +1,42 @@ +# Work Records — feature-control + +> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record +> stage 3). Do not edit by hand — edit the source file/block listed for +> each record and re-run fix-consistency to refresh this index. Archived +> workplans are omitted; closed decisions/intakes/engagements stay listed +> so recently-resolved work is still visible. [auto] + +| Kind | ID | Status | Lane | Source | +| --- | --- | --- | --- | --- | +| workplan | FEATURE-WP-ADHOC-2026-09-06 | finished | — | workplans/ADHOC-2026-09-06.md | +| workplan | FEATURE-WP-0001 | finished | — | workplans/FEATURE-WP-0001-statehub-bootstrap.md | +| workplan | FEATURE-WP-0002 | finished | — | workplans/FEATURE-WP-0002-canon-prd-ucc-alignment.md | +| workplan | FEATURE-WP-0003 | done | — | workplans/FEATURE-WP-0003-first-implementation-mvp.md | +| workplan | FEATURE-WP-0004 | done | — | workplans/FEATURE-WP-0004-feature-control-adoption-toolkit.md | +| task | FEATURE-WP-ADHOC-2026-09-06-T01 | done | — | workplans/ADHOC-2026-09-06.md | +| task | FEATURE-WP-0001-T01 | done | — | workplans/FEATURE-WP-0001-statehub-bootstrap.md | +| task | FEATURE-WP-0001-T02 | done | — | workplans/FEATURE-WP-0001-statehub-bootstrap.md | +| task | FEATURE-WP-0001-T03 | done | — | workplans/FEATURE-WP-0001-statehub-bootstrap.md | +| task | FEATURE-WP-0002-T01 | done | — | workplans/FEATURE-WP-0002-canon-prd-ucc-alignment.md | +| task | FEATURE-WP-0002-T02 | done | — | workplans/FEATURE-WP-0002-canon-prd-ucc-alignment.md | +| task | FEATURE-WP-0002-T03 | done | — | workplans/FEATURE-WP-0002-canon-prd-ucc-alignment.md | +| task | FEATURE-WP-0002-T04 | done | — | workplans/FEATURE-WP-0002-canon-prd-ucc-alignment.md | +| task | FEATURE-WP-0002-T05 | done | — | workplans/FEATURE-WP-0002-canon-prd-ucc-alignment.md | +| task | FEATURE-WP-0002-T06 | done | — | workplans/FEATURE-WP-0002-canon-prd-ucc-alignment.md | +| task | FEATURE-WP-0002-T07 | done | — | workplans/FEATURE-WP-0002-canon-prd-ucc-alignment.md | +| task | FEATURE-WP-0002-T08 | done | — | workplans/FEATURE-WP-0002-canon-prd-ucc-alignment.md | +| task | FEATURE-WP-0002-T09 | done | — | workplans/FEATURE-WP-0002-canon-prd-ucc-alignment.md | +| task | FEATURE-WP-0002-T10 | done | — | workplans/FEATURE-WP-0002-canon-prd-ucc-alignment.md | +| task | FEATURE-WP-0003-T01 | done | — | workplans/FEATURE-WP-0003-first-implementation-mvp.md | +| task | FEATURE-WP-0003-T02 | done | — | workplans/FEATURE-WP-0003-first-implementation-mvp.md | +| task | FEATURE-WP-0003-T03 | done | — | workplans/FEATURE-WP-0003-first-implementation-mvp.md | +| task | FEATURE-WP-0003-T04 | done | — | workplans/FEATURE-WP-0003-first-implementation-mvp.md | +| task | FEATURE-WP-0003-T05 | done | — | workplans/FEATURE-WP-0003-first-implementation-mvp.md | +| task | FEATURE-WP-0003-T06 | done | — | workplans/FEATURE-WP-0003-first-implementation-mvp.md | +| task | FEATURE-WP-0004-T01 | done | — | workplans/FEATURE-WP-0004-feature-control-adoption-toolkit.md | +| task | FEATURE-WP-0004-T02 | done | — | workplans/FEATURE-WP-0004-feature-control-adoption-toolkit.md | +| task | FEATURE-WP-0004-T03 | done | — | workplans/FEATURE-WP-0004-feature-control-adoption-toolkit.md | +| task | FEATURE-WP-0004-T04 | done | — | workplans/FEATURE-WP-0004-feature-control-adoption-toolkit.md | +| task | FEATURE-WP-0004-T05 | done | — | workplans/FEATURE-WP-0004-feature-control-adoption-toolkit.md | +| task | FEATURE-WP-0004-T06 | done | — | workplans/FEATURE-WP-0004-feature-control-adoption-toolkit.md | +| task | FEATURE-WP-0004-T07 | done | — | workplans/FEATURE-WP-0004-feature-control-adoption-toolkit.md | diff --git a/docs/canon-mapping.md b/docs/canon-mapping.md index ba9809c..8c2cad6 100644 --- a/docs/canon-mapping.md +++ b/docs/canon-mapping.md @@ -5,7 +5,7 @@ **Repo:** feature-control **Related:** INTENT.md, specs/ProductRequirementsDocument.md (PRD), specs/UseCaseCatalog.md (UCC), docs/feature-management-model.md (TBD per T02) -This document maps current `feature-control` concepts (from INTENT, PRD, and UCC) to identity-canon and **InfoTechCanon** concepts. It is intentionally explicit about owned facts, consumed facts, references, proposed extensions, and gaps. It follows the pattern established in `user-engine/docs/canon-mapping.md` and aligns with canon review-kit expectations (interface cards, consumer briefs, alignment reviews). +This document maps current `feature-control` concepts (from INTENT, PRD, and UCC) to **InfoTechCanon** concepts. It is intentionally explicit about owned facts, consumed facts, references, proposed extensions, and gaps. It follows the pattern established in `user-engine/docs/canon-mapping.md` and aligns with canon review-kit expectations (interface cards, consumer briefs, alignment reviews). ## Mapping Stance @@ -77,7 +77,7 @@ Local/test providers and generated constants must be usable without live canon o ## Current Gaps (feature-control side) - `Natural Person` not modeled (consistent with user-engine). Agent vs human must remain distinct in context and rules. -- Strong/weak identity linking and synonymity assertions are external (identity-canon). +- Strong/weak identity linking and synonymity assertions are external (InfoTechCanon `itc-ident`). - Full `Organization` / `Vendor` / `Legal Entity` / `Customer` modeling is referenced via tenant + external identifiers (small-saas profile uses tenant separation). - Presentation/Visibility semantics have no deep canon owner yet (future Landscape/Data or profile concern). feature-control owns the feature-derived portion only. - `Scope` (bare) term clash in prior feature docs vs canon producer-scope / ScopePressure. Mitigated by introducing EvaluationScope / TargetingScope. @@ -136,4 +136,12 @@ These preserve orthogonality: canon owns general concepts and machinery; feature - T09: Add references from INTENT/PRD/UCC; create short feature-management-model.md (T02) that shows OF surface → resolver/composition (feature-control) → canon facts. - After edits: update this mapping (Status, Updated), run `make fix-consistency REPO=feature-control` from state-hub, and request canon owner feedback. -This mapping + the revised PRD/UCC will ensure feature-control matches well with canon terminology and provides a deeper, interoperable understanding of feature management. \ No newline at end of file +This mapping + the revised PRD/UCC will ensure feature-control matches well with canon terminology and provides a deeper, interoperable understanding of feature management. +## Federation reference update — 2026-09-06 + +The [identity model](../../info-tech-canon/infospace/models/identity/InfoTechCanonIdentityModel.md) +owns Scope and Synonymity Assertion; organization/access definitions retain their +respective upstream owners. The [evidence model](../../info-tech-canon/infospace/models/evidence/InfoTechCanonEvidenceModel.md) +owns Evidence and Evidence Source. CommerceCanon owns commercial concepts. +This updates owner references under CFED-WP-0001-T09; it does not certify a new +consumer adoption or change feature-control behavior. diff --git a/workplans/ADHOC-2026-09-06.md b/workplans/ADHOC-2026-09-06.md new file mode 100644 index 0000000..725408e --- /dev/null +++ b/workplans/ADHOC-2026-09-06.md @@ -0,0 +1,38 @@ +--- +id: FEATURE-WP-ADHOC-2026-09-06 +type: workplan +title: "Update live canon federation references" +domain: infotech +repo: feature-control +status: finished +owner: codex +created: "2026-09-06" +updated: "2026-09-06" +state_hub_workstream_id: "83a3ba87-affc-5ba2-97f0-5cfa980822ce" +--- + +## Follow current canon source owners + +```task +id: FEATURE-WP-ADHOC-2026-09-06-T01 +status: done +priority: medium +state_hub_task_id: "dfb7e0af-ea2e-57e2-92c6-aaaf19e6188b" +``` + +Bounded source-reference correction authorized by CFED-WP-0001-T09. Preserve +historical workplans, evidence, UUIDs, runtime contracts and capability IDs. +Identity/evidence meanings now reference InfoTechCanon; the same renamed +repository is CommerceCanon for commercial semantics. + +Files reviewed: + +- `docs/canon-mapping.md` + +Acceptance: no live obsolete source reference in these files, valid YAML/Python +where applicable, unchanged runtime behavior, and consolidated fleet evidence in +prj-canon-federation. This does not assert independent consumer adoption. + +Result: current source references corrected; syntax and targeted verification +passed. Consolidated proof is owned by CFED-WP-0001-T09. No new implementation +residual is introduced by this documentation/coordinate update.