coulomb/info-tech-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Canon 0.6.0 freeze: ITC-CAP draft, AVT catalog, joinable review
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Finish ITC-WP-0013 (AttributeValueType under ITC-DATA) and ITC-WP-0014
T02/T03/T05/T06/T07. Capability contract schemas, live-catalog review
CLI, landscape/kernel-map pointers. Sit on this version.
This commit is contained in:
tegwick 2026-08-15 19:42:30 +02:00
parent 7805560a60
commit d453e17952
44 changed files with 1485 additions and 137 deletions
Download patch file Download diff file Expand all files Collapse all files

10
infospace/models/landscape/InfoTechCanonLandscapeModel.md
View file

@ -610,7 +610,15 @@ These concepts SHOULD eventually be reviewed against:
- product management,
- and governance models.
The Landscape Model should keep only landscape-relevant references once a dedicated strategy/capability standard exists.
A dedicated capability model now exists: **ITC-CAP**
(`model/capability`). Abstract ability — what a system must be able to do
— is owned there. `BusinessCapability` / `ProductCapability` in this
domain SHOULD resolve to references to ITC-CAP ids. This domain keeps
landscape-relevant strategy concepts (Goal, Driver, Initiative,
RoadmapItem, ValueStream). Capability as ability is no longer owned here.
ITC-CAP names *intended* requirement targets. This model still owns
services, technologies, runtime resources, and *observed* SLOs.
---