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
- 5
- suggestions
- 4
- votes
- 404
- planifiés
- 4 190
- livrés
- Planning bug: a cited BASELINE was inherited across the change that invalidated it — MOTIR-5028's 40.9-min "cold floor" is a `projectsIndexed: 2` run from before the fan-out was retired, and MOTIR-5031's whole deliverable rests on the same figure
- Planning bug: a card was authored against a `/docs` route deleted five days earlier — and the criterion that asserted it was INTRODUCED by an advisory disposition, replacing a true post-merge clause with a false in-PR one
- Planning bug: MOTIR-4944's highest-prior row asserted three assets "draw an icon slot with no icon slot rules" — all three declare `svg { width: 1em; height: 1em }`
- Planning bug: a card named two assets as a CLASS ("both are compiled builds") and proposed a fingerprint for it — one grep falsified both halves
- Planning bug: MOTIR-4430 priced a `headers()` read in `app/not-found.tsx` as one route's prerender, and asked for two properties of motir.co's 404 room that cannot both hold
- Planning bug: MOTIR-4316's first acceptance criterion greps for a string JSX line-wraps, so it returned nothing on the UNFIXED tree and could not fail
- Planning bug: MOTIR-4317 named the assertion its own guard cannot produce — a PASSING pair yields no finding to read a value off, and its before/after count was blind to the 146 grounds the fix moved
- Planning bug: a per-repo test gate was cut as TWINS and the motir-core half's coverage clause rode into the motir-ai one, where no coverage gate exists
- Planning bug: a criterion named a consumer that was PRESENT but UNREACHABLE — `situations/replan.ts`'s partition had been dead since MOTIR-3978
- Planning bug: a row inventory over a prettier-wrapped HTML design asset was taken with a line-oriented grep, so MOTIR-4248's evidence table under-read one asset by two rows
- Planning bug: a card enumerated a tool schema's MISSING fields without the command that produced the list, and named one the schema already had
- Planning bug: a card told a second repository to MIRROR a mechanism the first repository retired nineteen hours later — "mirror X" is a claim about another repo's current shape, and nothing re-checks it
- Planning bug: the WHAT's PRODUCER and CONSUMER disagree on its SHAPE — MOTIR-4083 pins it to prose `text`, MOTIR-4082 consumes a validated struct, and nothing converts one to the other
- Planning bug: MOTIR-4130 counted 3 of the 6 rows its claim quantifies over, and denied on the record the one edge it owed — to the OPEN PR that changes the row the card is named after
- Planning bug: a card read an element's specified measure off an UNAPPLIED rule in the mock's stylesheet, and called it "the value the asset draws"
- Planning bug: a card declared the WHAT out of scope on the ladder's HOW argument, and addressed its start-gate to the phase being gated
- Planning bug: a card specified ONE rule delivered to two packs with identical text — which `INVARIANT B — disjoint cover` forbids, and the 88-char segment id collides on
- Planning bug: MOTIR-4106 pinned motir-core owed a row in docs/contract.md, which is a motir-ai file — a repo straddle the BARE path hid from the detector
- Planning bug: a card asserted the release re-runs the PR's matrix without reading the lanes' own `if:` — the most expensive one had been PR-exempt for nine days
- Planning bug: MOTIR-3868's AC 1 required a diff against `work_item.targetRepoRole`, a column retired 11 days earlier — the enumeration was verified, the column behind it was not