Raw Payload
The static explorer stays available as its own subordinate payload.
This wrapper keeps the tool inside the shared shell while leaving the tree browser and data-binding internals untouched for now.
Static Tool Surface
The concept explorer now has the same framing strategy as the workbench and resolver surfaces while its internals stay unchanged.
Concept Explorer
Browse the UM concept space without dropping into an isolated raw app.
The explorer remains a static browser tool backed by a published concept graph. This route adds the shared shell, clearer framing, and a stable public entry while the original payload stays available at a subordinate path.
Explorer Payload
The underlying app runs unchanged behind a clearer route and frame.
The shared shell now does the explanation and routing work. The browser tool remains the same payload underneath it.
Related Surfaces
The concept explorer now fits the broader tool family.
Use the shared-shell route for a stable public entry or jump to the raw payload and source data when you need the underlying pieces directly.
Concept Data
The source data remains separately inspectable.
You can still fetch the underlying concept graph directly without loading the explorer UI, which helps machine evaluators and manual debugging.
Shared Tool Tier
The explorer now sits with the rest of the public tool family.
This keeps the MVP front door calm while making it clearer that the explorer belongs to the broader tool-and-proof layer.