How every capability connects, with weights.

teleon.dev/docs/graph-db stores the weighted edges between capabilities: which composes with which, how often a path succeeds, and what was believed when.

teleon.dev/docs/graph-dbDatabase cellhttpsjson

Read the docs Copy the agent prompt

Edges from one component

csv_readerout: rows

typed: rows

schema_checkweight 0.94

dedupe_rowsweight 0.81

parquet_writerweight 0.77

Stronger edges are paths that passed their checks more often.

What it does

Weighted edges

Each edge carries a weight learned from real runs.

Typed ports

Edges join output ports to matching input ports.

Assertions over time

Each edge keeps its history, so past graphs can be rebuilt.

The contract

Edges are calibrated from run receipts and kept as bitemporal assertions.

HoldsTyped, weighted edges

WeightsUpdated from run receipts

StoreS3 typed edges and composed graphs

AccessRING-1 and services

Identifiers

typed_edge_graph

Execution contracts

Four-stage value-generation spine and bot lineage

Sample queryCopy

SELECT src, dst, port, weight
FROM teleon_core.teleon_weighted_graph_edges
WHERE src = 'csv_reader'
ORDER BY weight DESC
LIMIT 3;

Endpoints

Method	Path	Access	What it does	Status
`GET`	`/v1/health`	RING-3	Read the cell's health
`GET`	`/v1/edges`	RING-2	Read edges for a component

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/graph-db.

How it connects

Reads from

Database and graph coreteleon.dev/docs/db Telemetry and driftteleon.dev/docs/telemetry

Feeds into

Composition arenateleon.dev/docs/arena Component mapteleon.dev/docs/dag Cheapest solutionsteleon.dev/docs/cheapest

Queuesaq18 aq64 aq119

StoresS3 Typed Edges, Engine Slots and Composed Graphs

For agents

Give your agent the read-only guide first. It reports back before any write.

Agent prompt

Read https://teleon.dev/docs/graph-db.md and list the strongest edges from one component. Read only.

Copy

llms.txt Agent card

Words on this page

Full glossary

DAG: A directed acyclic graph: steps joined by one-way edges, so work flows forward in a known order.
Bitemporal: A record that keeps two times: when a fact was true in the world and when the system learned it.
Contract: A versioned agreement on the shape of a request and response, so either side can change behind it safely.