d0216adb44
All 44 cache-only repository records resolved: 43 onboarded and classified, agent-harness dropped by owner decision. Central holds 121 repositories. Corrects an earlier claim in this workplan that the cache would hold nothing unique once the repository records were resolved. That generalised a repository-scoped result: the cache still holds ~400 workplans and ~1,950 tasks that exist nowhere else, which is ADR-010's original divergence. The cache database still must not be discarded. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
5.1 KiB
Disposition — repositories not onboarded to central
CUST-WP-0067-T05, 2026-08-24. Of the 44 cache-only repository records, 33 were
onboarded to central via rmgr repo-onboard. Central went from 78 to 111
repositories. These 11 did not, each for a reason that needs a decision rather
than a retry. One (agent-harness) has since been decided: dropped.
| Repository | Reason | Needed |
|---|---|---|
agent-harness |
no working copy on this machine | dropped 2026-08-25 — see below |
binky-control |
no .repo-classification.yaml |
author with the repo owner |
clay-borg |
no .repo-classification.yaml |
author with the repo owner |
direkt-vermittlung-de |
no .repo-classification.yaml |
author with the repo owner |
polycode-sim |
no .repo-classification.yaml |
author with the repo owner |
railiance-telemetry |
no .repo-classification.yaml |
author with the repo owner |
ralph-workplan |
no .repo-classification.yaml |
author with the repo owner |
rein-openweights |
no .repo-classification.yaml |
author with the repo owner |
soul-frame |
commits not pushed | owner decides whether to publish |
testdrive-jsui |
no .repo-classification.yaml |
author with the repo owner |
timeline-svg |
no .repo-classification.yaml |
author with the repo owner |
Why these were not forced
Classification is not mechanical (CUST-WP-0065-T01): the sector domain
describes intended users, and guessing it produces a confident wrong answer
that is harder to correct than a missing one. Nine repositories need a
classification file authored with their owner.
soul-frame has three unpushed commits carrying research content. Onboarding
correctly refused — a hub record whose backing file is only local cannot be
re-derived — but publishing someone's unpublished work is an owner decision,
not a side effect of onboarding. Once pushed:
uv run --project ~/repo-manager rmgr repo-onboard \
--path ~/soul-frame --api-base http://127.0.0.1:8000
agent-harness — dropped (2026-08-25)
Decided by Bernd Worsch: the repository is superseded by glas-harness and the
rein concept, so there is nothing to restore. It is therefore not onboarded
to central, and its cache-only record is left to disappear when the local cache
database is discarded. Preserving it as a hub-only record would be the ADR-001
violation ADR-010 calls out — a hub record with no backing file that nothing
can re-derive.
Successors verified present and classified on central before dropping:
| Successor | Domain | Category |
|---|---|---|
glas-harness |
infotech | tooling |
rein-aharness |
agents | tooling |
rein-openweights is part of the same concept but is still awaiting a
classification file, so it remains in the outstanding set below rather than
counting as a landed successor.
This is the one record of the 44 that is deliberately not recovered. Nothing else in the export should be dropped without an equivalent decision.
Classification is deferred for all 33
Every onboarded record carries its domain but no classification fields. The
hub returned 500 on each classification write because api/classification.py
resolved its allowed-values file only from developer workstation checkouts, so
in the container none exist. Fixed by REPO_CLASSIFICATION_ALLOWED_PATH
(state-hub 05dda8d), which still needs the canon file delivered into the pod
and the variable set — tracked as CUST-WP-0067-T09.
The records are correct and re-derivable in the meantime: the classification files are committed and pushed, so re-running onboarding projects them once the hub can validate.
Closed 2026-08-25 — all 44 resolved
| Outcome | Count |
|---|---|
| Onboarded to central and classified | 43 |
Dropped by owner decision (agent-harness) |
1 |
soul-frame's three research commits were pushed by owner decision and it
onboarded cleanly. The nine repositories without a classification file had their
sector domain and category decided with the owner one at a time; all nine
validated against canon, were committed, pushed, and onboarded. Central holds
121 repositories.
Two decisions worth keeping visible:
rein-openweightsmovedinfotech→agents, matching its siblingrein-aharnessso the rein concept groups coherently.railiance-telemetrymovedfinancials→infotechby owner decision, classifying it by what it is rather than the estate it serves. This deliberately splits it from the other Railiance repositories on central.
The cache database still must not be discarded
Repository records are fully recovered, but that was only this task's scope. Measured 2026-08-25:
| Record type | Local cache | Central |
|---|---|---|
managed_repos |
122 | 121 |
workplans |
1075 | 669 |
tasks |
6073 | 4123 |
Roughly 400 workplans and 1,950 tasks still exist only in the cache. That is
ADR-010's original divergence, which this workplan never claimed to close —
it addressed the repository-record subset. ADR-010 assessed the bulk of those
as file-backed and therefore re-derivable, but re-derivation has not been run
or verified.
Do not discard the cache database until that is resolved.