From 27b7e3f08a085571e0f8750a6851f6c0cba56f83 Mon Sep 17 00:00:00 2001 From: tegwick Date: Mon, 22 Jun 2026 03:08:20 +0200 Subject: [PATCH] Add 'tooling' category to Repo Classification Standard MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- .../repo-classification-standard_v1.0.md | 36 ++++++++++++++++--- .../repo-classification.allowed.yaml | 1 + ...po-classification-registration-redesign.md | 21 ++++++----- 3 files changed, 44 insertions(+), 14 deletions(-) diff --git a/canon/standards/repo-classification-standard_v1.0.md b/canon/standards/repo-classification-standard_v1.0.md index 2c5f68b..3574228 100755 --- a/canon/standards/repo-classification-standard_v1.0.md +++ b/canon/standards/repo-classification-standard_v1.0.md @@ -164,6 +164,7 @@ category: - experimental - research - project + - tooling - product - business ``` @@ -233,7 +234,31 @@ Examples: category: project ``` -### 5.4 `product` +### 5.4 `tooling` + +Use for reusable internal tooling and infrastructure that supports building, +coordinating, or operating other work — libraries, CLIs, services, and ops +components used across the ecosystem rather than offered to external customers. + +Main question: + +> Does this reliably support how we build and operate other work? + +Typical signs: + +- reused across multiple repos or by agents/operators, +- stable enough to depend on, but not a customer-facing product, +- no external pricing, customer onboarding, or go-to-market concerns, +- sits between `project` (a bounded build) and `product` (an offerable to + customers); may graduate to `product` if later externalised. + +Examples: + +```yaml +category: tooling +``` + +### 5.5 `product` Use for reusable, offerable products or product components with intended users or customers. @@ -255,7 +280,7 @@ Examples: category: product ``` -### 5.5 `business` +### 5.6 `business` Use for repos organizing commercial, operational, legal, strategic, financial, or organizational activity. @@ -623,8 +648,9 @@ Ask: 1. Is this mainly a spike or prototype? → `experimental` 2. Is this mainly knowledge, terminology, research, or standards? → `research` 3. Is this a bounded implementation effort? → `project` -4. Is this reusable and offerable to users/customers? → `product` -5. Is this about commercial, legal, financial, strategic, or organizational viability? → `business` +4. Is this reusable internal tooling/infrastructure supporting other work? → `tooling` +5. Is this reusable and offerable to users/customers? → `product` +6. Is this about commercial, legal, financial, strategic, or organizational viability? → `business` ### Step 2: Identify the primary domain @@ -1051,7 +1077,7 @@ Use the following prompt for agent-assisted classification. Classify this repository according to the Repo Classification Standard. Return a YAML block with: -- category: one of experimental, research, project, product, business +- category: one of experimental, research, project, tooling, product, business - domain: one of infotech, financials, communication, consumer, health, industrials, energy, utilities, materials, realestate, crypto, agents, space, government - secondary_domains: zero or more allowed domains, excluding the primary domain - capability_tags: lowercase kebab-case tags describing what the repo does or enables diff --git a/canon/standards/repo-classification.allowed.yaml b/canon/standards/repo-classification.allowed.yaml index 5341b9e..7c6e180 100644 --- a/canon/standards/repo-classification.allowed.yaml +++ b/canon/standards/repo-classification.allowed.yaml @@ -17,6 +17,7 @@ categories: - experimental - research - project + - tooling - product - business diff --git a/workplans/CUST-WP-0050-repo-classification-registration-redesign.md b/workplans/CUST-WP-0050-repo-classification-registration-redesign.md index 87237b5..9bab562 100644 --- a/workplans/CUST-WP-0050-repo-classification-registration-redesign.md +++ b/workplans/CUST-WP-0050-repo-classification-registration-redesign.md @@ -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