Publish project-repository-flavor_v0.1 with naming, GOAL.md (not durable
INTENT.md), authority boundary, lifecycle, residuals, and archive rules.
Close ADR-005 deferred naming and CUST-WP-0050 D1a; cross-link from the
repo classification standard.
Insert a 'tooling' category between project and product (reusable internal
tooling/infrastructure: libraries, CLIs, services, ops components used across
the ecosystem rather than offered to external customers). Update §5 definition,
§11 decision procedure, §16 agent prompt, the machine-readable allowed-values,
and the CUST-WP-0050 T02 progress note. Nine custodian tooling repos
reclassified to it; the-custodian and inter-hub remain research.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Activate the workplan and complete T01: add the machine-readable controlled
vocabulary canon/standards/repo-classification.allowed.yaml (categories,
domains, business_stake, business_mechanics, capability families, guidance),
reference it from the standard §12, and add tools/validate_repo_classification.py
(stdlib + PyYAML, --self-test PASS).
Begin T02: author the-custodian/.repo-classification.yaml (research · infotech ·
agents), which validates clean. classified_by: agent, pending human review.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Move specs/RepoClassificationStandard.md to
canon/standards/repo-classification-standard_v1.0.md with provenance
frontmatter (id: canon-repo-classification, status: active, v1.0). The
standard originated in Helix Forge; the-custodian is interim steward. Leave
a pointer stub in specs/ redirecting to canon and the rollout workplan.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
