One core database, a schema per site.

teleon.dev/docs/db holds the shared core tables every service reads: entities, executable payloads, annotations, weighted graph edges and bitemporal facts. Each site keeps its own tables in its own schema beside the core.

teleon.dev/docs/dbShared databaseTELEON-SVC-01httpsjson

Read the docs Copy the agent prompt

Core and site schemas

Site schemasone per site you run, for example surface_store and surface_docs

Row-level securityRING-0 to RING-3

teleon_coreentities, payloads, annotations, edges, facts

Every site reads the shared core and keeps its own tables in its own schema.

What it does

Shared core

Universal tables live in teleon_core and serve every site the same way.

A schema per site

Site-specific tables live in surface schemas, kept apart from the core.

Row-level security

Access rings decide which rows each caller sees.

The contract

Code bytes and their descriptions are stored apart, so a description can change while verified code stays as it is.

EnginePostgreSQL 17 with a connection pooler

Core schemateleon_core.*

Site schemassurface_<slug>.*

AccessRow-level security across RING-0 to RING-3

Identifiers

teleon_dual_track_request/v1
teleon_boundary_isolation/v1

Execution contracts

Sample queryCopy

-- core tables shared by every site
SELECT entity_id, kind, swhid
FROM teleon_core.teleon_entities
WHERE kind = 'capability'
LIMIT 3;

Copy

entity_id   | kind       | swhid
ent_00412   | capability | swh:1:cnt:ef1e...845e
ent_00413   | capability | swh:1:cnt:77c0...e1
ent_00418   | capability | swh:1:cnt:5e0c...a4

Endpoints

Method	Path	Access	What it does
`GET`	`/v1/health`	RING-3	Read health and replication lag
`GET`	`/v1/schemas`	RING-1	List core and site schemas with versions
`POST`	`/v1/migrations/plan`	RING-1	Plan a schema change through the gate

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

How it connects

Reads from

Identity and ringsteleon.dev/docs/auth

Feeds into

Entities cellteleon.dev/docs/entities-db Capability graph cellteleon.dev/docs/graph-db Queue storage cellteleon.dev/docs/queues-db Ledger cellteleon.dev/docs/ledger-db Recordsteleon.dev/docs/records

Queuesaq22 aq71

StoresS4 Canonical Entities, Leads and Bitemporal Attributes S18 Unified Partitioned Core Rows and LSH Bands

For agents

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

Agent prompt

Read https://teleon.dev/docs/db.md and list the core tables. Read only.

Copy

llms.txt Agent card

Words on this page

Full glossary

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.
Partition: One slice of a large table, chosen by a key such as site or queue, so reads and writes stay fast.
Bitemporal: A record that keeps two times: when a fact was true in the world and when the system learned it.
Sister track: The improvement track that runs beside each database: it tunes priorities, synonyms and steps behind holdout checks.