A graph makes a connection visible. Its names, sources and correction history give you something to check before trusting it.
Explore a small part of my actual project graph, then practice a correction you can undo.
A real project-data sample. Edits here stay in this browser.
31 original entity labels / 33 distinct connectionsHistorical extraction sample · checked 14 October 2026
A three-minute field trip
Try the graph. Leave a small edit. Bring it back.
Start with panelforge. The lines show extracted build relationships. Choose a connected label or a connection in the list to inspect it.
02 / Follow its neighborhood
panelforge
Project · extracted historical relationships
Selected connection
panelforge built_with inertia-js
Arrowheads follow the stored direction. Select a connection to read it; choose an entity in the index to move the focus.
Connections as a list
No visible connections remain for this entity. Undo an edit, reset the sample, or choose another label.
Your local edit trail
A change with a way back.
These receipts describe only your interaction with this illustration. The exported sample stays intact.
33 of 33 connections visible
No edits yet. Select a connection and try setting it aside.
The reading rules
Memory needs a little doubt.
01
A name is not a verdict.
vue, vue-js and vue-3 appear as separate labels in this sample. They may overlap in meaning. That alone is not enough evidence to merge them, and a versioned name may carry useful context.
02
A line is a claim to inspect.
built_with is the graph's stored predicate. Read it in its source context: a conversation might concern one component, prototype or stage of the project. This sample is not a map of today's architecture.
03
A correction needs a return path.
The lab preserves the selected tuple and previous view for undo. The real curation work uses action records and before-state snapshots; this local illustration shows why a correction should remain inspectable.
The interactive lab gives the data a small, readable stage. This recording shows the real PanelForge graph: searching for the project, filtering build relationships and focusing its neighborhood.
Actual product recording. The lab above uses a separately audited subset of the same filtered graph.Search narrows the actual graph to PanelForge. A predicate filter selects build relationships, then selecting the project brings nearby software into focus. Zoom and fit change the view. Cuts shorten stationary pauses.What happens in this recording
Actual product recording. The lab above uses a separately audited subset of the same filtered graph.
Search narrows the actual graph to PanelForge. A predicate filter selects build relationships, then selecting the project brings nearby software into focus. Zoom and fit change the view. Cuts shorten stationary pauses.