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
- solicitudes
- 4
- votos
- 414
- planificados
- 4220
- publicados
- (motir-core) The FOLDER filter field — `folder` in the registry and FilterAST, compiled on the effective folder with sub-folders, stale folder ids resolved, and `search_work_items` naming itFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) The item page READS its placement — `IssueDetailDto.folderPath` for the item's EFFECTIVE folder (its own, else its root ancestor's), and one placement re-read the page asks after a moveFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- Every other surface places a filed work item correctly — its page's parent and breadcrumb, the roadmap, the public project and the filters all read a folder parentFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) The top bar's context path OVERFLOWS at `xl` on a cloud build — the right cluster paints over the project switcher, which becomes unclickable
- 8.98 (motir-core) The `coverage` advisory does not reach a PROJECTED `validate_work_item` — a plan that re-parents existing cards under a proposed container is where criteria go unowned, and `planId` reports nothing
- Planning bug: a defect card counted its affected routes with a file-local absence grep that cannot see an IMPORTED error mapper — "13 routes 500" was 4 × 500 + 9 × 403
- Planning bug: a decision REVERSED at a design review was recorded on the reviewed card only — the old decision's MERGED implementation and two follow-ups kept the rejected shape until a run hit it
- Planning bug: MOTIR-4906's re-plan drew HOW TO TEST as a separate section instead of the evidence inside the ONE approve-to-merge gate — it never read how Design result renders through the frame
- Planning bug: MOTIR-5180 enumerated ONE `subtask_pr_merge_mode` citation in `prompts/` while five existed — its grep criterion and its "no other file" boundary could not both hold
- Planning bug: MOTIR-5316 was re-authored by a re-plan without re-running its preconditions — the quick view has no folder, filing returns no token, and no quick-view → tree channel exists
- Planning bug: MOTIR-5315 was sized 5 pt / 65 min for the whole folder-action surface before its design existed — the merged design's GIVES list is five cards and two unowned reads
- Planner sized a UI card before its design AND before its backend fixed the interaction model — MOTIR-5262 outgrew 5 pts once MOTIR-5260's grant-then-bind flow was drawn
- Planning bug: MOTIR-4592's hard gate B was authored against a lane margin and a period revenue that do not exist — no edge to the blocked calibration that owns them
- Planning bug: two runs wrote obligations for MOTIR-5193 into PROSE — a design § naming a consequence "not in its criteria", an inventory row naming its GET gate — and neither edited the card's criteria or its size
- Planning bug: MOTIR-5199 recorded an exit code for all nine guards and never asked whether a RUNNER could obtain their inputs — two read a private sibling repo
- Planning bug: two sibling cards CONTRADICTED each other on paging, because one cited a RETIRED convention by a path that no longer exists
- Planning bug: a story's own run STRUCK a row of its audit table and cancelled the card that implemented it, but did not sweep the VERIFICATION card whose readings quote that row — three of MOTIR-4665's seven readings name a route the same story decided never to build
- Planning bug: MOTIR-5106 sized its sweep on a count taken with a LOOSER predicate than the claim it supported — "30+ files drive both verbs" measured files that MENTION both; 7 actually drive both, and none needed changing
- Planning bug: a remedy card wrote "which the service STORES" about a value the service only VALIDATES — the normalisation of a logged field reads exactly like a write path
- Planning bug: MOTIR-5117 named an UNOBSERVED mechanism as its root cause — a job named for a measurement was read as having failed THAT measurement, while its own log named no threshold and a control run was green