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
- 要望
- 4
- 賛成票
- 409
- 計画済み
- 4,254
- リリース済み
- 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
- Planning bug: a ratchet number was attached to a counter that measures a SUBSET of the population the card's own reason quantifies over
- Planning bug: MOTIR-4017 asserted two facts about the plan detail that the render falsified — a scroll that does not happen, and an arrival floor this surface cannot reach
- (motir-core) `claim_next_ready` claims WITHOUT assigning — the one dispatch door that leaves a card In Progress with no owner
- Planning bug: a card cited an existing guard's debt table by its NAME and not its PREDICATE — the decrement it ordered was arithmetically impossible and would have turned the guard red
- Planning bug: a `blocked_by` wired to an ARCHIVED predecessor gates nothing — the card sealed `ready: true` against a retirement that has not shipped, and the advisory that named it was never read
- Planning bug: a card specified a JUDGEMENT and never checked what its own call carried — ten acceptance criteria passed over a prompt asking a model to weigh evidence the request did not send
- Planning bug: MOTIR-4375 was sealed at 13pts/240min across two repos with a fix-mechanism nobody verified — gate 2 is run on what a card CONSUMES, never on the remedy it PRESCRIBES
- (motir-core) Design — the UNIVERSAL APPROVAL FRAME: a port that renders what is being decided, with Approve · Request changes below it, in every stateApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- 2200.6 (motir-core) MEASURED — the health-check alert IS delivered and read; the gap is that no delivered alert creates an OBLIGATION, and two have sat unacknowledged for 4 and 11 days
- Planning bug: `run.md`'s parent-run PR lifecycle is wrong and its CLI table is stale — adopt the DECIDED lifecycle (draft at the first child, ready at the last, linked to the story)
- Planning bug: MOTIR-4964 was sealed with NO acceptance criteria — by the same pass that had filed MOTIR-4958 about a card with no acceptance criteria, 95 minutes earlier
- Planning bug: MOTIR-4902 asserts a `callPage()` site "never awaits it" — the site has released and awaited since before MOTIR-4898, and one `git show` falsifies it
- Planning bug: a card EXCLUDED a `blocked_by` on a container claim it never read — the two cards are siblings under one epic, and the exclusion is what let it seal `ready: true` with all three deliverable files held by an open PR