coulomb/feature-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Reference current InfoTechCanon identity and evidence owners
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b
This commit is contained in:
tegwick 2026-09-06 01:38:25 +02:00
parent 482b7c86db
commit a555aaaf35
3 changed files with 91 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/canon-mapping.md
View file

@ -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.
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.