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-5015's first half was ALREADY SHIPPED — the card's precondition check read the surface it was fixing, never the seam it was specifying
- Planning bug: MOTIR-5009 was sealed with two POST-DEPLOY criteria behind an operator config flip, sized as one code card — gate 14's ORDERING limb, its release TRIO and type-runtime's WIRING limb all exist and none was run
- Planning bug: two cards assert a refusal NOTE that no code path posts — the claim was derived from an outcome name and propagated card-to-card without a read
- Planning bug: a card's "what the code does today" section was written from a FUNCTION and not from its CALL SITES — `openPrEagerly` reads as unconditional in the file, and the premise it produced understated the card by a whole lane
- Planning bug: amending an ADR and adding the stories it implies swept neither the DESIGN card nor the CODE card that draw the superseded model — the second such miss on the same card
- Planning bug: a precondition LIFTED to a parent edge for legality is blind to the child being archived — add the lesson, and the rule that a `blocked_by` must name what is actually depended on
- Planning bug: a correction was authored on a FALSE ABSENCE — one grep for the phrasing that was seen concluded "neither home carries the clause" when both carry it, TOTAL
- Planning bug: sweep the MOTIR-4642 tree for preconditions cited as prose `motir-ref:` links — the shape the `reference` advisory is blind to by construction
- Planning bug: MOTIR-4959's criteria 1 and 6 CONTRADICT — a card that moves code out of a file, and requires the 27 assertions reading that file for the moved text to pass "untouched"
- Planning bug: MOTIR-4956 was filed UNPINNABLE and UNAUTHORED — no `targetRepo` while its own fix direction named files in two repositories, no criteria, no sizing, and an open defect recorded as prose; it still sealed `ready: true` / `valid: true`
- Planning bug: a feature was planned by which SURFACE it resembles, so a gate-shaped capability was filed as a settings relocation and never reached the epic that exists for it
- Planning bug: a card quoted shipped UI copy from MEMORY and used the quotation as its rung-2 argument against one of its own fix shapes
- Planning bug: a card that REMOVES a state enumerated the state's CONSUMERS and closed only the PRODUCER where it was noticed, so its criteria deleted the answer for the two producers it never looked for
- Planning bug: two cards filed against ONE contradiction resolved it in OPPOSITE directions, wired only `relates_to` — both read `ready`, and the second to run built on the first's deleted premise
- Planning bug: a surface EXEMPT from the tier-hiding rule was planned around as an exception instead of read as a missing fold-in — so the plan defended a workspace row inside the PROJECT rail
- Planning bug: two sibling design cards were laid as INDEPENDENT while one's acceptance criteria cite the other's file by PATH — in a repo whose design lane enforces that cited paths resolve
- Planning bug: a gate was planned onto a session that had neither the TOOL nor the FACTS — and its citation resolved, because the shipped code preserves the struck reasoning
- Planning bug: a control surface was copied from a comparable of a DIFFERENT product kind, and one axis was copied in a shape that comparable does not use — the residency switch promised EU and resolved to two US providers
- Planning bug: MOTIR-4408's population was measured with a command narrower than its own claim — five of eight members were invisible to it, three of them predating the card
- Planning bug: two cards for one race, filed 12h apart with mutually exclusive remedies on the same four lines — gate 8 sweeps who CLAIMS a deliverable, never who has declared it OFF-LIMITS