How the whole backend fits together.

teleon.dev/docs/architecture is the blueprint: the shared core beside each site's own schema, the two tracks every database runs on, and the order the services were built in.

teleon.dev/docs/architectureBlueprint v1httpsmarkdownjson

Read the blueprint Copy the agent prompt

The build order

1Storage and content storedb, cas, cdnWave 0

2Identity and handshakesauth, apiWave 1

3SearchsearchWave 2

4QueuesqueuesWave 3

5SandboxsandboxWave 4

6Gateway and ledgermcp, ledger, telemetryWave 5

Each wave stands on the one before it, so sites connect to a working backend.

What it does

Shared core, site schemas

Universal tables live once in the core; each site keeps its own tables beside it.

Two tracks per database

An operational track serves traffic; a sister track improves it behind holdouts.

Built backend first

Storage, identity, search, queues, sandbox, then the gateway and ledger.

The contract

The blueprint is published as Markdown and JSON so agents and people read the same plan.

FormatsMarkdown and JSON

WavesSix build waves, storage first

Rule of twoA primitive joins the core once two sites need it

AccessRING-3

Identifiers

teleon_dual_track_request/v1
teleon_boundary_isolation/v1

Execution contracts

Request and responseCopy

GET /architecture
Accept: application/json

# Response
{
  "core": "teleon_core.*",
  "site_schemas": ["surface_store", "surface_docs", "surface_support"],
  "waves": ["storage", "identity", "search", "queues", "sandbox", "gateway_and_ledger"]
}

Endpoints

Method	Path	Access	What it does	Status
`GET`	`/architecture`	RING-3	Read the blueprint as Markdown or JSON	Listed
`GET`	`/index.json`	RING-3	Read the machine index	Listed

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/architecture.

How it connects

Reads from

Database and graph coreteleon.dev/docs/db Component mapteleon.dev/docs/dag

Feeds into

Teleon documentationteleon.dev/docs Orientationteleon.dev/docs/orient

Queuesaq22 aq28

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/architecture and summarize the build order. Read only.

Copy

llms.txt Agent card

Words on this page

Full glossary

Sister track: The improvement track that runs beside each database: it tunes priorities, synonyms and steps behind holdout checks.
Access ring: One of four access levels. RING-0 is internal operations, RING-1 operators, RING-2 keyed agents and sites, RING-3 public reads.
Handshake: The first call a site or agent makes to agree on API version and settings for everything that follows.