railiance-fabric/workplans/RAIL-FAB-WP-0029-coordination-graph-perspective.md

54 lines
2.1 KiB
Markdown
Raw Normal View History

---
id: RAIL-FAB-WP-0029
type: workplan
title: "Inspectable workplan and wait graph in the Fabric explorer"
domain: financials
repo: railiance-fabric
status: blocked
flavor: planning
owner: grok
topic_slug: railiance
created: "2026-09-14"
updated: "2026-09-27"
related: [RAIL-FAB-WP-0028, CUST-WP-0071]
state_hub_workstream_id: "1daac341-94dd-5f44-9907-91c611e7e3c1"
---
Repository files remain the workplan source; State Hub indexes them. Fabric already has a
graph-explorer shell. This plan is a *perspective*: open workplans, open
tasks, and wait/depends_on edges, so the 100+ loose ends are inspectable.
First slice (this file's companion commit):
`export --format coordination` and
`/ui/graph-explorer?mode=coordination`.
## Host the coordination overlay next to Fabric topology
```task
id: RAIL-FAB-WP-0029-T01
status: wait
priority: medium
state_hub_task_id: "f80a8b15-ea3d-5701-9707-0a6151f50b5c"
```
Keep the projection a read of State Hub. Add mode switching without a full
page reload, chokepoint sizing from in-degree, and a hosted registry path
under RAIL-FAB-WP-0028 when that authority exists. Do not let Fabric become
the place workplans are edited.
## Loose-end review — 2026-09-27
Completed the repo-local portion of T01: topology/coordination mode changes
and residual visibility now fetch and replace the graph without page reload.
The requested topology mode survives the switch back; empty payloads remain
switchable, failed fetches retain the previous graph, and stale responses cannot
overwrite a newer request. Shared URLs retain residual visibility. Existing
in-degree sizing and indexed/citation edge precedence remain in place.
T01 stays `wait` and the workplan is `blocked` solely for hosted acceptance
under RAIL-FAB-WP-0028. The read-only coordination export already has a registry
route (`/exports/graph-explorer?mode=coordination`); it must be verified on the
admitted hosted authority once available. No separate task was created for this
remaining gate. Validation: JavaScript syntax check, executable transition
regression, and the repository Python suite (see session progress receipt).