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
- verzoeken
- 4
- upvotes
- 415
- gepland
- 4.243
- uitgebracht
- Planning bug: MOTIR-4334 asserted four absences it had greped in ONE repository, and two of them were already satisfied elsewhere
- Planning bug: MOTIR-4516 asserts the `type-*` / `kind-*-author` provenance preambles "sit inside `split.py`-generated headers" — they sit in the BODY, the header holds 2 of 79 keys, and the sentence count is 31 not 16
- Planning bug: a decision rule that A/Bs two configurations across a TIME GAP owes a workload control — MOTIR-3963's pre-committed rule fired REVERT on an 18% suite growth, not on a result
- Planning bug: an `## Advisory dispositions` section discharged gate 4 by naming the BRANCH the substrate sits on — "committed on parent/… " read as "shipped", and the card sealed ready against a 404
- Planning bug: a card asserted the default E2E lane is cloud-on — it is off-cloud, and the whole two-arm plan was built on it
- Planning bug: the loaded corpus narrates its own correction history — 27 struck/CORRECTED blocks and a PROVENANCE key habit make an agent read a change log to find the rule
- Planning bug: MOTIR-4972 and MOTIR-4976 both cite substrate that is not there — a criterion asking to UPDATE assertions that never existed, and two paragraph quotes taken from the sibling repository's file
- Planning bug: a card's "Root cause — VERIFIED" was falsified by a comment in the very file it cites, written by the very card it cites as precedent
- Planning bug: MOTIR-4746 diagnosed a guard whose FILE SET was too narrow, and enumerated its own population with a command just as narrow — 3 unswept citing files where 7 stood at the card's own base ref
- Planning bug: MOTIR-4736 enumerated the other `plan` submits from memory — it named two services that submit `noop` and `discovery`, and missed both real sites
- Planning bug: an acceptance criterion quoted a rule sentence it had re-worded, and named a guard that does not exist — both in a card whose own body demanded the verbatim text
- Planning bug: MOTIR-4570 named `applyDelta` as "the single writer every kind goes through" — it has two callers, both positive, so the offset placed there would have been dead code
- Planning bug: MOTIR-4263's criterion 3 asks for the edit its own filer's branch had just decided AGAINST — performing it turns the guard RED, by name
- Planning bug: a later merge deleted every test subject while the lane-fix work item stayed ready
- Planning bug: a rung-2 "verified from shipped reality" claim read the CHILD component and missed the parent — MOTIR-1764 asserted an ephemeral dismissal that actually persists in localStorage
- Planning bug: MOTIR-4538 measured "no upstream Go/React source is modified" over FIVE directories where the claim quantifies over the whole upstream tree, and split its 37 into 22/15 with no command behind the split
- Planning bug: MOTIR-4578's AC 4 named the VITEST lane for a layout assertion happy-dom cannot make — the guard it asked for would have been green on the unfixed component
- Planning bug: MOTIR-4507 says the /docs index lists EIGHT destinations — it lists seven, and its own table enumerates seven
- Planning bug: MOTIR-4422 encoded the mechanism it existed to re-measure as an acceptance criterion, and named three of five carriers
- Planning bug: MOTIR-4412's "all 111 `MOTIR-\d+` hits in the loadable packs" counted the loadable packs PLUS the unloaded CORPUS-MAINTENANCE.md — the loadable figure at its own ref is 55