state-hub/workplans/STATE-WP-0098-hub-core-receipt-inputs.md

id	type	title	domain	repo	status	owner	topic_slug	created	updated	flavor	related	state_hub_workstream_id
STATE-WP-0098	workplan	Supply State Hub inputs that hub-core receipt tasks wait on	infotech	state-hub	active	claude-code	infotech	2026-10-13	2026-10-13	implementation	STATE-WP-0079 HUB-WP-0006 HUB-WP-0011	0c68970e-295b-57fc-ac70-e472ee3a7bc4

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

id: STATE-WP-0098-T01
status: done
priority: high
state_hub_task_id: "2197b8ae-40d1-52ff-b9d5-3244b9e5e8a9"

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

id: STATE-WP-0098-T02
status: progress
priority: medium
state_hub_task_id: "e6ef3381-9867-52f6-8c9c-2aa24f9a16b3"

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

id: STATE-WP-0098-T03
status: wait
needs_human: true
blocking_reason: "Founder decisions on tombstone retention, pre-retirement purge, broadcast delivery stamps and the additive migration (docs/inbox-change-feed-contract.md)"
priority: high
state_hub_task_id: "17c424c9-4089-56d2-9057-42e34f13827b"

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

id: STATE-WP-0098-T04
status: todo
priority: medium
state_hub_task_id: "077797c8-289b-55ec-9597-28f223891b02"

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.

2026-10-13 delivery:

• T01: docs/a5-topic-spine-comparison-packet.md and docs/evidence/a5-topic-spine-comparison-cases.json (10 cases).
  • A5 is 3 topic reads, 4 writes and the topics table, not 8 read endpoints.
  • All direct callers are State Hub's own tooling. 126 repos keep a topic_id that must stay stable.
  • Gaps that block hub-core: legacy_topic_aliases is hard-coded empty in hub-core repository_navigation.py; RM_SLICE_TOPICSPINE is not implemented anywhere; topic routes are not metered; the 154 legacy vs 123 published repository gap is unexplained.
• T02: 22 A4 dashboard views mapped to owners (same packet). Owner requests sent 2026-10-13.
• T03: docs/inbox-change-feed-contract.md drafted. A migration is required (no revision column on agent_messages/message_receipts, no tombstones). Four founder decisions are open.