tegwick
e1a6314131
import-review takes any partner manifest and returns, per concept, whether the name resolves in the ownership index and to which artifact, and per entry whether the pinned SHA-256 matches the blob at the declared source commit. Both run in one pass so neither can be recorded without the other, which is the failure this workplan exists to prevent. It exits non-zero on a finding, reads JSON or YAML, needs no partner checkout, and carries its own limit: resolution proves a name exists and names one owner, nothing more. Accepted manifests are registered under infospace/interfaces/manifests/ as provenance-preserving copies owned by the partner, with the partner revision and retrieval date recorded. Editing a copy to make a check pass is forbidden in the file itself. Validation re-resolves them and reports drift as federation_import_drift, a warning naming the partner rather than an error, because a stale partner pin is not this repository's file to fix. The review kit gains an extension-boundary-review template requiring hash count, resolution count and conflict count as three separate lines, and an operating rule saying one is never evidence of another. Both boundary files carry the standing-check result. Verified live: security-canon resolves 11 of 11, interface-canon 23 of 25 with the two known Interface and Endpoint pins. make check passes with 58 tests, clean validation and those two warnings. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 3588@bnt-lap001 Assistant-Session: 24b80f66-e5a7-4e61-99fe-2d422e6d17da
37 lines
1.8 KiB
YAML
37 lines
1.8 KiB
YAML
id: review-kit/alignment
|
|
title: Canon Consumer Alignment Review Kit
|
|
status: candidate
|
|
created_by_workplan: ITC-WP-0011
|
|
purpose: Provide a repeatable, agent-friendly process for mapping consumer repositories to InfoTechCanon and producing repo-local alignment workplans.
|
|
review_modes:
|
|
- quick-scan
|
|
- full-alignment-review
|
|
- focused-domain-review
|
|
entrypoints:
|
|
cli:
|
|
- info-tech-canon review-kit
|
|
- info-tech-canon alignment-template
|
|
api:
|
|
- GET /review-kit
|
|
- GET /alignment-template
|
|
components:
|
|
workflow: review-kit/alignment/workflow
|
|
scorecard: review-kit/alignment/scorecard
|
|
model_selection_guide: review-kit/alignment/model-selection-guide
|
|
schema: review-kit/alignment/schema
|
|
consumer_workplan_template: review-kit/alignment/workplan-template
|
|
extension_boundary_template: agent/templates/extension-boundary-review.template.md
|
|
required_outputs:
|
|
- repository_context
|
|
- selected_canon_surfaces
|
|
- mapping_findings
|
|
- scorecard
|
|
- recommended_workplans
|
|
- canon_feedback
|
|
operating_rules:
|
|
- Consumer repository changes and adoption workplans belong in the consumer repository.
|
|
- Canon pressure must be captured explicitly as proposed canon feedback, not as silent model drift.
|
|
- Evidence quality and confidence must be recorded separately from reviewer judgment.
|
|
- INTENT, SCOPE, and PURPOSES should be checked before proposing alignment work.
|
|
- Namespace, role, scope, tenant, evidence, and purpose terms must not be conflated across native systems and canon concepts.
|
|
- An import manifest must be checked twice, by pinned blob hash and by name resolution against the ownership index. A hash proves the reviewed file is the pinned file; only resolution proves the concept named in the manifest exists in it. Record both counts, never one as evidence of the other.
|