roadmap

ROADMAP protocol (hi-claude)

docs/ROADMAP.md is the single register of what is MISSING. docs/ESTADO.md (STATE.md in English projects) is the live picture of what EXISTS. Neither keeps a log.

The nine rules

1. An item is DELETED when it reaches 100% — never marked done. If closing it changed the state of the system, that goes in-place into ESTADO.md. The design of what was built lives in the work itself and in the commits, not in a list of trophies.
2. The progress line is ONE line, rewritten, never stacked. Ya resuelto: / Resolved: carries what is already standing, so a session that arrives cold does not redo it. Past two lines, the item was several items: split it.
3. The open-work block holds at most 3 items, between the hi-claude:en-curso markers. That block is injected at every session start and is what answers "what were we doing". More than three and it stops being an answer.
4. Closing route: unmarked = [C], closable by a work session on its own. Mark only what a session cannot close alone — [V] needs the real world · [O] needs a window, access or coordination · [D] needs the user's GO · [B] needs a dedicated measuring session. Marking only what saves time is the whole point of marking.
5. (Done: …) is runnable when the item admits one — a grep that must return 0, a test that fails before and passes after, a command that must exit 0, a URL that must respond. Turning the criterion into something runnable is the FIRST move when taking an item. If it cannot be made runnable, that is information about the item: it is probably [V], not [C].
6. Timeless. No dates, no "today", no "this session". hi-claude:work-protocol governs how every line is written — same rules as any other document.
7. HUBS first, classes not bullets. An item that unblocks others goes first. Twenty defects sharing one root cause are ONE job with one rule that closes them all; taking them one by one fixes the same thing three times.
8. Work that is not for now lives in the HORIZON of its thematic block, under a Horizonte / Horizon heading, and it carries the CONDITION that brings it in — not a date, the thing that has to become true. It stays in the same file: migrating is moving a block, and a second file is a second place where something can expire unseen. The horizon does not ride into the session, so it costs nothing at startup and it is not a place to hide work that already started.
9. The register is written so a PIECE can check it, and what that piece cannot read is a defect of the ITEM. Three invariants, none of them tied to a language: the runnable forms live in the piece and never in the item · what it cannot measure comes back as a THIRD state, never as "open" · and the count of criteria it cannot read is a ceiling that only goes DOWN. references/roadmap-anatomy.md carries the contract and what it costs.