Add 'tooling' category to 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>
This commit is contained in:
2026-06-22 03:08:20 +02:00
parent 40cc73f22e
commit 27b7e3f08a
3 changed files with 44 additions and 14 deletions

View File

@@ -192,15 +192,18 @@ Done when each custodian repo has a committed file that validates against T01 an
has been reviewed by a human.
**Progress (2026-06-22):** all 11 custodian-domain repos now carry a committed,
validated `.repo-classification.yaml` (first-pass `classified_by: agent`):
the-custodian (research·infotech), state-hub (product·infotech), hub-core
(product·infotech), inter-hub (research·infotech), activity-core
(project·infotech), issue-core (product·infotech), kaizen-agentic
(product·agents), llm-connect (product·agents), ops-bridge (product·infotech),
ops-warden (product·infotech), email-connect (product·infotech). Commits are
**local-only** in each repo (not yet pushed to Gitea). Task stays `in_progress`
pending the **human review** step (done-criterion); review the `research` vs
`project`/`product` calls and the agents-vs-infotech primary-domain choices.
validated `.repo-classification.yaml` (first-pass `classified_by: agent`).
Following the 2026-06-22 decision, a new **`tooling`** category (between `project`
and `product`) was added to the standard for reusable internal
tooling/infrastructure, and the nine tooling repos were reclassified to it:
the-custodian (research·infotech), inter-hub (research·infotech), state-hub
(tooling·infotech), hub-core (tooling·infotech), activity-core (tooling·infotech),
issue-core (tooling·infotech), kaizen-agentic (tooling·agents), llm-connect
(tooling·agents), ops-bridge (tooling·infotech), ops-warden (tooling·infotech),
email-connect (tooling·infotech). Commits are **local-only** in each repo (not
yet pushed to Gitea). Task stays `in_progress` pending the **human review** step;
remaining review item is the agents-vs-infotech primary-domain choice for
kaizen-agentic and llm-connect.
### T03 - Classify the full Gitea inventory