STATE-WP-0098: plan State Hub inputs that hub-core receipt tasks wait on
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 356991@bnt-lap001
Assistant-Session: 5d99ea69-ed55-4a1e-8d97-f4f312db247f
This commit is contained in:
tegwick 2026-10-13 23:08:15 +02:00
parent 55af31590e
commit 0af43ae413
2 changed files with 82 additions and 3 deletions

View file

@ -2,7 +2,7 @@
# Custodian Brief — state-hub
**Domain:** infotech
**Last synced:** 2026-10-13 20:36 UTC
**Last synced:** 2026-10-13 20:58 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
@ -21,11 +21,11 @@ Progress: 6/9 done | workplan_id: `ed077b62-7048-5752-bf65-f90471f45854`
**Open tasks:**
- ! Execute move/replace slices `3a454438`
*(wait: Founder authorized production writer changes on 2026-10-05 (913b924b). No route switches until hub-core, repo-manager, activity-core and ops-hub route-switch and rollback receipts exist.)*
*(wait: Founder authorized production writer changes on 2026-10-05 (913b924b). No route switches until hub-core, repo-manager, activity-core and ops-hub route-switch and rollback receipts exist. Hub-core receipts are HUB-WP-0011-T03 and HUB-WP-0006-T06, which wait on State Hub for parity cases, caller/alias mapping and a bounded switch window (a mutual wait). repo-manager, activity-core and ops-hub have no receipt workplan yet (requested 2026-10-13).)*
- ! Retire legacy surfaces `f6cf8c01`
*(wait: 2026-10-06 weekly review: zero retirement candidates. Three high-volume /workstreams reads need 60 quiet days (earliest 2026-10-20); two interfaces still have live callers.)*
- ! Stabilization window and archive prep `9230c99b`
*(wait: Stopping the primary is a founder decision; needs T04 handoffs and T05 retirement first; legacy meter still has live callers.)*
*(wait: Needs T04 handoffs and T05 retirement first; legacy meter still has live callers. The primary stop follows the standing change rule (decision 2fd5849c, resolved 2026-10-11); no separate founder gate.)*
## Inbox Hygiene

View file

@ -0,0 +1,79 @@
---
id: STATE-WP-0098
type: workplan
title: "Supply State Hub inputs that hub-core receipt tasks wait on"
domain: infotech
repo: state-hub
status: active
owner: claude-code
topic_slug: infotech
created: "2026-10-13"
updated: "2026-10-13"
flavor: implementation
related: [STATE-WP-0079, HUB-WP-0006, HUB-WP-0011]
---
Breaks the mutual wait recorded on STATE-WP-0079-T04. T04 waits on hub-core
receipts HUB-WP-0011-T03 and HUB-WP-0006-T06. Both of those wait on artifacts
that State Hub owns. This plan delivers those artifacts. It does not switch any
route: switches stay under STATE-WP-0079-T04 and the founder's 2026-10-05
writer authorization (913b924b), with old-route fallback and metered
acceptance retained by State Hub.
## A5 topic-spine comparison packet
```task
id: STATE-WP-0098-T01
status: todo
priority: high
```
Input for HUB-WP-0006-T06. Enumerate the A5 topic/classification read
endpoints (8 per `docs/retirement-cutover-slice-plan.md`) and their actual
callers from the legacy meter. Capture legacy response shapes. State the alias
expectations: legacy topic ids and slugs versus registrar `repository_id`.
Define concrete comparison cases against the deployed hub-core projection.
Name the fallback route. Deliver as `docs/a5-topic-spine-comparison-packet.md`
plus a JSON case list, and notify hub-core.
## A4 work/repo UI caller inventory and owner asks
```task
id: STATE-WP-0098-T02
status: todo
priority: medium
```
Enumerate the 22 A4 UI read endpoints and the clients that call them. Name the
UI/client owner for each. Ask each owner for a candidate read smoke and a
reversible switch plan. Record the owners and requests in the A5 packet's
companion section. A4 redirects stay behind the retained UI as rollback.
## Inbox change-feed contract
```task
id: STATE-WP-0098-T03
status: todo
priority: high
```
Input for HUB-WP-0011-T01. Specify a versioned State Hub inbox change feed:
a consistent snapshot plus a monotonic revision/cursor; read/archive state
changes; deletion versus retention semantics (tombstones; State Hub stays the
only message writer); replay/compaction recovery; and source timestamps for
freshness. Deliver as `docs/inbox-change-feed-contract.md`. Any
retention/ownership choice that the existing T08/T09 record does not settle
goes to the founder before hub-core implements against it.
## Named single reader and parity window
```task
id: STATE-WP-0098-T04
status: todo
priority: medium
```
Input for HUB-WP-0011-T03. Name the one inbox reader to switch first. Give
its parity sample/window and the rollback endpoint (current State Hub
`/messages/`). Get the reader owner's agreement. This depends on T03 being
accepted by hub-core.