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
- 544
- planned
- 5,441
- shipped
- Planning bug: a card's "Root cause — VERIFIED" was falsified by a comment in the very file it cites, written by the very card it cites as precedent
- Planning bug: MOTIR-4746 diagnosed a guard whose FILE SET was too narrow, and enumerated its own population with a command just as narrow — 3 unswept citing files where 7 stood at the card's own base ref
- Planning bug: MOTIR-4736 enumerated the other `plan` submits from memory — it named two services that submit `noop` and `discovery`, and missed both real sites
- Planning bug: an acceptance criterion quoted a rule sentence it had re-worded, and named a guard that does not exist — both in a card whose own body demanded the verbatim text
- Planning bug: MOTIR-4570 named `applyDelta` as "the single writer every kind goes through" — it has two callers, both positive, so the offset placed there would have been dead code
- Planning bug: MOTIR-4263's criterion 3 asks for the edit its own filer's branch had just decided AGAINST — performing it turns the guard RED, by name
- Planning bug: a later merge deleted every test subject while the lane-fix work item stayed ready
- Planning bug: a rung-2 "verified from shipped reality" claim read the CHILD component and missed the parent — MOTIR-1764 asserted an ephemeral dismissal that actually persists in localStorage
- Planning bug: MOTIR-4538 measured "no upstream Go/React source is modified" over FIVE directories where the claim quantifies over the whole upstream tree, and split its 37 into 22/15 with no command behind the split
- Planning bug: MOTIR-4578's AC 4 named the VITEST lane for a layout assertion happy-dom cannot make — the guard it asked for would have been green on the unfixed component
- Planning bug: MOTIR-4507 says the /docs index lists EIGHT destinations — it lists seven, and its own table enumerates seven
- Planning bug: MOTIR-4422 encoded the mechanism it existed to re-measure as an acceptance criterion, and named three of five carriers
- Planning bug: MOTIR-4412's "all 111 `MOTIR-\d+` hits in the loadable packs" counted the loadable packs PLUS the unloaded CORPUS-MAINTENANCE.md — the loadable figure at its own ref is 55
- Planning bug: MOTIR-4402's criterion 2 cites a guard that does not exist — `landing-owner-guard` scans `/home` and `/dashboard` only, so "already fails on one" is false for `/onboarding`
- Planning bug: MOTIR-3947 was carved out of MOTIR-3933 and inherited two unverified claims — a consumer that does not exist in that form, and a figure one tile optimistic
- Planning bug: MOTIR-4343 was authored with an acceptance criterion editing a test file that exists only on an open PR, and no `blocked_by` edge — it sealed `ready: true`
- Planning bug: MOTIR-4295 mis-diagnosed its own top cost site (the remedy it prescribed was already in place), and its "top ten" shape cannot reach an order-dependent cost
- Planning bug: MOTIR-4298 was sealed with an EMPTY blocked_by while two of its four criteria read on a sibling container's unmerged output, and pinned ONE repository while its own body pins a two-repository contract
- Planning bug: MOTIR-4165 counted the catalogue at 39 by reading a number out of a comment, and generalised a four-tool sample to "one tool"
- Planning bug: MOTIR-4079 asked motir-ai's gate to assert core's READINESS verdict "through the shipped read" — motir-ai's lanes fake core by construction, so the verdict can only be asserted in motir-core