docs: complete canon alignment housekeeping

SCOPE.md

@@ -119,10 +119,12 @@ publication addressing are completed.
 
 ## InfoTechCanon Repository-Layout Alignment
 
-Declared conformance: **`minimal`** under ITC-REPO-LAYOUT 0.1.0-RC1.
+Declared conformance: **`core`** under ITC-REPO-LAYOUT 0.1.0-RC1.
 
 - `INTENT.md` contains stable aspiration and boundaries.
 - `SCOPE.md` contains current evidenced responsibility and explicit gaps.
+- `demand/` holds unreviewed architecture demand and requires a purpose/scope
+  disposition before work is committed.
 - `docs/` contains stakeholder-facing framework contracts and ADRs.
 - `workplans/` contains committed work and remains authoritative for State Hub.
 - `history/` contains dated, inactive architecture explorations.
@@ -132,11 +134,12 @@ Intentional deviations and omissions:
 - Finished workplan archival follows the Custodian ADR-001 convention at
   `workplans/archived/YYMMDD-...`, not the generic ITC `history/` placement, so
   State Hub discovery remains deterministic.
-- `demand/`, `research/`, `spec/`, `wiki/`, and `issues/` are not currently
-  claimed. They should be added only when their distinct semantics are needed,
-  not as empty structural decoration.
+- `research/`, `spec/`, `wiki/`, and `issues/` are not currently claimed. They
+  should be added only when their distinct semantics are needed, not as empty
+  structural decoration.
 - Consumer purposes and inbound requests are not folded into INTENT or SCOPE;
-  a future demand intake may provide that third plane explicitly.
+  `demand/` provides that third plane and resolved reviews move to dated
+  `history/` records.
 
 ---
 
@@ -191,6 +194,6 @@ keywords: [schema, validation, declaration, rail, rapp, reef]
 
 ## Gap to Intent
 
-The next obvious alignment work is to make accepted ADRs publication-ready,
-formalize how raw architecture demand is reviewed before it becomes a workplan,
-and cleanly archive completed work without breaking State Hub conventions.
+The remaining alignment work is to complete downstream ADR publication, cleanly
+archive completed work without breaking State Hub conventions, and retain a
+repeatable canon-consumer review packet as the architecture evolves.