Match each task to allowed compute.
teleon.dev/docs/q19 matches work units to compute pools under usage and license rules, keeping free inference and sandboxed execution in their own lanes.
| Unit | Needs | Pool |
|---|---|---|
| pwu_7710 | GPU, commercial | managed_gpu_a |
| pwu_7711 | CPU, open license | donor_pool_3 |
| pwu_7712 | GPU, research | waiting for GPU |
Each unit goes to a pool whose rules allow it; the donor pool takes public-good work.
What it does
Rules first
Each pool states what it may run: who pays, which licenses, which hardware.
Free and paid apart
Free inference and sandboxed execution use separate lanes.
Capacity feeds
Pools publish snapshots of what they can take right now.
The contract
A queue cell owns one kind of task end to end: its rows, its leases and its hand-offs.
portable_work_unit/v1capacity_feed_snapshot/v1
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/pools | RING-3 | Read capacity snapshots | |
POST | /v1/claim | RING-2 | Claim a matching task |
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/q19.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- 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.
- Lane
- A path through the queues for one kind of contribution, such as describing files or solving problems.