Add repo-scoping comparison assets

infospace/evaluations/repo-scoping/consumer-workplan-brief.md

@@ -0,0 +1,61 @@
+---
+id: comparison/repo-scoping/consumer-workplan-brief
+title: Repo Scoping Consumer Workplan Brief
+status: candidate
+consumer: repo-scoping
+comparison_report: comparison/repo-scoping/report
+---
+
+# Repo Scoping Consumer Workplan Brief
+
+## Purpose
+
+Use this brief as the seed for a repo-scoping workplan. The adoption and
+implementation workplan belongs in the repo-scoping repository, not in
+InfoTechCanon.
+
+## Goal
+
+Compare repo-scoping with InfoTechCanon and adopt the canon where it improves
+repository intent, current scope, purposes, governance decisions, evidence, and
+scope evolution.
+
+## Canon Inputs
+
+- `infospace/evaluations/repo-scoping/comparison-report.md`
+- `infospace/evaluations/repo-scoping/comparison-frame.yaml`
+- `infospace/evaluations/repo-scoping/canon-benefit-analysis.yaml`
+- `infospace/evaluations/repo-scoping/extension-candidates.yaml`
+- `infospace/agent/templates/canon-interface-card.template.yaml`
+- `infospace/models/governance/InfoTechCanonPurposeDemandExtension.md`
+- `infospace/patterns/intent-scope-purposes.md`
+
+## Workplan Tasks For Repo-Scoping
+
+1. Complete a Canon Interface Card for repo-scoping.
+2. Map Scope, Ability, Capability, Feature, Evidence, ObservedFact,
+   ReviewDecision, ExpectationGap, and DependencyImpactAnalysis to canon
+   concepts or extension candidates.
+3. Separate design-time INTENT.md semantics from generated or curated SCOPE.md
+   semantics.
+4. Identify consumer purposes for humans, agents, State Hub, managed repos, and
+   capability catalog consumers.
+5. Evaluate extension candidates and mark which are proven, rejected, deferred,
+   or repo-scoping-specific.
+6. Create repo-scoping tasks for schema, API, UI, and documentation changes.
+
+## Expected Outputs
+
+- completed interface card,
+- mapping table from repo-scoping concepts to canon concepts,
+- list of accepted canon concepts,
+- list of extension candidates with evidence,
+- list of repo-scoping implementation tasks,
+- list of canon EvolutionRequests.
+
+## Non-Goals
+
+- Do not modify InfoTechCanon standards from the repo-scoping workplan without a
+  canon-side EvolutionRequest.
+- Do not collapse intent, current scope, and consumer purposes into one field.
+- Do not treat generated candidates as approved truth without governance review.