info-tech-canon/infospace/models/capability/boundary-review.md
tegwick 5f652d200f
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s
Resolve the two senses of Authority and declare the unowned remainder (T05, T07)
R-3 is resolved by disambiguation without a rename. CARING section 10.7 now says
its Authority exposure mode names a demanding party rather than a right, links to
ITC-ORG section 10.17, and notes that such an Authority holds no organizational
authority over the system it compels. ITC-ORG carries the reciprocal sentence and
records that SecurityCanon's AuthMode qualifies the exercise of the right rather
than redefining it.

The seventeen concepts no artifact declared are now declared: eleven to the
Organization Model, four to CARING and two to the Capability Model. Capacity in
the Organization Model and Capacity behaviour in the Capability Model are two
concepts, not one, and neither moves. Two of CARING's four turned out not to be
new concepts at all but the prose spellings of CaringCapabilityProfile and
CaringDerivedCapability; both spellings are declared to the same owner so the
name a reader meets resolves. Effective Access and Declared Access were
genuinely undeclared.

Three boundary reviews are added for organization, caring and capability,
bringing the count to fourteen. The concept_defined_without_owner warning is at
zero, and the test that asserted it fires now proves it on a modified corpus
instead of on the live one.

make check passes with 54 tests, clean validation, no warnings, no stale assets.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 3588@bnt-lap001
Assistant-Session: 24b80f66-e5a7-4e61-99fe-2d422e6d17da
2026-09-20 23:32:57 +02:00

1.2 KiB

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.