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 |
||
|---|---|---|
| .. | ||
| interfaces | ||
| mappings | ||
| vocabulary/mode-of-authority | ||