Close the section 32 generalisation as accepted upstream

InfoTechCanon reviewed the demand signal separately and accepted option B as
INFO-DEC-2026-001: the CARING section 32 role set now applies wherever a
subject's access is exercised through another party, rather than to non-human
subjects only. CARING moves to canon version 0.4.0-RC2-itc2.

The change is additive and no SecurityCanon declaration moves. The blank cell in
the mapping table stands: InfoTechCanon's access-control model still has no
on-behalf-of relation.

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
This commit is contained in:
tegwick 2026-09-20 23:54:12 +02:00
parent e159fe7a1b
commit 7e2de19dc6
2 changed files with 13 additions and 6 deletions

View file

@ -112,9 +112,11 @@ either.
## 6. Open
- Whether CARING generalises its §32 role set beyond non-human subjects. Additive
and non-breaking if adopted, but it is InfoTechCanon's to accept — raise as a
demand signal there, not as a change here. Analysis in the
- ~~Whether CARING generalises its §32 role set beyond non-human subjects.~~
**Closed 2026-09-20.** InfoTechCanon accepted option B as INFO-DEC-2026-001:
the role set now applies wherever access is exercised through another party,
CARING is at canon version 0.4.0-RC2-itc2, and the change is additive. The
mapping below is unaffected. Analysis in the
[implications note](../../docs/260920-actor-subject-implications.md) §4.
- Whether `AuthMode` becomes a machine-readable authorization attribute
consumable by CARING descriptors (v0.1 draft Q7).