1# grafo-nav
2
3The navigable DAG contract, written once.
4
5Any DAG in the repo (Monads, commits, cells, messages) becomes navigable and
6manageable by implementing `GrafoNavegable`: it declares its nodes, its directed
7edges `(parent → child)`, and which `Verbo`s it allows on the selection.
8Everything structural — roots, heads, cone, fork — derives itself, purely, from
9the edges.
10
11The shared cockpit (`llimphi-widget-navigator::cockpit_grafo_view`) takes any
12`impl GrafoNavegable` and paints it with pan/zoom/selection and the verb palette.
13This crate knows NOTHING about the UI: only topology and vocabulary.
14
15Edge direction convention: `(from, to)` = `ancestor → descendant`.
16
17---
18
19Part of **shared** — see [shared](../README.md).
README.md
grafo-nav
The navigable DAG contract, written once.
Any DAG in the repo (Monads, commits, cells, messages) becomes navigable and
manageable by implementing GrafoNavegable: it declares its nodes, its directed
edges (parent → child), and which Verbos it allows on the selection.
Everything structural — roots, heads, cone, fork — derives itself, purely, from
the edges.
The shared cockpit (llimphi-widget-navigator::cockpit_grafo_view) takes any
impl GrafoNavegable and paints it with pan/zoom/selection and the verb palette.
This crate knows NOTHING about the UI: only topology and vocabulary.
Edge direction convention: (from, to) = ancestor → descendant.
Part of shared — see shared.