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

id, type, title, domain, repo, status, priority, created, updated, depends_on_workplans, state_hub_workstream_id

id	type	title	domain	repo	status	priority	created	updated	depends_on_workplans	state_hub_workstream_id
ITC-WP-0009	workplan	Repo Scoping Comparison And Extension	canon	info-tech-canon	proposed	high	2026-05-23	2026-05-23	ITC-WP-0005 ITC-WP-0006	97efb3e4-3303-41bd-a220-d1fbd7c24f01

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

id: ITC-WP-0009-T01
status: todo
priority: high
state_hub_task_id: "7f5b0093-29b8-453f-ab73-c44db71cde52"

• 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

id: ITC-WP-0009-T02
status: todo
priority: high
state_hub_task_id: "d026d36b-e89d-4498-9c07-0f2e7f0c3c4c"

• Identify which canon concepts repo-scoping can reuse directly.
• Identify which mappings or profiles would make repo-scoping more useful.

T03 - Extension candidates

id: ITC-WP-0009-T03
status: todo
priority: high
state_hub_task_id: "98888f6a-774f-4e6b-93f4-335fb3001e9c"

• 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

id: ITC-WP-0009-T04
status: todo
priority: medium
state_hub_task_id: "5b8ac21c-e0e4-4e45-817c-a91111712c82"

• 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.