Store any kind of record in one table.
teleon.dev/docs/records keeps every kind of record in one self-describing table. New kinds arrive with their own schema in the envelope, and row versions keep concurrent writes safe.
| Record | Kind | Schema | Version |
|---|---|---|---|
| rec_501 | dataset_recipe | recipe/v1 | 4 |
| rec_502 | capability_note | note/v2 | 1 |
| rec_503 | scenario_seed | seed/v1 | 7 |
Every record names its own kind and schema, so new kinds fit the same table as they are.
What it does
Self-describing rows
Each record carries its kind and schema in an envelope.
Safe concurrent writes
A row version must match before an update lands.
Combinations streamed
Mixes of fields stream out as new rows for experiments.
The contract
A record is an envelope plus fields; the row version guards every write.
teleon_universal_flat_record/v1teleon_combinatorial_emission/v1
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/records | RING-2 | List records by kind | Listed |
PUT | /v1/records/{id} | RING-2 | Write a record with its row version |
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/records.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- OKF
- The schema-free record format at the first rung of the schema ladder, used for catch-all items.
- Idempotent
- Safe to repeat: running the same request twice leaves the same result as running it once.
- Partition
- One slice of a large table, chosen by a key such as site or queue, so reads and writes stay fast.