The Journey So Far

Roadmap vs journey

Roadmap

The roadmap is the forward-looking page: where Thomas is headed, what the three big phases are, and what each phase is trying to unlock.

Open the roadmap

Journey

This page stays practical. It tracks what has actually shipped, what changed in the architecture, and what constraints still define the product.

Why Thomas exists

Most AI tools let the AI do whatever it wants. Thomas makes every action go through an approval step first. Nothing runs without your OK.

The goal: a local execution tool with explicit approvals and verifiable contracts for every command. You stay in control.

What we won't compromise on

  • No unbounded execution. Every action is tied to a command family and policy gate.
  • Local-first operation, with remote integration explicit and bounded.
  • We only ship claims backed by release artifacts and release notes.

Milestones

2026-02

Execution boundary enforced

Implemented

Request parsing and approval gates now sit in front of every execution path.

2026-02

Command family contracts

Implemented

Each command family has depth markers and validation tied to releases.

2026-02

Release-linked observability

Partial

Download, artifact, and log metadata merged into one evidence trail.

2026-03

Gateway and CLI alignment

Partial

API routes and CLI commands now share the same validation surface.

What's next

  • Expand plugin sandbox and policy checks.
  • Improve release reproducibility without adding complexity.
  • Keep the control plane as a view over local execution, not a standalone agent.

What's not planned: Letting the AI run anything without approval, adding features without contract-backed evidence, or skipping reproducibility checks.

Thomas Infinite

The mobile companion app for Thomas. Still in development.

See what Thomas is doing from your phone. Queue commands, check results, approve actions. Everything still goes through Thomas for policy, validation, and audit. Infinite is a window, not a backdoor.

What stays local

Infinite is a UI surface, not a standalone runtime.

What can be remote

Tokened transport and pairing are supported; key rotation is still in progress.

What it won't do

Infinite never runs commands outside the Thomas core path.