15 lines
1.2 KiB
Markdown
15 lines
1.2 KiB
Markdown
|
# InfoTechCanon Capability Model concept boundary review — 2026-09-20
|
||
|
|
|
||
|
|
Authority: INFO-WP-0027-T07, which declared the two concepts this model defined
|
||
|
|
without declaring. No concept is renamed, moved or removed.
|
||
|
|
|
||
|
|
| Concept | Owner | Resolution | Decided by |
|
||
|
|
| --- | --- | --- | --- |
|
||
|
|
| `Capacity behaviour` | model/capability | Whether a capability's supply is elastic or fixed as demand grows. The Organization Model's `Capacity` is how much work an actor or group can absorb. Different questions; no transfer. | this review |
|
||
|
|
| `Supply` | model/capability | Internal, drawn from own capacity, or external, purchased. No other artifact defines the name. | this review |
|
||
|
|
| `Capability` | model/capability | The canonical capability concept. The Organization Model's `OrganizationalCapability` is the organizational reading and imports; the Purpose and Demand extension's `ProducerCapability` and CARING's `CaringCapabilityProfile` are qualified specializations. | this review |
|
||
|
|
|
||
|
|
Concepts this artifact declares are listed in its frontmatter. An overlap
|
||
|
|
recorded here means another artifact defines the same name; where the owner is
|
||
|
|
another artifact, this one imports the definition rather than restating it.
|