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

CUST-WP-0061-T06: migrate 10 live legacy suggestions to file-backed intake
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details

Browse source 
One-time close-out of the legacy suggestions table, per the
founder-reviewed decision to retire it (fresh intake entity, not a
rename-bridge). At retirement, 10 records were still open (stage:
suggestion, never promoted/declined) -- real signal from other domains'
agents: 7 ops-warden WARDEN-WP-0012 gated routing scenarios, 2
state-hub STATE-WP-0069/0073 items, 1 binky-control repo-classification
finding. Rather than discard the signal, migrated each into a proper
file-backed intake record (CUST-IN-0001..0010) landing in this repo --
the fleet's natural holding ground for cross-domain findings with no
specific owning repo yet, since none of these ever had a file origin
(hub-first creation is exactly the anti-pattern this whole effort
exists to close).

Each carries origin: "legacy-suggestion:<uuid>" back to the retired
record. All 10 registered live against the real hub via C-32 (state_hub_intake_id
written back). WORK-RECORDS.md regenerated to include them.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-07-21 01:51:38 +02:00
parent 56b1d991fa
commit 6403f6fbc8
2 changed files with 153 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

10
WORK-RECORDS.md
View file

@ -392,3 +392,13 @@
| task | CUST-WP-0061-T04 | done | — | workplans/CUST-WP-0061-work-record-stage3-intake-promotion-index.md |
| task | CUST-WP-0061-T05 | todo | — | workplans/CUST-WP-0061-work-record-stage3-intake-promotion-index.md |
| task | CUST-WP-0061-T06 | todo | — | workplans/CUST-WP-0061-work-record-stage3-intake-promotion-index.md |
| intake | CUST-IN-0001 | open | green | intake-legacy-suggestions-migration.md |
| intake | CUST-IN-0002 | open | green | intake-legacy-suggestions-migration.md |
| intake | CUST-IN-0003 | open | green | intake-legacy-suggestions-migration.md |
| intake | CUST-IN-0004 | open | green | intake-legacy-suggestions-migration.md |
| intake | CUST-IN-0005 | open | green | intake-legacy-suggestions-migration.md |
| intake | CUST-IN-0006 | open | green | intake-legacy-suggestions-migration.md |
| intake | CUST-IN-0007 | open | green | intake-legacy-suggestions-migration.md |
| intake | CUST-IN-0008 | open | blue | intake-legacy-suggestions-migration.md |
| intake | CUST-IN-0009 | open | blue | intake-legacy-suggestions-migration.md |
| intake | CUST-IN-0010 | open | green | intake-legacy-suggestions-migration.md |

143
intake-legacy-suggestions-migration.md Normal file
View file

@ -0,0 +1,143 @@
# Legacy suggestion migration — CUST-WP-0061-T06
> Status: one-time close-out, 2026-07-21. The state-hub `suggestions` table
> predates the work-record canon and is being retired to read-only legacy
> (fresh `intake` entity, not a rename-bridge — founder-reviewed decision,
> `WorkOrchestrationArchitectureDraft.md` §8 item 6). At the time of
> retirement, 10 suggestion records were still open (`stage: suggestion`,
> never promoted or declined) — real backlog signal from other domains'
> agents (ops-warden `WARDEN-WP-0012` gated routing scenarios, state-hub's
> own `STATE-WP-0069`/`STATE-WP-0073`, one binky-control repo-classification
> item). Rather than discard that signal, each is migrated here as a proper
> file-backed `intake` work record — landing in `the-custodian` since none
> of these ever had a repo-file origin (they were created hub-first,
> exactly the ADR-001 gap this whole effort exists to close) and
> `the-custodian` is the fleet's natural holding ground for cross-domain
> findings without a specific owning repo yet.
>
> Each intake below carries `origin: "legacy-suggestion:<uuid>"` for
> traceability back to the retired record. The originals were declined in
> the hub with a note pointing here (not deleted — historical record
> preserved). **If you own one of these domains, pick up the finding**:
> vet it, route it, and promote it into a proper workplan/task in the
> right repo — that's the whole point of the mechanism this repo now has.
```yaml
id: CUST-IN-0001
title: "Issue-core ingestion API key OpenBao path"
lane: green
status: open
origin: "legacy-suggestion:256e94f0-833f-4502-a927-70873c3b5a1b"
origin_ref: "issue-core-ingestion-api-key"
notes: "Gated routing scenario from WARDEN-WP-0012. Owner path not yet
shipped; accrued relevance=1 in the legacy suggestions table before
migration (2026-07-21)."
state_hub_intake_id: "019f81e5-ab50-716d-8d69-680d46001856"
```
```yaml
id: CUST-IN-0002
title: "Activity-core issue sink consumer key custody"
lane: green
status: open
origin: "legacy-suggestion:a1a08013-1c5c-4471-8dc6-7bf0b2acb591"
origin_ref: "activity-core-issue-sink"
notes: "Gated routing scenario from WARDEN-WP-0012. Owner path not yet
shipped; accrued relevance=1 in the legacy suggestions table before
migration (2026-07-21)."
state_hub_intake_id: "019f81e5-b404-7e7f-87a9-c92196351216"
```
```yaml
id: CUST-IN-0003
title: "OpenRouter llm-connect OpenBao -> K8s Secret path"
lane: green
status: open
origin: "legacy-suggestion:b431df3a-3a0d-4ce9-abf9-d931dff58523"
origin_ref: "openrouter-llm-connect"
notes: "Gated routing scenario from WARDEN-WP-0012. Owner path not yet
shipped; migrated 2026-07-21."
state_hub_intake_id: "019f81e5-be9a-733b-b8ea-711b220d4177"
```
```yaml
id: CUST-IN-0004
title: "Object storage STS vending path (NK-WP-0007)"
lane: green
status: open
origin: "legacy-suggestion:1fc77948-951a-43be-a3c9-8caebfc9243d"
origin_ref: "object-storage-sts"
notes: "Gated routing scenario from WARDEN-WP-0012, references net-kingdom
NK-WP-0007. Owner path not yet shipped; migrated 2026-07-21."
state_hub_intake_id: "019f81e5-d422-7e78-9b5a-8b4635fec15d"
```
```yaml
id: CUST-IN-0005
title: "Human OIDC login via key-cape / Keycloak"
lane: green
status: open
origin: "legacy-suggestion:b3b59fbe-6932-4934-b960-e9f3f244eeb1"
origin_ref: "human-oidc-login"
notes: "Gated routing scenario from WARDEN-WP-0012. Owner path not yet
shipped; migrated 2026-07-21."
state_hub_intake_id: "019f81e5-f82b-70c8-8948-8fc07e1879e0"
```
```yaml
id: CUST-IN-0006
title: "flex-auth policy decision before sensitive action"
lane: green
status: open
origin: "legacy-suggestion:1e152a52-88a7-455c-b35b-36ef9a24beeb"
origin_ref: "flex-auth-resource-check"
notes: "Gated routing scenario from WARDEN-WP-0012. Owner path not yet
shipped; migrated 2026-07-21."
state_hub_intake_id: "019f81e6-06f1-7718-bac1-c93ee29265b9"
```
```yaml
id: CUST-IN-0007
title: "auth_principals sync for host principal deploy"
lane: green
status: open
origin: "legacy-suggestion:0ddbfc0c-469a-4d73-a20f-06071b7114a0"
origin_ref: "host-principal-deploy"
notes: "Gated routing scenario from WARDEN-WP-0012. Owner path not yet
shipped; migrated 2026-07-21."
state_hub_intake_id: "019f81e6-1149-78aa-97d2-635c75622e9e"
```
```yaml
id: CUST-IN-0008
title: "Roll out weekly legacy-meter review on Railiance activity-core"
lane: blue
status: open
origin: "legacy-suggestion:05da5540-e7cd-41fb-a511-3c1572e4604f"
origin_ref: "weekly-legacy-meter-review-railiance-rollout"
notes: "From STATE-WP-0069 (financials domain). Migrated 2026-07-21."
state_hub_intake_id: "019f81e6-198b-7df7-964e-6f8c06443454"
```
```yaml
id: CUST-IN-0009
title: "Rebuild activity-core:railiance01-prod for legacy-meter 8h capture"
lane: blue
status: open
origin: "legacy-suggestion:8b3301d6-0222-41e4-89c9-99e8c6dd5248"
origin_ref: "legacy-meter-8h-capture-railiance-rollout"
notes: "From STATE-WP-0073 (financials domain). Migrated 2026-07-21."
state_hub_intake_id: "019f81e6-2348-72a8-8ec9-edb851acb9aa"
```
```yaml
id: CUST-IN-0010
title: "Reclassify repos and guidance docs to the new sector domain scheme"
lane: green
status: open
origin: "legacy-suggestion:9c1de00d-7f2c-43f9-aaef-62356038c0b7"
origin_ref: "binky-control fix-consistency C-24 / session 2026-07-16"
notes: "Originated from a binky-control fix-consistency C-24 classification
gap. Migrated 2026-07-21."
state_hub_intake_id: "019f81e6-2a31-7bee-b50a-8e9ca67267b7"
```