coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Complete CUST-WP-0070: publication category established
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Python Tests / pytest (push) Successful in 24s
Details

Browse source 
Standard at v1.1, repo-manager teaches it as a durable flavor, hall-of-helix
classified. resolve_flavor returns publication for the hall where it previously
fell through to tooling. repo-manager suite: 161 passed.

Also carries generated updates to WORK-RECORDS.md and intakes.md from
fix-consistency.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SQ6oF1DtVDKcD1FCpvRVLx
This commit is contained in:
codex 2026-09-05 22:14:22 +02:00
parent c0308bb573
commit 119c3bee89
3 changed files with 17 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

16
workplans/CUST-WP-0070-publication-repo-category.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Add the publication category to the Repo Classification Standard"
domain: infotech
repo: the-custodian
status: active
status: finished
owner: claude-code
topic_slug: custodian
priority: medium
@ -13,9 +13,14 @@ updated: "2026-09-05"
quality_dor: DoR-Ok
quality_dor_at: "2026-09-05"
quality_dor_by: claude-code
quality_dod: DoD-Ok
quality_dod_at: "2026-09-05"
quality_dod_by: claude-code
quality_dod_note: "Standard at v1.1 with §5.7, the §5 vocabulary, §11 decision procedure, §16 agent prompt and §17 versioning rule updated; allowed.yaml carries publication plus history/participation in knowledge_and_evidence. repo-manager updated in classification.py, standards.py (DURABLE_FLAVORS) and cli.py — full suite 161 passed. hall-of-helix classified: canon linter ok, fix-consistency 0 warns, resolve_flavor now returns publication where it previously fell through to tooling."
quality_dor_note: "Classifying hall-of-helix exposed a real gap: a published corpus of authored records fits none of the six categories, and the fallback (project) is the only non-durable one, implying eventual retirement of a permanent record. The change is additive and no existing classification becomes invalid, so the enforcement points are known and bounded."
related:
- HOH-WP-0001
state_hub_workstream_id: "6d11d4fd-9882-55db-9010-b35754434b54"
---
# Add the publication category to the Repo Classification Standard
@ -55,8 +60,9 @@ distinguish adding a permitted value (minor) from renaming or removing one
```task
id: CUST-WP-0070-T01
status: todo
status: done
priority: high
state_hub_task_id: "75f56501-1416-5ab4-9d91-405ae532ac6b"
```
In `canon/standards/repo-classification-standard_v1.0.md`:
@ -83,8 +89,9 @@ In `canon/standards/repo-classification.allowed.yaml`:
```task
id: CUST-WP-0070-T02
status: todo
status: done
priority: high
state_hub_task_id: "6c943dec-f676-57af-a004-8c40b0ddebc1"
```
Three hardcoded lists in `~/repo-manager`, plus tests:
@ -101,8 +108,9 @@ turns out to be more than a vocabulary addition.
```task
id: CUST-WP-0070-T03
status: todo
status: done
priority: medium
state_hub_task_id: "0661c1d4-20e5-5d02-9435-eae171b07e13"
```
Write `hall-of-helix/.repo-classification.yaml`: