generated from coulomb/repo-seed
97 lines
4.8 KiB
YAML
97 lines
4.8 KiB
YAML
id: comparison/repo-scoping/canon-benefit-analysis
|
|
title: Repo Scoping Canon Benefit Analysis
|
|
status: candidate
|
|
consumer: repo-scoping
|
|
comparison_report: comparison/repo-scoping/report
|
|
direct_reuse:
|
|
- canon_surface: model/purpose-demand-extension
|
|
benefit: Distinguishes producer intent, current scope, consumer purposes, demand signals, purpose fit, scope pressure, and evolution requests.
|
|
repo_scoping_surfaces:
|
|
- INTENT.md
|
|
- SCOPE.md
|
|
- expectation gaps
|
|
- self-scoping comparison outcomes
|
|
- canon_surface: model/governance
|
|
benefit: Provides Decision, Review, Evidence, Risk, Issue, Exception, Approval, and review-cycle vocabulary for candidate acceptance.
|
|
repo_scoping_surfaces:
|
|
- ReviewDecision
|
|
- approved characteristics
|
|
- rejected candidates
|
|
- quality-gate overrides
|
|
- regression outcomes
|
|
- canon_surface: model/information-space
|
|
benefit: Provides artifact, source reference, provenance, retrieval, citation, index, and interface-card concepts.
|
|
repo_scoping_surfaces:
|
|
- SourceReference
|
|
- ContentChunk
|
|
- ObservedFact
|
|
- SCOPE.md sections
|
|
- scope-generation API outputs
|
|
- canon_surface: model/task
|
|
benefit: Provides work semantics for review tasks, remediation, refactors, rebuilds, recalculation, and follow-up work.
|
|
repo_scoping_surfaces:
|
|
- expectation gaps
|
|
- rebuild dry-runs
|
|
- dependency impact analysis
|
|
- self-assessment actions
|
|
- canon_surface: standard/tagging
|
|
benefit: Provides lightweight classification vocabulary for primary class, attributes, source roles, and utility relationships.
|
|
repo_scoping_surfaces:
|
|
- primary_class
|
|
- attributes
|
|
- source_role
|
|
- utility_relationship
|
|
candidate_mappings:
|
|
- repo_scoping_concept: Scope
|
|
canon_mapping: RepositoryScopeProfile
|
|
fit: extension_needed
|
|
rationale: Canon has generic Scope, Profile, and Purpose concepts, but repo-scoping needs a source-linked current-state repository utility profile.
|
|
- repo_scoping_concept: Ability
|
|
canon_mapping: ProducerCapability
|
|
fit: partial_fit
|
|
rationale: Ability is a high-level useful outcome; ProducerCapability is close but should not hide repository-specific abstraction level.
|
|
- repo_scoping_concept: Capability
|
|
canon_mapping: CapabilityClaim
|
|
fit: extension_needed
|
|
rationale: Repo-scoping capabilities are reviewable utility claims with confidence, evidence, and source references.
|
|
- repo_scoping_concept: Feature
|
|
canon_mapping: FeatureClaim
|
|
fit: extension_needed
|
|
rationale: Feature is concrete behavior supporting a capability and needs typed evidence links.
|
|
- repo_scoping_concept: Evidence
|
|
canon_mapping: EvidenceLink
|
|
fit: extension_needed
|
|
rationale: Governance Evidence exists, but repo-scoping needs a link object that can target facts, chunks, files, or lower-level characteristics.
|
|
- repo_scoping_concept: ObservedFact
|
|
canon_mapping: SourceObservation
|
|
fit: extension_needed
|
|
rationale: Observed facts are deterministic scanner outputs and should not be collapsed into evidence or truth claims.
|
|
- repo_scoping_concept: ReviewDecision
|
|
canon_mapping: Decision
|
|
fit: direct
|
|
rationale: ReviewDecision is a governance decision over candidate truth, with reviewer, criteria, evidence, and rationale.
|
|
- repo_scoping_concept: ExpectationGap
|
|
canon_mapping: Issue / ScopePressure / EvolutionRequest
|
|
fit: partial_fit
|
|
rationale: Some gaps are quality issues, some are out-of-scope expectations, and some create purpose-driven evolution requests.
|
|
- repo_scoping_concept: DependencyImpactAnalysis
|
|
canon_mapping: ScopeFreshness / PropagationImpact
|
|
fit: extension_needed
|
|
rationale: Canon lacks a precise way to express staleness propagation from observed facts to approved utility claims.
|
|
profile_candidates:
|
|
- id: profile/repository-scope
|
|
title: Repository Scope Profile
|
|
purpose: Define minimal artifacts and relationships needed to represent repository intent, current scope, consumer purposes, approved claims, evidence links, decisions, and freshness.
|
|
- id: profile/scope-md-interface
|
|
title: SCOPE.md Interface Profile
|
|
purpose: Define the SCOPE.md section contract, generation ownership, curator-owned sections, and capability block expectations.
|
|
- id: profile/self-scoping-assessment
|
|
title: Self-Scoping Assessment Profile
|
|
purpose: Define golden profile, challenger assessment, known-bad seed, comparison outcome, and regression evidence structures.
|
|
repo_scoping_value:
|
|
- Better separation of INTENT, SCOPE, and PURPOSES.
|
|
- Cleaner review semantics for generated candidates and approved truth.
|
|
- Source-linked evidence model that can become reusable across canon consumers.
|
|
- Explicit extension path for self-scoping, scope freshness, and scope propagation.
|
|
- Interface Card fields that repo-scoping can produce for other repositories.
|