#7 - Sprint 1 — Graph Foundation - foravo/milestone-proof-2-20260519050439

Imported from GitHub issue `conorgregson/worldbuilding-codex#21`. Source: https://github.com/conorgregson/worldbuilding-codex/issues/21 Original author: @conorgregson Original state: closed  --- ## Goal Add the core Relationship Graph foundation for Worldbuilding Codex v1.3 by creating a dedicated graph view that visually represents connected lore. Sprint 1 should establish the first working version of the graph by loading world entities and relationships, then rendering them as nodes and directional edges. --- ## Context Worldbuilding Codex v1.3 focuses on adding a visual Relationship Graph so users can better understand how lore entities connect across a world. This sprint is the foundation layer. It should prioritize stable routing, graph data loading, basic rendering, and safe behavior for sparse or empty graph data. Later sprints will add filtering, selection, highlighting, accessibility polish, responsive polish, and release documentation. --- ## Scope - Add a dedicated Relationship Graph route or page section. - Load the selected world’s entities and relationships. - Render entities as graph nodes. - Render relationships as directional graph edges. - Show relationship type or label information where practical. - Add navigation from the world detail page to the Relationship Graph view. - Add a clear graph page heading and helper text. - Handle worlds with entities but no relationships. - Handle worlds with no entities. - Confirm graph route refresh behavior. --- ## Acceptance Criteria - [x] Users can open a Relationship Graph page or section for a world. - [x] Relationship Graph route/page is protected behind authentication. - [x] Relationship Graph route/page loads the correct world data. - [x] Entities render as visible graph nodes. - [x] Relationships render as visible directional edges. - [x] Relationship type or label information appears where practical. - [x] Users can navigate to the graph view from the world detail page. - [x] A world with entities but no relationships does not crash. - [x] A world with no entities does not crash. - [x] Refreshing the graph route/page does not crash. - [x] Graph layout is usable on desktop. - [x] Graph layout remains usable on a narrow viewport. - [x] No major console errors appear during normal graph usage. --- ## Verification Checklist ### Local Verification - [x] Run frontend build. - [x] App runs locally. - [x] User can log in locally. - [x] Open a world with multiple entities and relationships. - [x] Open the Relationship Graph route/page. - [x] Confirm entities appear as graph nodes. - [x] Confirm relationships appear as directional edges. - [x] Confirm relationship labels or types appear where practical. - [x] Refresh the graph route/page. - [x] Confirm the graph route/page remains stable. - [x] Open a world with entities but no relationships. - [x] Confirm the graph page does not crash. - [x] Open a world with no entities. - [x] Confirm the graph page does not crash. - [x] Test desktop layout. - [x] Test narrow/mobile layout. - [x] Confirm no major console errors appear. ### Production Verification Complete after merge/deploy: - [x] Production frontend loads successfully. - [x] Production login works. - [x] Production world detail flow works. - [x] Production Relationship Graph route/page loads successfully. - [x] Production Relationship Graph route refresh works. - [x] Production entity nodes render correctly. - [x] Production relationship edges render correctly. - [x] Production sparse/empty graph states do not crash. - [x] Backend health endpoint is reachable. - [x] No major production console errors appear. --- ## Out of Scope - Relationship type filtering. - Selected entity highlighting. - Incoming/outgoing relationship highlighting. - Graph search. - Graph layout persistence. - Drag-and-drop graph editing. - Creating or editing relationships from the graph. - README, ROADMAP, CHANGELOG, and release notes finalization. --- ## Notes - Keep the first graph implementation simple and stable. - Graph rendering should defensively handle missing or incomplete entity/relationship data. - If a graph library is introduced, keep it lightweight and maintainable. - Sprint 2 will build on this by adding navigation, filtering, and highlighting.

foravo_admin commented

2026-05-19 05:04:48 +00:00

Owner

Imported from GitHub issue conorgregson/worldbuilding-codex#21.

Source: https://github.com/conorgregson/worldbuilding-codex/issues/21
Original author: @conorgregson
Original state: closed

Goal

Add the core Relationship Graph foundation for Worldbuilding Codex v1.3 by creating a dedicated graph view that visually represents connected lore.

Sprint 1 should establish the first working version of the graph by loading world entities and relationships, then rendering them as nodes and directional edges.

Context

Worldbuilding Codex v1.3 focuses on adding a visual Relationship Graph so users can better understand how lore entities connect across a world.

This sprint is the foundation layer. It should prioritize stable routing, graph data loading, basic rendering, and safe behavior for sparse or empty graph data.

Later sprints will add filtering, selection, highlighting, accessibility polish, responsive polish, and release documentation.

Scope

Add a dedicated Relationship Graph route or page section.
Load the selected world’s entities and relationships.
Render entities as graph nodes.
Render relationships as directional graph edges.
Show relationship type or label information where practical.
Add navigation from the world detail page to the Relationship Graph view.
Add a clear graph page heading and helper text.
Handle worlds with entities but no relationships.
Handle worlds with no entities.
Confirm graph route refresh behavior.

Acceptance Criteria

Users can open a Relationship Graph page or section for a world.
Relationship Graph route/page is protected behind authentication.
Relationship Graph route/page loads the correct world data.
Entities render as visible graph nodes.
Relationships render as visible directional edges.
Relationship type or label information appears where practical.
Users can navigate to the graph view from the world detail page.
A world with entities but no relationships does not crash.
A world with no entities does not crash.
Refreshing the graph route/page does not crash.
Graph layout is usable on desktop.
Graph layout remains usable on a narrow viewport.
No major console errors appear during normal graph usage.

Verification Checklist

Local Verification

Run frontend build.
App runs locally.
User can log in locally.
Open a world with multiple entities and relationships.
Open the Relationship Graph route/page.
Confirm entities appear as graph nodes.
Confirm relationships appear as directional edges.
Confirm relationship labels or types appear where practical.
Refresh the graph route/page.
Confirm the graph route/page remains stable.
Open a world with entities but no relationships.
Confirm the graph page does not crash.
Open a world with no entities.
Confirm the graph page does not crash.
Test desktop layout.
Test narrow/mobile layout.
Confirm no major console errors appear.

Production Verification

Complete after merge/deploy:

Production frontend loads successfully.
Production login works.
Production world detail flow works.
Production Relationship Graph route/page loads successfully.
Production Relationship Graph route refresh works.
Production entity nodes render correctly.
Production relationship edges render correctly.
Production sparse/empty graph states do not crash.
Backend health endpoint is reachable.
No major production console errors appear.

Out of Scope

Relationship type filtering.
Selected entity highlighting.
Incoming/outgoing relationship highlighting.
Graph search.
Graph layout persistence.
Drag-and-drop graph editing.
Creating or editing relationships from the graph.
README, ROADMAP, CHANGELOG, and release notes finalization.

Notes

Keep the first graph implementation simple and stable.
Graph rendering should defensively handle missing or incomplete entity/relationship data.
If a graph library is introduced, keep it lightweight and maintainable.
Sprint 2 will build on this by adding navigation, filtering, and highlighting.

foravo_admin

closed this issue
added the
enhancement

relationships

responsive

routing

v1.3
labels

Rows
Columns

Sprint 1 — Graph Foundation #7