Canon 0.5.0: uses_provisions so P stays purchased platform
A provision can name which other provision satisfies a catalog dependency. Relation vocabulary is depends_on / may_use only. Quoted sits below the invoiced/measured peer pair for propagation.
This commit is contained in:
parent
40accbbf3d
commit
0b28ec570e
12 changed files with 156 additions and 35 deletions
|
|
@ -12,9 +12,9 @@ canon:
|
|||
name: InfoTechCanon Capability Model — Capability Catalog
|
||||
short_name: ITC-CAP
|
||||
artifact_id: model/capability
|
||||
version: 0.3.0
|
||||
version: 0.4.0
|
||||
status: proposed
|
||||
canon_version: 0.4.0
|
||||
canon_version: 0.5.0
|
||||
purpose: Canonical, implementation-independent catalog of the abilities an information system may require
|
||||
or provide.
|
||||
normative_document: models/capability/InfoTechCanonCapabilityModel.md
|
||||
|
|
@ -300,6 +300,7 @@ domains:
|
|||
may_use:
|
||||
- runtime.scheduling
|
||||
- operations.observability
|
||||
- security.secrets
|
||||
- id: data.archive
|
||||
name: Archive & Retention
|
||||
purpose: Preserve information for long-term retention under defined lifecycle, integrity, and retrieval
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue