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

Canon 0.5.0: uses_provisions so P stays purchased platform
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
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:
tegwick 2026-08-15 19:23:44 +02:00
parent 40accbbf3d
commit 0b28ec570e
12 changed files with 156 additions and 35 deletions
Download patch file Download diff file Expand all files Collapse all files

6
demand/ProvisionRelationships.md
View file

@ -1,12 +1,12 @@
# Demand: Provision-to-provision relationships — which provision satisfies a dependency
**Status:** inbound demand (un-reviewed)
**Status:** accepted (canon 0.5.0 / ITC-CAP 0.4.0)
**Date:** 2026-08-15
**Source:** resource-control (consumer), domain `financials`
**Proposed owner:** `ITC-CAP` (§4.7 CapabilityProvision, §7 Relationships)
**Owner:** `ITC-CAP` (§4.7 CapabilityProvision, §7 Relationships, CAP-R11)
**Requested by:** info-tech-canon, in reply to the ITC-CAP restatement, 2026-08-15
**Consumer evidence:** `resource-control/data/capability/platform-audit-storage.json`
**Proposed workplan:** `ITC-WP-0014` follow-on
**Workplan:** `ADHOC-2026-08-15` T03
---