coulomb/repo-manager
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
repo-manager/docs/repository-classification-contract_v1.0.md
tegwick 35e86d7b85 feat: advance repository records and provenance 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
2026-08-21 22:07:48 +02:00

1.4 KiB
Raw Blame History

id type title version status created updated workplan_task canon_source
RMGR-CONTRACT-CLASSIFICATION-0001 contract Repository classification receiving contract 1.0 active 2026-08-21 2026-08-21 RMGR-WP-0008-T06 the-custodian/canon/standards/repo-classification-standard_v1.0.md

Repository classification receiving contract v1.0

Repo Manager reads .repo-classification.yaml as repository authority and validates it against version 1.0 of the Custodian's Repo Classification Standard. It publishes the validated value in repository snapshots; downstream topic or domain services consume that projection and do not replace the file.

The required scalar fields are category and domain. Optional list fields are secondary_domains, capability_tags, business_stake, and business_mechanics. Controlled values and the tag syntax are in the companion machine-readable contract.

Invalid classifications fail observation with field-specific errors. Repo Manager does not coerce unknown values, infer the primary domain from technical tags, or write classification during observation. A canon vocabulary change requires a new contract version and implementation update; the canon remains the source of meaning.

Boundary with hub-core: Repo Manager owns file validation and the repository projection. Hub-core may aggregate those projections into topics and fleet navigation, but does not become classification authority.