Ephesus
Roadmap

What is built, and what is not

The honest version. Milestones are only marked done when they close on a run rather than a checklist, audited by two independent passes — one verifying by execution, one checking the diff against the documented design.

Now M8 — hardening Next M7b — packaging and delivery Installer not until M7b.5
Landed

Eight milestones, each closed on evidence

M0

Skeleton

Electron shell, preload bridge, a real PTY vertical, the floor, persistent app state.

✓
M1

One real agent

A single agent CLI under management on both planes — the process, and the record of what it did.

✓
M3

The floor becomes true

Stations that are facts rather than decoration, the circuit breaker armed, gates that hold work.

✓
M5

The accountable company

A review task is mechanically unclosable until its deck is archived. New dependencies are held at the choke point until a memo is verdict-ed.

✓
M5b

The learning company

The Stoa: registered sources at pinned commits, read-only research plans, briefs whose findings must cite a path or die.

✓
M6

The floor’s face

Citizens at specification, stations, act-coloured envelope flights.

✓
M7

The outward missions

Skeleton Crew and Front Office — the company watching something real.

✓
M8

The company you can leave running

Coverage baseline and the seam rule; a quit path that actually runs; visible, countable degradations; every hire in its own checkout and its own engine install.

✓
Next

M7b — the milestone that produces an installer

M8 is being finished first, deliberately. M7b ships signed builds of a company that improves itself, and shipping that before it could survive a restart, report that it had stopped, or keep its agents out of the architect’s working tree would have been worse than not shipping it.

M7b.1

Company GitHub identity

One Architect-owned machine identity so the company can act on GitHub as itself.

·
M7b.2

Recursive Improvement profile

The self-improvement mission as a switchable crew.

·
M7b.3

Pull requests with provenance

Approved proposals arrive as pull requests that cite the brief they descend from.

·
M7b.4

Chat bridge

One Slack-compatible webhook so the company can reach you where you already are.

·
M7b.5

Packaging and update check

Signed builds for macOS, Windows and Linux. This is the milestone that turns Ephesus into something you can install.

·
M7b.6

Suites and exit review

The recursive chain proven end to end in CI.

·
Deliberately not planned

Things that are not coming

A roadmap that only lists intentions is half a roadmap. These are decisions, not omissions.

A hosted or cloud version

Ephesus is a desktop application that drives CLIs on your machine. A hosted version would need to hold your credentials and run your code on someone else’s computer, which is a different product with a different threat model.

A plugin marketplace

Not while the core is pre-alpha. A stable extension surface is a promise, and promises are expensive to keep.

Autonomy without gates

There is no configuration that removes the human from irreversible actions. Gates can be tuned; they cannot be turned off.

Support for every agent CLI at once

Adapters are added one at a time, each backed by captured output from a real installation. An adapter written against imagined output is worse than no adapter.