Add one concern at a time, safely.
teleon.dev/docs/wrappers composes chains of up to 32 thin layers around an engine, each adding one concern such as clamping, engine choice or scrubbing. Databases are served directly, outside the chain.
Each layer adds one concern. The engine inside can be swapped while callers stay the same.
What it does
One concern per layer
Each wrapper does one job and composes with the others.
Dry-run first
A chain runs against fixtures before it serves traffic.
Engine slots
Swap the engine inside the chain while callers stay the same.
The contract
A chain is an ordered list of wrappers around one engine slot; database calls go direct.
recursive_component_wrapper_engine/v1
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/wrappers | RING-3 | Inspect chains in use | Listed |
GET | /v1/wrappers/{component} | RING-3 | Read one component's chain | |
POST | /v1/wrappers/{component}/dry-run | RING-1 | Dry-run a proposed chain |
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/wrappers.
Words on this page
- Kleisli wrapper
- A thin layer that wraps a call with one concern, such as clamping inputs or scrubbing secrets, and composes with others.
- Contract
- A versioned agreement on the shape of a request and response, so either side can change behind it safely.