Correct the owner of Scope to the identity model (R-1)

The placement record named ITC-ACCESS the owner of Scope and imports.json pinned
it there. The corpus says otherwise: ITC-IDENT section 2.10 defines Scope as the
general boundary, and ITC-ACCESS section 11.8 ResourceScope already declares
itself a refinement of it rather than a competing definition. The second use R-1
was actually reaching for is CARING section 21, resolved upstream in
InfoTechCanon by ADHOC-2026-09-20-T01.

Scope now imports from InfoTechCanonIdentityModel. No hash changes: both files
were already pinned at the same source commit.

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

infospace/interfaces/concept-placement.md

@@ -25,7 +25,7 @@ Pinned import source: info-tech-canon at
 | Subject | InfoTechCanon | ITC-ACCESS | ITC → SC (import) | Bound as "the access-control view of an actor". SC references, never redefines. |
 | Principal | InfoTechCanon | ITC-ACCESS | ITC → SC (import) | |
 | PrincipalType | InfoTechCanon | Identity Model | ITC → SC (import) | The identity model is a shared root, not security terminology. |
-| Scope | InfoTechCanon | ITC-ACCESS | ITC → SC (import) | ITC-ACCESS is the single definition. See residual R-1. |
+| Scope | InfoTechCanon | Identity Model (ITC-IDENT 2.10) | ITC → SC (import) | The general boundary. ITC-ACCESS `ResourceScope` (11.8) refines it; CARING 21 ranges over it. Owner corrected by R-1. |
 | AccessOperations | InfoTechCanon | ITC-ACCESS | ITC → SC (import) | Orthogonal to Auth Mode: `read + USE` and `read + OBSERVE` share an operation. |
 | Purpose | InfoTechCanon | Purpose and Demand extension | ITC → SC (import) | Resolves to the extension, not to a SecurityCanon definition. |
 | Authority | InfoTechCanon | Organization Model (ITC-ORG 10.17) | ITC → SC (import) | The recognized right itself. AuthMode qualifies its exercise and never redefines it. Added by T03 (F-1). |
@@ -101,10 +101,13 @@ with SECURITY-WP-0001-T05, the migration handoff, having been cancelled.
 
 ## Residuals
 
-- **R-1 — CARING `Scope` and ITC-ACCESS `Scope`.** The review found two
-  definitions of one concept inside InfoTechCanon. This record names ITC-ACCESS
-  as the owner; reconciling CARING's wording to it is an InfoTechCanon-internal
-  change and is not made here.
+- **R-1 — resolved 2026-09-20 in InfoTechCanon (ADHOC-2026-09-20-T01).** The
+  owner named here was wrong in both halves. `Scope` is owned by ITC-IDENT 2.10;
+  ITC-ACCESS owns `ResourceScope` 11.8, which the model already declares as a
+  refinement rather than a competing definition. The real second use was CARING
+  21, which now states that its dimension ranges over ITC-IDENT Scope instances
+  and that its ladder is a value set, not a definition. The table row and
+  `imports.json` are corrected to import `Scope` from the identity model.
 - **R-3 — CARING `Authority` exposure mode against `itc-org:Authority`.** One
   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

infospace/vocabulary/mode-of-authority/imports.json

@@ -24,7 +24,6 @@
       "concepts": [
         "Subject",
         "Principal",
-        "Scope",
         "AccessOperations"
       ]
     },
@@ -33,8 +32,10 @@
       "path": "infospace/models/identity/InfoTechCanonIdentityModel.md",
       "sha256": "20bc844d9de07041c40009cc5e3d6eeb42aeb7adcbb86b0194d4b2517aa23f32",
       "concepts": [
-        "PrincipalType"
-      ]
+        "PrincipalType",
+        "Scope"
+      ],
+      "note": "Scope is the general boundary, ITC-IDENT 2.10. ITC-ACCESS ResourceScope 11.8 refines it."
     },
     {
       "artifact": "InfoTechCanonOrganizationModel",