Improve each database beside its daily work.
teleon.dev/docs/improve runs the improvement track beside every database: it tunes priorities, locales, synonyms and steps, and each change passes holdout checks and review before it reaches traffic.
Every proposal runs against holdouts first; reviewers apply only the ones that win.
What it does
Two tracks per database
One track serves requests; the sister track proposes improvements.
Holdouts decide
A change ships only when it beats the baseline on held-out data.
Six tuning dimensions
Priorities, locales, synonyms, steps, weights and thresholds.
The contract
Each database unit has an operational connector and an improvement connector, governed by one policy.
teleon_dual_track_request/v1LayerGovernancePolicy
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/proposals | RING-3 | Browse improvement proposals | |
POST | /v1/proposals/{id}/apply | RING-1 | Apply a proposal that passed review |
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/improve.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- Sister track
- The improvement track that runs beside each database: it tunes priorities, synonyms and steps behind holdout checks.
- Holdout
- Test data kept apart from training and tuning, so scores on it show real performance.