See how every part connects, live.
teleon.dev/docs/dag draws the self-describing map of databases, queues and connectors: what feeds what, which version is live, and where a change would ripple.
Selecting a node highlights what feeds it and what it feeds.
What it does
Live topology
Nodes and edges come from the running services, so the map stays current.
Versions on every node
Each node shows the version it runs and its contract.
Ripple view
Select a node to highlight everything downstream of it.
The contract
The map is built from service self-descriptions and queue graph edges.
typed_edge_graph
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/dag | RING-3 | Read the map around a node | |
GET | /v1/dag/ripple/{node} | RING-3 | List everything downstream of a node |
Listed paths appear in the service’s published files today. In the one-host plan every path here is served under api.teleon.dev/v1/dag.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- DAG
- A directed acyclic graph: steps joined by one-way edges, so work flows forward in a known order.
- Baton
- The hand-off between queues: when one step finishes, its output becomes the next queue's input row.