Every Dispatch issue now sits inside one project-owned registry contract.
Project issues
Issue registry and archive-ready source records.
Project-scoped issue registry for Dispatch source records, archive rows, and publication structure.
Live publishingRefine migration activeCadence: Monthly issue cycleRead-only previewUpdated Apr 5, 2026, 2:10 PM UTCRuntime-backed: 1Founder preview: 3
Registry runtime
The issues route now behaves more like a real resource desk than a static archive summary.
This project lane keeps the issue registry live inside the workbench so scope, source posture, and structure stay inspectable without dropping back into disconnected content pages. The desk can now hold a dense table and a current issue detail rail at the same time.
Live issue registry0 rows in scopeAll access statesWaiting for sync
Hydrating live issue rows through the Refine runtime.
Search and access filters now narrow the desk without leaving the route.
Paid-preview rows stay distinct from archive-facing public issue rows.
Source posture remains visible before the review or delivery lanes widen.
Registry table
The issue desk should let you inspect structure before opening content.
| Issue | Access | Source | Published | Structure |
|---|---|---|---|---|
| No issue rows match the current desk filters. Adjust the search query or access state to widen the project registry view. | ||||
Selected issue
The right rail now keeps one issue fully in view while the table stays dense.
No issue is available in the current filtered view yet.
- Archive alignment: access state stays visible before you leave the registry for the content route.
- Review readiness: source kind and content hash stay attached to the same row the quality lane will inspect next.
- Delivery alignment: structure and included-item counts remain visible before subscriber delivery logic widens.