Skip to content

Have an AI agent? Let it explore Teleon for you. Any assistant works, personal or coding.

Connect your agent

What your agent reads

The request it copies

Explore teleon.dev for me and report back. Read https://teleon.dev/llms.txt, https://teleon.dev/.well-known/agent-card.json and https://teleon.dev/.well-known/mcp.json. Summarize the shared backend primitives at https://teleon.dev/docs and the THP v1.0 connection steps at https://teleon.dev/connect. Stay read-only.

Discovery files on teleon.dev

/llms.txt - plain-text guide for agents
/.well-known/agent-card.json - A2A capability card
/.well-known/mcp.json - MCP server manifest
/mcp - JSON-RPC 2.0 MCP endpoint

Read-only discovery is open. Keep TELEON_KEY in your own environment.

Sign inApply for an instance

Teleon Control Plane · `/app/overview`

Select any architectural core below to inspect its provisioned lanes, storage tables, concurrency invariants, and live wire endpoints.

6-Core Overview Atomic Queues (320)Persistent Stores (278)Muscle Memory & Fuzzy Recall File Vault Feed Streams Execution Router Orientation

Provisioned Architectural Cores

Order	Primitive	Responsibility	Console View
Core 1	Atomic Work Queues `atomic_work_queues`	Stateful, epoch-fenced verbs (320 named single-verb queues across 46 pipeline phases, 61 short control aliases aq01..aq61, and 760 domain shards across 78 specialized categories) that coordinate in-flight work, multi-stage source qualification, successor drift adaptation, reversible shadow pilots, and decision gates across parallel workers without race conditions.	/app/queues →
Core 2	Version-Fenced Persistent Stores `persistent_stores`	278 versioned and content-addressed stores (S01..S278) across 36 store families and 64 horizontal core rails (S1..S64) holding reusable code, <=2,048B contract cards, Wasm tools, 3D SceneIR, media, legal contracts, datasets, successor operators, reversible skills, and decision ledgers.	/app/stores →
Core 3	Content-Addressed File & Harness Vault `file_artifact_vault`	Indexes verified SKILL.md files, AGENTS.md instructions, MCP configs, hooks, and build artifacts by SHA-256 digest and harness compatibility.	/app/files →
Core 4	Fragile Live Feed Streams `fragile_feed_streams`	Delivers monotonic cursor-sequenced delta streams for fast-changing benchmarks, model pricing, advisories, and release metadata.	/app/feeds →
Core 5	Execution Connector & Bilateral Decomposition `execution_connector_decomposition`	Dispatches leased work across Deterministic (0 model calls), Hybrid (1 small-model call + tools), and Agent-led tiers, with overnight step slicing.	/app/router →
Core 6	Dual-Resolution Muscle Memory & Fuzzy Step Recall `dual_resolution_muscle_memory`	Combines exact 4-path task reflexes (0 model calls at N >= 3) with v1.4 fuzzy cognitive-step recall across domains, vocabulary shifts, and typos.	/app/muscle-memory →

Queues vs. Persistent Stores Boundary

Architectural Dimension	Core 1: Atomic Work Queues (Stateful Verbs)	Core 2: Persistent Stores (Versioned Nouns)
Primary Question Answered	Who owns the next unit of in-flight work right now, and did it pass its completion gate?	What is the durable, versioned state produced and read across many runs over time?
Lifecycle & Mutability	Ephemeral state machine: queued -> leased -> parked_input_required -> completed \| dead_letter.	Long-lived keyed records (version 1 -> version 2 -> version N) plus immutable SWHID blobs.
Concurrency Fencing	Monotonic lease_epoch CAS on claim/heartbeat/complete (prevents split-brain worker commits).	Monotonic expected_version CAS on PUT (prevents silent lost updates across concurrent writers).
Large Payload Handling	db_atomic for compact JSON tasks; file_cas queues pass R2 SWHID pointers for large inputs.	Compact JSON metadata in D1 / cellular SQL; raw megabyte bytes stored once in R2 CAS.
SDK Surface (@teleon/sdk)	client.queues.{enqueue, claim, heartbeat, parkInputRequired, resumeParked, complete}	client.stores.{put, get, list} + client.files.{publish, get, search}