coulomb/security-canon
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Close the section 32 generalisation as accepted upstream

Browse source 
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
Download patch file Download diff file Expand all files Collapse all files

11
infospace/interfaces/concept-placement.md
View file

@ -135,6 +135,11 @@ No concept is contested and no semantic disposition changes.
word, two live InfoTechCanon senses: a right held by an actor (ITC-ORG 10.17) word, two live InfoTechCanon senses: a right held by an actor (ITC-ORG 10.17)
and an external body compelling disclosure (CARING 10.7). Disambiguation is and an external body compelling disclosure (CARING 10.7). Disambiguation is
InfoTechCanon-internal and is not made here. InfoTechCanon-internal and is not made here.
- **R-2 — CARING section 32 generalisation.** Referenced by SecurityCanon, - **R-2 — resolved 2026-09-20 in InfoTechCanon (INFO-DEC-2026-001).** The
explicitly not accepted by the InfoTechCanon-side boundary review. It remains section 32 role set now applies wherever a subject's access is exercised
an InfoTechCanon proposal requiring its own review. through another party, not to non-human subjects only. Option B from the
implications note was accepted narrowly: section 32.1 stays agent-stated, no
role is renamed, and CARING moves to canon version 0.4.0-RC2-itc2. Additive
and non-breaking; no SecurityCanon declaration changes. The blank cell in the
mapping table stands — InfoTechCanon's access-control model still has no
on-behalf-of relation.

8
infospace/mappings/mode-of-authority-to-infotechcanon.md
View file

@ -112,9 +112,11 @@ either.
## 6. Open ## 6. Open
- Whether CARING generalises its §32 role set beyond non-human subjects. Additive - ~~Whether CARING generalises its §32 role set beyond non-human subjects.~~
and non-breaking if adopted, but it is InfoTechCanon's to accept — raise as a **Closed 2026-09-20.** InfoTechCanon accepted option B as INFO-DEC-2026-001:
demand signal there, not as a change here. Analysis in the 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. [implications note](../../docs/260920-actor-subject-implications.md) §4.
- Whether `AuthMode` becomes a machine-readable authorization attribute - Whether `AuthMode` becomes a machine-readable authorization attribute
consumable by CARING descriptors (v0.1 draft Q7). consumable by CARING descriptors (v0.1 draft Q7).