See quality drift before users do.
teleon.dev/docs/telemetry takes in scrubbed evidence from every run, updates the weights on the capability graph, and watches for drift with canary checks every six hours.
The canary flagged the dip on day 5; a repair task brought the pass rate back.
What it does
Scrubbed on the way in
Personal data and secrets are removed before anything is stored.
Weights that learn
Each receipt nudges the graph's edge weights toward what works.
Drift caught early
Canary checks compare today with a baseline and flag movement.
The contract
Telemetry records are scrubbed receipts; drift alerts cite the baseline they compared.
teleon_dual_track_request/v1
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
POST | /v1/receipts | RING-2 | Send a scrubbed run receipt | |
GET | /v1/drift | RING-3 | Read current drift checks |
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/telemetry.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- Drift
- A slow change in inputs or results over time, caught by comparing today's readings with a baseline.
- Canary
- A small share of traffic or checks run against a change first, so a problem shows up early and stays small.
- Baton
- The hand-off between queues: when one step finishes, its output becomes the next queue's input row.