tegwick
30cf417a18
The role set — Principal, effective actor, Delegator, tool or agent, policy ceiling, execution context, audit identity — now applies wherever a subject's access is exercised through another party, rather than to non-human subjects only. The gap this closes is not about agents. A support operator impersonating a customer involves no non-human subject anywhere in the path, yet without the decomposition that operator's audit identity and policy ceiling collapse into the customer's, which is the outcome CARING's exposure analysis exists to prevent. CARING already names customer impersonation as an exposure mode and ImpersonationBlocked as a control; the vocabulary for analysing it was gated to subjects the case does not involve. Section 33 was already subject-agnostic, so the canon applied the execution paths to any subject while restricting the roles along those paths to non-human ones — an artifact of the section heading, not a considered position. Accepted narrowly. Section 32.1 stays agent-stated, with a note on reading the capability ceiling for a human effective actor. No role is removed, renamed or added, and section 33 is untouched. Option C, a twelfth dimension, is rejected as duplicating sections 32 and 33 while touching a dimension set the Kubernetes RBAC benchmark depends on. Canon version moves to 0.4.0-RC2-itc2; source version stays 0.4.0-RC2, since this revises the InfoTechCanon-aligned standard and claims nothing about upstream CARING. The change is additive: an implementation that applied the set only to non-human subjects stays conformant for those subjects. Review record in history/; the SecurityCanon boundary file and placement record are updated to show R-2 resolved. 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 |
||
|---|---|---|
| .. | ||
| manifests | ||
| federation.yaml | ||
| interface-canon-boundary.md | ||
| README.md | ||
| security-canon-boundary.md | ||
Canon federation interface
The interface card publishes this canon's federation boundary under accepted ADR-006.
- commerce-canon interface
- the-custodian interface
- InterfaceCanon boundary review — scoped acceptance of the draft 0.1.1 extension boundary, with pinned sources and review evidence.
- SecurityCanon interface
- SecurityCanon boundary review — scoped acceptance of the draft 0.2.0 architecture-layer authority vocabulary, with pinned sources.
Each export names its source document and current maturity. Imports identify actual dependencies; reciprocal navigation does not imply reciprocal semantic imports. Custodian supplies ecosystem governance, InfoTechCanon information- processing semantics, and CommerceCanon commercial semantics. Family remains seeded, not authored. The card scope is this federation, not every repo artifact.
Reproduce G7 from the adjacent project checkout:
python3 tools/validate_interfaces.py --workspace ..