Register infospace service workplans

workplans/ITC-WP-0009-repo-scoping-comparison-and-extension.md

@@ -0,0 +1,82 @@
+---
+id: ITC-WP-0009
+type: workplan
+title: "Repo Scoping Comparison And Extension"
+repo: info-tech-canon
+status: planned
+priority: high
+created: "2026-05-23"
+updated: "2026-05-23"
+depends_on_workplans:
+  - ITC-WP-0005
+  - ITC-WP-0006
+---
+
+# ITC-WP-0009 - Repo Scoping Comparison And Extension
+
+## Goal
+
+Compare InfoTechCanon with `repo-scoping` to identify how repo-scoping can
+benefit from the canon and where the canon should be extended to maximize
+repo-scoping utility.
+
+## Intent
+
+Repo-scoping is likely to stress the Governance Model and the emerging
+INTENT/SCOPE/PURPOSES pattern. The comparison should be explicit and should
+produce extension candidates rather than silently blending models.
+
+## Tasks
+
+### T01 - Comparison frame
+
+```task
+id: ITC-WP-0009-T01
+status: planned
+priority: high
+```
+
+- Define the questions used to compare repo-scoping with the canon.
+- Cover repository intent, current scope, future scope, consumers, purposes,
+  decisions, evidence, risks, and evolution requests.
+
+### T02 - Canon benefit analysis
+
+```task
+id: ITC-WP-0009-T02
+status: planned
+priority: high
+```
+
+- Identify which canon concepts repo-scoping can reuse directly.
+- Identify which mappings or profiles would make repo-scoping more useful.
+
+### T03 - Extension candidates
+
+```task
+id: ITC-WP-0009-T03
+status: planned
+priority: high
+```
+
+- Identify concepts the canon lacks or under-specifies.
+- Pay special attention to PURPOSES and governance concepts.
+- Produce candidate changes for review before altering standards.
+
+### T04 - Consumer workplan brief
+
+```task
+id: ITC-WP-0009-T04
+status: planned
+priority: medium
+```
+
+- Produce a brief for a repo-scoping consumer workplan.
+- Keep the actual repo-scoping adoption workplan in that repo.
+
+## Acceptance
+
+- There is a clear comparison report.
+- Canon extension candidates are explicit.
+- Repo-scoping can plan adoption from its own repository.
+