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

Canon 0.3.0: capability provision economics (ITC-CAP 0.2.0)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Accept resource-control demand: move resource classes onto provisions,
let requirements carry targets and constraints, add human-effort class H
with native-unit consumption. Model stays proposed.
This commit is contained in:
tegwick 2026-08-15 18:19:30 +02:00
parent 9c7c1e4bdf
commit b69b048dcb
14 changed files with 410 additions and 131 deletions
Download patch file Download diff file Expand all files Collapse all files

7
infospace/assimilation/it-capability-canon/open-questions.md
View file

@ -41,6 +41,13 @@ if consumers start requiring structural semantics (invoices, entitlements,
prompts, evaluations). **Review trigger:** the first consumer demand that needs
structure rather than ability.
**Partial fire, 2026-08-15.** `demand/CapabilityProvisionEconomics.md` needed
structure for *consumption of* intelligence (native unit `token`, quality
dimension `intelligence_intensity`, class `I` as substitute for `H`). That
structure landed in ITC-CAP 0.2.0 as resource-class and provision semantics, not
as a new intelligence domain model. Invoices, entitlements, prompts, and
evaluations still have no owning model. The trigger remains open for those.
## OQ-6 — How are capability requirements validated against provisions?
The source sketches a validator (§18) comparing product requirements to provider