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-4269's headline count was measured with a PROXY predicate — `grep -c 'descriptionFingerprint:'` counts the interface's own field declaration as a tool
- Planning bug: MOTIR-4363 set a 75% heap target without measuring the FIXED share of the cost it was partitioning — and its own criterion 2 forbade the only partition that could have reached it
- Planning bug: MOTIR-4363 enumerated FOUR vitest suites importing into `tests/e2e/`; there are NINE, and every one of the five it missed predates the card
- Planning bug: a card AUDITING a stale count copied the count from the wrong source — MOTIR-3580's "THREE rows behind" was five, and its table's first row was another card's state
- Planning bug: a card's *Measured* block quoted a `grep -c .` of 4 that returns 5 — the count was retyped from a partial read, not run
- Planning bug: MOTIR-4237 chose a UI destination from Motir's OWN surface inventory and never ran rung 1 — its "alternatives weighed and rejected" table listed three existing surfaces and no mirror product
- Planning bug: MOTIR-4193's acceptance criterion defers a decision to "the design pass" that has no card — a prose reference the advisory detector cannot see, and the card sealed ready: true
- Planning bug: MOTIR-3942 planned the conversation's whole CONTRACT and no PRODUCER — the pack, the value and the rules all ship, and nothing runs a conversation
- Planning bug: an interim UI defect card was ready with four visible dispositions and no design prerequisite
- Planning bug: a card's scope-boundary OUT list named the sibling that BUILDS the surface its criteria assert against — and the `blocked_by` edge pointed the other way
- Planning bug: `blocks` does not cross the AI boundary either — MOTIR-4055 enumerates THREE missing link kinds and there are FOUR
- Planning bug: MOTIR-3999 re-combined the publish + the re-pin on one card and omitted the 0.1.3 bump — the exact release-shape MOTIR-3965 was re-scoped out of, one release later
- Planning bug: MOTIR-3932's /explore and /docs scope items have no cards after the host-branch cards were archived
- Planning bug: a bug card counted "the other three inks clear it" over the set its OWN diagnosis had just shown to be unmeasured — the enumeration inherited the guard's blind spot it was filed about
- Planning bug: a re-plan reason that admitted two OPPOSITE readings was acted on without confirmation — an approved plan archived the wrong surface and wrote a false lesson into the corpus
- Planning bug: a reversed direction was recorded as a COMMENT on the decision card it governed, leaving four of its seven criteria demanding the rejected shape
- Planning bug: a card planned a live-run indicator on the READY list, whose membership predicate excludes every item that has a run — and removing it exposed that a run had no general door at all
- Planning bug: a story ACCEPTANCE CRITERION had no child that owns it — MOTIR-3870 pre-dates MOTIR-3891 and was scoped against a different parent
- Planning bug: a story was authored with three children whose acceptance criteria can only be met after the story's own merge and deploy — the container had no exit, and every gating signal read green
- Planning bug: the `AgentRun` collision was RECORDED and not removed — the name shipped into the plan anyway, and a year's drift made it three-way