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
- 520
- planned
- 5,600
- shipped
- Capture a merged PR's changed file paths and its merge instant — the substrate a subsumption check needs, and the one `github_pull_request` does not carry
- Planning bug: a flake card named its MECHANISM in the title and enumerated the two allowed repairs — the first measurement falsified both
- Planning bug: `COMPRESSION.conserve.py` cannot express "a gate gained a sub-bullet" — the enumeration's COUNT NUMERAL is surviving text, so every future limb re-words it
- The credit top-up bundle SELECTOR is decorative — the 1× / 5× / 10× choice never leaves the browser, so the "$100 · 10 000 credits" button would charge $10 for 1 000
- Planning bug: `motir run <id>` has NO claim, so two sessions built MOTIR-2952 at once — and the tell was a `git status`, not anything the MCP said
- (nextjs-prisma-vercel-starter) The vendored acceptance uploader ACTION cannot LOAD — `${{ }}` inside its input `description`s fails GitHub's manifest validation, so the publish step errors on every acceptance-spec PR
- `bareTransactionScan` cannot see `bindWorkspaceContext`, so the blessed mid-block bind reads as UNBOUND — and the guard's own instructions push you to record a false verdict
- Planning bug: an ADR run swept OUTWARD for what it left unowned and never INWARD for the criteria it had just falsified — including the card its own header names first
- Every ratchet constant in `tests/rls/` is measured on a BRANCH, so a sibling merging underneath makes it stale — decide the mechanism once, before the second instance
- Planning bug: a card described a SESSION LIFECYCLE the shipped model does not have — and two of its release paths would have defeated the lock
- The two credential flows land on two different pages — sign-UP still defaults to `/dashboard` while sign-IN defaults to `/home`, and both surfaces still document `/dashboard` as where both land
- Planning bug: a card quoted the exact line it was changing and called it unexplained — the twelve-line comment directly above it said the opposite
- Planning bug: 8.1.5 shipped a checkout endpoint that could never work, because the deferral was written into a CODE COMMENT ("EITHER … OR …") instead of a card — the orphaned-deferral shape, on the revenue path
- `POST /v1/stripe/checkout-session` can NEVER create a session — motir-core sends a price LOOKUP KEY, motir-ai passes it straight into `line_items[].price`, and every catalog key 404s `No such price`
- Planning bug: the correction was posted as a COMMENT and the description kept the false claim — second instance, and both times the run that wrote the comment also wrote the card that asserted it was applied
- Planning bug: MOTIR-2939 attributed a count rise to two specs from what LANDED RECENTLY, not from measuring — one of the two was already inside the baseline
- Planning bug: an acceptance criterion asserted a PIPELINE's outcome ("the PR is green") when the card owned one STAGE of it — the other stages were never verified
- `main` is RED — MOTIR-2918 landed `UNCONVERTED_E2E_CEILING = 454` against a tree that already measured 457, so the ratchet it added fails on its own merge commit
- Planning bug: MOTIR-2919 called MOTIR-2911's conversions "landed" two minutes before their PR existed, and wired the edge `relates_to` — its "0 failures" criterion is unreachable from `origin/main`
- Planning bug: a decision forbade every in-product path that could write the column it governs, and no card owned the one path left — a dev-only seed criterion made it look owned