Give each site the view it needs.

teleon.dev/docs/q18 routes answers and byte streams to each website through its own surface lens, so every site gets its own shape, wording and identity.

teleon.dev/docs/q18Queue cell Q18httpsjsonmcp

Read the docs Copy the agent prompt

One capability, three lenses

creative_native_project_request/v1one capability

projected per site

Studio lensscene cards

Library lensfile rows

Agent lensL0 card

The same capability is shaped three ways; each site keeps its own wording and identity.

What it does

One backend, many lenses

Each site sees capabilities shaped for its audience.

Exact bytes

Byte ranges stream straight from the content store.

Separate identities

Every site keeps its own brand, cookies and tokens.

The contract

A queue cell owns one kind of task end to end: its rows, its leases and its hand-offs.

HoldsDelivery tasks per site

RuleOne lens per website

FeedsSchema lenses, snapshot CDN

AccessRING-2 to claim

Identifiers

teleon_surface_handshake_plan/v1
teleon_boundary_isolation/v1

Execution contracts

Task rowCopy

{
  "queue": "q18",
  "surface": "media_site",
  "capability": "creative_native_project_request/v1",
  "lens": "studio_cards_v2"
}

Endpoints

Method	Path	Access	What it does	Status
`GET`	`/v1/lenses`	RING-3	List surface lenses
`POST`	`/v1/claim`	RING-2	Claim a delivery 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/q18.

How it connects

Reads from

API and handshakeapi.teleon.dev Capability cardsteleon.dev/docs/cards

Feeds into

Schema lensesteleon.dev/docs/lenses Snapshot CDNteleon.dev/docs/cdn

Queuesaq20 aq22 aq94

StoresS2 Code Descriptions and L0, L1, L2 Cards

For agents

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

Agent prompt

Read https://teleon.dev/docs/q18.md and list the surface lenses. Read only.

Copy

llms.txt Agent card MCP card

Words on this page

Full glossary

Lens: A pair of functions that translate a request or response between two schema versions in both directions.
Handshake: The first call a site or agent makes to agree on API version and settings for everything that follows.
Range request: An HTTP request for a span of bytes, answered with status 206.