PM: review cycle 1
Stage line, feature breadth estimate, M1-M3 hours recalibrated x0.1 after cycle C1 (2.5 h agent time for 37 h estimated). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
cea9a0430e
commit
851d438e2a
4 changed files with 21 additions and 18 deletions
21
ROADMAP.md
21
ROADMAP.md
|
|
@ -1,23 +1,23 @@
|
|||
# Lutra Roadmap
|
||||
|
||||
**Stage: pre-alpha (foundation done)** · next: M1 editor and project; alpha when the six core workflows work end to end (see [docs/roadmap.md › Alpha gate](docs/roadmap.md#alpha-gate))
|
||||
**Stage: pre-alpha (M1 in progress)** · next: the rest of M1 (recovery, palette, settings, themes), then M2 syntax and search; alpha when the six core workflows work end to end (see [docs/roadmap.md › Alpha gate](docs/roadmap.md#alpha-gate))
|
||||
|
||||
> **Last reviewed:** 2026-10-14 · **Last updated:** 2026-10-15 · **Change:** minor (tabs and editor in the app) · **Target:** JetBrains PhpStorm 2026.x, described from public documentation only
|
||||
> **Last reviewed:** 2026-10-15 · **Last updated:** 2026-10-15 · **Change:** minor (cycle C1 review: estimates recalibrated) · **Target:** JetBrains PhpStorm 2026.x, described from public documentation only
|
||||
|
||||
Lutra is a clean-room, open-source PHP IDE with a Rust core and a Tauri + Vue interface, targeting the PhpStorm workflow. Agents can drive all of it over MCP, the `lutra` CLI and a JSON control channel. This page is the summary; the evidence is in [`docs/target-app-parity.md`](docs/target-app-parity.md) and the work list in [`docs/gaps.md`](docs/gaps.md).
|
||||
|
||||
**Why pre-alpha:** milestone M0 built the foundation (workspace, quality gate, command registry with panic guard, control channel, an empty themed window), but no PHP feature exists yet. M1–M3 deliver the MVP.
|
||||
**Why pre-alpha:** M0 built the foundation (workspace, quality gate, command registry with panic guard, control channel, a themed window). M1 so far lets you open a folder, browse it in the project tree and edit and save files in tabs, but as plain text: no PHP feature (highlighting, completion, navigation) exists yet. M1–M3 deliver the MVP.
|
||||
|
||||
## Headline numbers
|
||||
|
||||
| | Value | Kind |
|
||||
|---|---|---|
|
||||
| **Feature breadth** (PhpStorm's actions, tool windows, languages, integrations exist) | **0%** | measured |
|
||||
| **Feature breadth** (PhpStorm's actions, tool windows, languages, integrations exist) | **<1%** (project tool window, editor tabs; no inventory to count against yet) | estimated |
|
||||
| **Feature depth** (weighted by use, scored by behaviour) | **~1.4%** (Editor core 8% × weight 12, Project view 8% × weight 6, of 101) | estimated |
|
||||
| **To MVP (M3)** | **~190 h** (M1 ~60 h, M2 ~50 h, M3 ~80 h) | estimated |
|
||||
| **To full parity** | **~3,300 h** (range 2,000–5,000 h) | estimated |
|
||||
| **To MVP (M3)** | **~20 h** (M1 ~6 h of which 2.5 h done, M2 ~5 h, M3 ~8 h); was ~190 h before calibration | estimated (×0.1 from cycle C1) |
|
||||
| **To full parity** | **~330 h** if cycle C1's speed holds (range 300–3,300 h; deep areas such as type inference and inspections have no data yet) | estimated |
|
||||
|
||||
Hours are agent wall-clock hours for one agent. M0 took about 2 h of active agent time (measured from the session, excluding toolchain installation and waiting for owner decisions). Later milestones are estimated far more conservatively per line of code, because editor, language and UI work need integration, debugging and visual checks that the foundation did not. Estimates are recalibrated from merged-commit timestamps after each milestone. PhpStorm is **not** inspected: the clean-room rule in [`AGENTS.md`](AGENTS.md) forbids it, so everything is measured from our code against public documentation.
|
||||
Hours are agent wall-clock hours for one agent. M0 took about 2 h of active agent time (measured from the session, excluding toolchain installation and waiting for owner decisions). Later milestones are estimated far more conservatively per line of code, because editor, language and UI work need integration, debugging and visual checks that the foundation did not. Estimates are recalibrated after each cycle from task start times and commit timestamps. Cycle C1 (M1.1–M1.6) took 2.5 h of agent time for 37 h estimated (factor 0.07); M1–M3 hours are scaled by ×0.1 since then, and the per-area hours below are the raw first estimates (multiply by ~0.1 for the calibrated value). PhpStorm is **not** inspected: the clean-room rule in [`AGENTS.md`](AGENTS.md) forbids it, so everything is measured from our code against public documentation.
|
||||
|
||||
## By dimension
|
||||
|
||||
|
|
@ -68,9 +68,9 @@ All hours estimated. Weights, evidence and the missing items per area: [target-a
|
|||
|
||||
## Upcoming
|
||||
|
||||
1. **M1 editor and project (~60 h):** open folder, project tree, tabs, editor, save and recovery, command palette, settings, themes.
|
||||
2. **M2 syntax and search (~50 h):** highlighting, file structure, find in files, go to file/class/symbol.
|
||||
3. **M3 language server, terminal and CLI (~80 h):** completion, diagnostics, go to definition via Phpactor; terminal; `lutra` CLI and MCP. **MVP.**
|
||||
1. **M1 editor and project (~6 h, 2.5 h done):** open folder, project tree, tabs, editor, save and recovery, command palette, settings, themes.
|
||||
2. **M2 syntax and search (~5 h):** highlighting, file structure, find in files, go to file/class/symbol.
|
||||
3. **M3 language server, terminal and CLI (~8 h):** completion, diagnostics, go to definition via Phpactor; terminal; `lutra` CLI and MCP. **MVP.**
|
||||
4. **Then:** Git (M4), debugger, tests and Composer (M5), own indexer and frameworks (M6).
|
||||
|
||||
## Progress log
|
||||
|
|
@ -86,6 +86,7 @@ All hours estimated. Weights, evidence and the missing items per area: [target-a
|
|||
|
||||
| Date | Change | Summary |
|
||||
|---|---|---|
|
||||
| 2026-10-15 | minor | Cycle C1 review: stage line, breadth estimate, hours recalibrated ×0.1 |
|
||||
| 2026-10-15 | minor | Feature depth ~1.4%: tabs and editor (M1.6) |
|
||||
| 2026-10-15 | minor | Feature depth above 0%: project tree runs against the engine (M1.4) |
|
||||
| 2026-10-14 | minor | M0 done; MVP and parity estimates; stability and agent automation scored |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue