Project Telos
About
Local-first MCP tools for AI-assisted work receipts, source intake, workspace maps, routing ledgers, action receipts, and MATCH / DRIFT / UNVERIFIABLE verification.
Details
- Author
- harperz9
- Categories
- Developer Tools, Automation, Other, Productivity
Jump to
Setup
Install Project Telos in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/harperz9/telos
Follow the installation instructions in the repository README, then restart your MCP client.
The shared workbench: durable state, native workstation control, sensory organs, a discovery forge.
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 singlenode demo/run.mjs. Every run writes a receipt you can re-check.
Project Telos|gather|crucible|index|forum|telos|learn|emet|buildlang
- One MCP surface over five flagships.node demo/telos-mcp.mjs(ornpm start) runs a stdio MCP server exposing 41 nativetelos.*tools, and the server manifest launches gather, index, forum, and crucible beside it: 69 tools total plus 29 declared auxiliary compatibility tools, with ready-to-paste host config for Codex (TOML), Claude (JSON), and OpenAI Agents.
- Four proof lanes through one CLI.node demo/proof.mjsassembles 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, andnode demo/proof.mjs verify <packet.json>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 atdemo/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.mjsdrives the browser via the Chrome DevTools Protocol and native apps via Windows UI Automation, delivering synthetic events so the operator's cursor and keyboard stay free; the MCP tooltelos.native.controlis the read-only capability catalog, and browser-evidence packets make automated browsing reviewable.
Zero runtime dependencies. Node 20 or newer; CI runs on Node 24.
git clone https://github.com/HarperZ9/telos.git cd telos node demo/run.mjs
demo/run.mjsrenders a 4-D cube, perceives it through independent channels, checks the recovered vertex and edge counts against the true criterion, and prints a certificate that re-checks from its own evidence. Then it feeds the loop a render too small to read and shows it returning UNVERIFIABLE instead of a confident pass. A verifier that cannot fail is not a verifier.
From there, the two orientation commands:
node demo/catalog.mjs --summary # operator map: 69 tools across 5 flagships node demo/server-manifest.mjs --summary # 5-server MCP launch map with host config
Project Telos MCP Catalog tools 69 total, 69 available transport stdio, streamable-http gather 5 tools ... index 5 tools ... forum 5 tools ... crucible 13 tools ... telos 41 tools ...
To run the MCP server for a host:npm start(stdio). Health and state:
node demo/status.mjs --summary node demo/doctor.mjs --summary node demo/room.mjs --json
Every command emits aproject-telos.flagship-action/v1envelope with a MATCH, DRIFT, or UNVERIFIABLE status. The package also shipstelosandtelos-mcpbin entries that route to the same demo surface.
Worked example: a proof packet that can fail
Assemble the demo agent-action proof packet, then replay its verification from the packet alone:
node demo/proof.mjs agent-action --demo --json > packet.json node demo/proof.mjs verify packet.json
The packet joins source refs, context refs, route, admission decision, side effects, and output digests. The verifier recomputes digests from the embedded materials, so editing any load-bearing field flips the verdict to DRIFT, and a missing recomputable basis is reported as UNVERIFIABLE with the gap named by path. The sibling lanes work the same way:researchrecomputes source and negative-control digests and refuses reproduction-gated promotion in a single packet,visualrecomputes color and luminance from embedded sRGB samples, andbuildrecomputes a conserved-quantity invariant against a negative fixture that must break it. The delivery ledger isdocs/PROOF-LANES.md.
node demo/catalog.mjsis the authoritative map. Highlights by area:
Most accept--summaryfor a compact terminal (TUI) view and--jsonfor IDE, app, and automation hosts.
The doctor lanes in full:node demo/ci-doctor.mjs,node demo/presentation-doctor.mjs,node demo/accessibility-doctor.mjs,node demo/performance-doctor.mjs,node demo/compatibility-doctor.mjs, andnode demo/operator-doctor.mjs, plusnode demo/ci-triage.mjsandnode demo/mcp-freshness.mjs. Live CI intake works read-only:node demo/ci-triage.mjs --gh-run owner/repo#run_id --summary.
- docs/INTRODUCTION.md: what Telos is and your first ten minutes.
- docs/HOW-IT-WORKS.md: the verifier loop, step by step, including where it stops.
- docs/ARCHITECTURE.mdanddocs/PROJECT-CONNECTION-MAP.md: system shape and how the five flagships connect.
- docs/PROOF-LANES.md: the proof-lane contracts and delivery ledger.
- docs/CURRENT-STATE.md: the live evidence-first state packet.
- USAGE.md: install, run, MCP, and verify commands.
Peer repos:gather(research intake),index(workspace maps and context),forum(agent routing with a causal ledger),crucible(claim verification),[emet(independent coherence witness). Telos launches and reconciles all five from one manifest; each also stands alone.
…
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
