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
- 547
- planned
- 5,443
- shipped
- 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
- Planning bug: a design amendment settled "nothing else branches" from a RENDERED fixture whose fields cannot co-occur — `tier: null` beside `balance: -4210`, on the org whose tier the debit itself assigns
- Planning bug: a card NAMED its own missing design in prose — "a design ruling is likely owed before the fix ships" — and sealed `ready: true` with no design blocker. A gate is an EDGE, not a sentence.
- Planning bug: a card's context ref named `ProposalRecord.blockedByRefs` as substrate to READ, and the field has never existed — a proposal's `blocked_by` set is dropped at the registry
- Planning bug: MOTIR-4258 asserted every action on the row survived elsewhere, and wrote an acceptance criterion requiring a door it never checked existed — the ⋯'s Expand / Re-plan had none
- Planning bug: MOTIR-4206's Q7 cited Atlassian's rename cap as 3; the documented figure on the cited page is 15
- Planning bug: the 8.3 re-plan moved the public marketing surface to motir.co and never swept MOTIR-1043, whose whole premise was that surface — it kept `(motir-core)` in its title, and had no design blocker, for two months
- 2200.12 (motir-core) Repository reads still key on the RETIRED workspace tier — the project link is an isolation boundary and the workspace rung leaks past it