HarperZ9/telos

One workbench, and packets that recompute their own claims.
Telos is a zero-dependency local workbench for creating, simulating, and replaying AI work. It ships a five-server MCP surface plus CLI fallbacks: doctors for CI, presentation, accessibility, performance, and compatibility, a creative engine with deterministic kernels and ten measurement meters, model-foundry and learning-forge lanes, and research proof packets spanning causal, embodied, and quantum demos. It ties gather, index, forum, and crucible into one operator map you can run with a single node demo/run.mjs. Every run writes a receipt you can re-check.
Project Telos | gather | crucible | index | forum | telos | learn | emet | buildlang
What it does
- **One MCP surface over five flagships.** node demo/telos-mcp.mjs (or npm start) runs a stdio MCP server exposing 50 native telos.* tools, and the server manifest launches gather, index, forum, and crucible beside it: 78 tools total plus 36 declared auxiliary compatibility tools, with ready-to-paste host config for Codex (TOML), Claude (JSON), and OpenAI Agents.
- **Read the web, Reddit and X.** telos reach and nine MCP tools read public pages, feeds and sitemaps through a crawler that obeys robots.txt and Crawl-delay, Reddit through its official Data API with your own app, single X posts through X's public oEmbed endpoint, the X API with your own key, and official APIs such as Hacker News, GitHub, arXiv and Wikipedia. Every request lands in a receipt with its robots.txt decision and a SHA-256 of the bytes. telos reach doctor shows which channels work for you, with no side effects. See the reach guide.
- **Four proof lanes through one CLI.** node demo/proof.mjs assembles agent-action, research-claim, visual-truth, and build proof packets. Each has a pure verifier that recomputes every load-bearing claim from materials embedded in the packet, so a canned pass is structurally impossible, and node demo/proof.mjs verify replays any of them by schema id.
- **Nine doctors.** CI doctor and CI triage read GitHub Actions state and separate fatal failures from runtime migration warnings. Presentation, accessibility, performance, compatibility, and operator doctors audit README parity, static a11y, byte budgets, protocol coverage, and discoverability. All run offline against local checkouts.
- **A creative engine you can measure.** Deterministic kernels (ordered dither, pixel sort, harmonograph, clustered light), a WebGPU/WebGL/canvas/static renderer selection contract, and ten runnable meters across histogram, dither, splat, cluster, audio, flicker, curvature, interaction, uncertainty, and frame-budget signals. The visual surface lives at demo/index.html.
- **Research proof packets.** Deterministic preflights for causal inference (toy-DAG minimal adjustment set), embodied sim-to-real (differential drive with safety envelope and latency bound), and quantum error correction (3-qubit bit-flip stabilizer code), each with negative controls and explicit non-claims.
- **Model foundry and learning forge.** A bounded contract for routing work across hosted frontier APIs and local open-weight models, seven executable lab contracts with failure cases and metrics, and a self-improving daemon loop that only promotes verified changes.
- **Context tooling for large codebases.** Budgeted, validated context packs and envelopes for handing a big workspace to a model without losing provenance.
- **Native workstation control.** node demo/native-control.mjs drives the browser via the Chrome DevTools Protocol and native apps via Windows UI Automation. UIA focus and keyboard-input actions can affect the foreground window; receipts distinguish known focus behavior from unknown effects. An explicit browser match must select one target. The MCP tool telos.native.control remains a read-only capability catalog. See the control contract before actuation.
See it work, step by step
The animated explainer