---
id: CUST-WP-0065
type: workplan
title: "Reclassify repos and guidance docs to the new sector domain scheme"
domain: infotech
repo: the-custodian
status: active
owner: codex
created: "2026-08-23"
updated: "2026-08-23"
quality_dor: DoR-Ok
quality_dor_at: "2026-08-23"
quality_dor_by: codex
quality_dor_note: "The live registry baseline, canonical vocabulary, source-of-truth boundary, owner dependencies, non-mechanical classification risk, and acceptance checks are explicit."
state_hub_workstream_id: "e2702474-b276-4e15-8337-41bfa344c89c"
---

# Reclassify repos and guidance docs to the new sector domain scheme

## Goal

Complete the transition from legacy project/estate labels to the canonical
sector-domain vocabulary without mechanically rewriting project identities or
silently assigning ambiguous repos. Populate the authoritative repository
projection, update Custodian guidance, and route repo-owned classification
changes to their owners.

**Promoted from intake** `019f81e6-2a31-7bee-b50a-8e9ca67267b7` — origin: "intake:019f81e6-2a31-7bee-b50a-8e9ca67267b7"

## Establish the live baseline and migration semantics

```task
id: CUST-WP-0065-T01
status: done
priority: high
```

Count active repositories with complete and incomplete classification
projection, distinguish missing source files from missing ingestion, and define
how legacy project names relate to sector domains. Do not treat a project name
as a one-to-one market classification.

**Done (2026-08-23):** `docs/repo-classification-sector-migration-baseline-2026-08-23.md`
records the live 117-repository baseline: 38 active records have no projected
category, comprising 14 missing source files and 24 present-but-unprojected
files. It also fixes the migration rule: legacy names remain project/estate
identity; sector values describe intended users and require repo-owner review
when the answer is ambiguous.

## Publish canonical migration guidance

```task
id: CUST-WP-0065-T02
status: done
priority: medium
```

Review the baseline semantics into the active Repo Classification Standard and
agent-facing guidance. Replace only obsolete domain-field instructions; keep
historical project names and canon references intact. Add a validation example
that rejects legacy names in `repo_classification.domain` while allowing them
as project/topic identity.

**Done (2026-08-23):** the active Repo Classification Standard now explicitly
separates legacy project/estate identities from sector-domain metadata and
links the governed migration baseline. The contribution convention and all
four contribution templates now show current sector values. The classification
validator self-test proves `custodian` is rejected as a classification domain;
project names remain valid outside that field.

## Repair source records and authoritative projection

```task
id: CUST-WP-0065-T03
status: progress
priority: high
```

Route the 14 missing `.repo-classification.yaml` files to repository owners and
have Repo Manager/State Hub diagnose the 24 files that exist locally but remain
null in the registry. Classification judgments stay with repo owners; the
Custodian coordinates vocabulary and acceptance. Require schema validation and
normal registrar/reconcile paths rather than direct database edits.

**Started (2026-08-23):** Repo Manager received the 24-repo projection defect
and `config-atlas` sentinel proof in message `a5e685c9`; `binky-control`
received the first missing-source owner handoff in message `15d8f2df`. The
remaining missing-source repos stay in the baseline for governed owner routing.

## Verify fleet convergence and close

```task
id: CUST-WP-0065-T04
status: todo
priority: medium
```

Re-run the active-repository baseline. Close when every active repo either has
a valid projected classification or a governed exclusion, current agent
guidance uses sector domains, and no project identity was destroyed by the
migration. Record any genuine owner decision as a live residual before
finishing.

## Indexing note

The workplan is indexed as `e2702474-b276-4e15-8337-41bfa344c89c`, but the
primary registrar rejected task UUID assignment under correlation
`57bb4daf-7386-4115-8ffb-37218892d482`. Its repository-wide identity audit
correctly fails closed on grandfathered workplan ids and bare `T01`–`T09`
collisions in older Custodian files. No task ids were invented or database rows
patched. Repo Manager received the compatibility evidence in message
`76f1c416`; file task states remain authoritative until a governed registrar
path can bind them.

## Acceptance

- [x] Live missing-classification baseline is reproducible and split by cause
- [x] Legacy project identity is distinguished from sector-domain metadata
- [x] Canonical and agent-facing migration guidance is current
- [ ] Missing source classifications are owner-reviewed and validated
- [ ] Present source classifications project into State Hub
- [ ] Active fleet has zero unexplained null category projections