moooon
Motir
Vibe the project. Bring an idea — Motir's three AI layers plan it, track it, and ship it, end to end. You're looking at Motir, built in Motir.
- Vibe Project
- Open Source
- AI Agent
- AI Loop
- 6
- requests
- 4
- upvotes
- 597
- planned
- 5,376
- shipped
- Planning bug: MOTIR-4906's re-plan drew HOW TO TEST as a separate section instead of the evidence inside the ONE approve-to-merge gate — it never read how Design result renders through the frame
- Planning bug: MOTIR-5180 enumerated ONE `subtask_pr_merge_mode` citation in `prompts/` while five existed — its grep criterion and its "no other file" boundary could not both hold
- Planning bug: MOTIR-5316 was re-authored by a re-plan without re-running its preconditions — the quick view has no folder, filing returns no token, and no quick-view → tree channel exists
- Planning bug: MOTIR-5315 was sized 5 pt / 65 min for the whole folder-action surface before its design existed — the merged design's GIVES list is five cards and two unowned reads
- Planner sized a UI card before its design AND before its backend fixed the interaction model — MOTIR-5262 outgrew 5 pts once MOTIR-5260's grant-then-bind flow was drawn
- Planning bug: MOTIR-4592's hard gate B was authored against a lane margin and a period revenue that do not exist — no edge to the blocked calibration that owns them
- Planning bug: two runs wrote obligations for MOTIR-5193 into PROSE — a design § naming a consequence "not in its criteria", an inventory row naming its GET gate — and neither edited the card's criteria or its size
- Planning bug: MOTIR-5199 recorded an exit code for all nine guards and never asked whether a RUNNER could obtain their inputs — two read a private sibling repo
- Planning bug: two sibling cards CONTRADICTED each other on paging, because one cited a RETIRED convention by a path that no longer exists
- Planning bug: a story's own run STRUCK a row of its audit table and cancelled the card that implemented it, but did not sweep the VERIFICATION card whose readings quote that row — three of MOTIR-4665's seven readings name a route the same story decided never to build
- Planning bug: MOTIR-5106 sized its sweep on a count taken with a LOOSER predicate than the claim it supported — "30+ files drive both verbs" measured files that MENTION both; 7 actually drive both, and none needed changing
- Planning bug: a remedy card wrote "which the service STORES" about a value the service only VALIDATES — the normalisation of a logged field reads exactly like a write path
- Planning bug: MOTIR-5117 named an UNOBSERVED mechanism as its root cause — a job named for a measurement was read as having failed THAT measurement, while its own log named no threshold and a control run was green
- Planning bug: MOTIR-5057's recommendation rests on "ZERO were `getByTestId`" — the record says TWO, and both are the deploy-blocking `highest` incidents
- Planning bug: a card's "the record gains a paragraph" step cited a DOC SECTION that does not exist, and its consumer enumeration was short by two — both falsifiable by one grep at authoring time
- Planning bug: a three-repo MIRROR card was wired to the card that renamed the STORE, not to the card that widens the TOOL its reader calls — and the dependency it did state was prose in an acceptance criterion, so it sealed `ready: true`
- Planning bug: a card citing its blockers as a PHRASE ("the four member packs") got two of four `blocked_by` edges, and no channel could see the gap
- Planning bug: MOTIR-4774 reasoned that renaming the lesson axis leaves "a collision between a tool and nothing" — the new values ARE the two tool names, a shipped guard refuses them, and the card also cited a `contract.md` section that does not exist and undercounted its own sweep 13 → 4
- Planning bug: MOTIR-5032 specified the port's render signal as the iframe `load`/`error` events, which the file it cites in its own Context refs deliberately rejects — and named a `pnpm design:guards` script that does not exist
- Planning bug: `core.md` routes gates 4 and 20 to "`phase-author.md`, THE ESTIMATION GATE" — that section does not exist in the pack