Give every component a team of five.

teleon.dev/docs/pods assigns each component and queue a five-role pod: a deterministic engine, a solver, a supervisor, a repair agent and a verifier. Teams are managed here, along with the middleware each pod runs through.

teleon.dev/docs/podsPod governancehttpsjsonmcp

Read the docs Copy the agent prompt

The pod for one componentaq17 search

R1 Deterministic engineCode

RunsSQL, BM25F, AST, Wasm

Slotbm25f_roaring_v3

R2 Primary solverAgent

Works onone flat task row

Freedomopen search

R3 Supervisor

Watchesdepth, stalls, limits

Actionsplit, keep parent

R4 Repair and shim

Checksedge contract first

Buildsshims for mismatches

R5 Verifier and distillerOther family

Gradescross-family

Distillsrepeat wins to code

R1 answers in code where it can. R2 takes the rest, R3 splits stalled work, R4 repairs edges and R5 checks with a different model family.

What it does

Five clear roles

Engine, solver, supervisor, repair and verifier each own one part of the work.

Code first, models second

The deterministic engine answers what it can; the solver handles the rest with freedom to search.

Checked by another family

The verifier grades with a different model family and distills repeat wins into code.

The contract

Every component and queue is governed by one pod record with five filled roles.

Pod recordteleon_component_pod_team/v1

RolesR1 engine, R2 solver, R3 supervisor, R4 repair, R5 verifier

MiddlewareUp to 32 thin wrapper layers per pod

AccessRING-1 to change a pod; RING-3 to read

Identifiers

teleon_component_pod_team/v1
teleon_parent_preserving_supervisor/v1

Execution contracts

Request and responseCopy

GET /v1/pods/aq17_hybrid_search

# Response
{
  "component": "aq17_hybrid_search",
  "roles": {
    "R1_DET_ENGINE": "bm25f_roaring_v3",
    "R2_PRIMARY_SOLVER": "slot-11",
    "R3_QUEUE_SUPERVISOR": "split-supervisor",
    "R4_DIAGNOSTIC_REPAIR": "repair-shim",
    "R5_VERIFIER_DISTILLER": "cpop-distill"
  }
}

Endpoints

Method	Path	Access	What it does	Status
`GET`	`/v1/pods`	RING-3	List pods and their role holders	Listed
`GET`	`/v1/pods/{component}`	RING-3	Read one pod and its wrapper chain
`PUT`	`/v1/pods/{component}/roles`	RING-1	Assign or rotate a role holder
`GET`	`/v1/wrappers`	RING-3	Inspect the middleware layers in use	Listed

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/pods.

How it connects

Reads from

Routerteleon.dev/docs/router Thin wrappersteleon.dev/docs/wrappers

Feeds into

Queue brokerteleon.dev/docs/queues Auditorsteleon.dev/docs/auditors Voting and conflictsteleon.dev/docs/decisions

Queuesaq41 aq42 aq88 aq28

StoresS6 Versioned Schemas, Lineage, Scorecards and Private Vault

For agents

Give your agent the read-only guide first. It reports back before any write.

Agent prompt

Read https://teleon.dev/docs/pods.md and describe the five pod roles. Read only: ask me before changing any pod.

Copy

llms.txt Agent card MCP card

Words on this page

Full glossary

Pod: A small team of agent roles that owns one component: it builds, checks and repairs it together.
CPOP: Cross-provider pairing: the model family that checks a result differs from the one that made it.
Kleisli wrapper: A thin layer that wraps a call with one concern, such as clamping inputs or scrubbing secrets, and composes with others.
Deterministic check: A check written as code that gives the same answer every time for the same input, at code speed and cost.