Split out from #17. Parked — no implementation until the design questions below are answered.
Open questions
- What triggers expansion? User action, viewport, drill-down on a view?
- Where does the expanded graph come from? Metadata service, live DB introspection, bundled catalog?
- Caching and invalidation model.
- Permissions model. FlowScope is privacy-first and browser-based — what, if anything, leaves the browser?
Related work
- Flat-model refactor is a prerequisite (a
CrossAssets EdgeType only makes sense once node lists are unified).
- Collapse/expand UI issue provides the visual primitive.
Next step
Write docs/design/lazy-expansion.md. Do not open PRs against this issue until the design is reviewed.
Split out from #17. Parked — no implementation until the design questions below are answered.
Open questions
Related work
CrossAssetsEdgeTypeonly makes sense once node lists are unified).Next step
Write
docs/design/lazy-expansion.md. Do not open PRs against this issue until the design is reviewed.