generated from coulomb/repo-seed
99 lines
2.6 KiB
Markdown
99 lines
2.6 KiB
Markdown
---
|
|
id: ITC-WP-0009
|
|
type: workplan
|
|
title: "Repo Scoping Comparison And Extension"
|
|
domain: canon
|
|
repo: info-tech-canon
|
|
status: finished
|
|
priority: high
|
|
created: "2026-05-23"
|
|
updated: "2026-05-23"
|
|
depends_on_workplans:
|
|
- ITC-WP-0005
|
|
- ITC-WP-0006
|
|
state_hub_workstream_id: "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
|
|
|
|
```task
|
|
id: ITC-WP-0009-T01
|
|
status: done
|
|
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
|
|
|
|
```task
|
|
id: ITC-WP-0009-T02
|
|
status: done
|
|
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
|
|
|
|
```task
|
|
id: ITC-WP-0009-T03
|
|
status: done
|
|
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
|
|
|
|
```task
|
|
id: ITC-WP-0009-T04
|
|
status: done
|
|
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.
|
|
|
|
## Implementation Notes
|
|
|
|
- Added a repo-scoping comparison frame, canon benefit analysis, extension
|
|
candidate set, comparison report, and consumer workplan brief under
|
|
`infospace/evaluations/repo-scoping/`.
|
|
- Registered all repo-scoping comparison assets in the artifact index and
|
|
retrieval generation flow.
|
|
- Added structural validation for the comparison domains, candidate mappings,
|
|
extension candidates, and markdown deliverables.
|
|
- Regenerated agent briefs, indexes, tree views, and validation output.
|