Roadmap

No dates. Claven is built in evenings and a date would be a promise made with someone else's time. What is here instead is the order, and the condition that ends each milestone — vague milestones never finish.

  1. M1

    It opens filesdone

    Window, file tree, editor, tabs, save, session restore.

    Done when: A real file edit survives on disk.

  2. M2

    Does not look like a demodone

    Syntax highlighting, the brand theme, fonts, find-in-file.

  3. M3

    Language serversdone

    Spawn servers, JSON-RPC framing, diagnostics, completion, hover, go-to-definition.

    Done when: A TypeScript error squiggles without saving.

  4. M4

    Terminalin progress

    A real PTY, and xterm.js in front of it.

  5. M5

    Dogfood and decideplanned

    One week with Claven as the only editor, then read the annoyance log and pick the premise.

  6. M6

    Agent clientplanned

    ACP — the Agent Client Protocol. Premise-neutral, so it can be built before the premise is known.

  7. M7

    The premiseplanned

    Whatever the log turned out to say.

M1 to M4 are identical whichever direction Claven eventually takes, which is why the product question waits until M5 rather than being guessed at now.