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
- (motir-core) THE ROW OPENS IT — a To-approve row's plain primary click opens the overlay in place, and the in-list disclosure it replaces is DELETED with its server action, its lazy subject read and its inventory rowApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) THE OVERLAY HOST — mounted once in the authed shell beside the planning overlay, open state held ONLY in the address, every close through one `requestClose()`, and a SMOKE that opens itApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) GET THE ONE GATE THE OVERLAY RENDERS — a work item's gate, its rendered subject and `canDecide` over HTTP in the 4-layer shape, access-gated server-side, with its permission-inventory rowApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- DECIDE IT FULL SCREEN — an approval opens as an overlay over the page you are on, and the To-approve row's in-list disclosure gives way to itApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- 8.100 (motir-marketing) The design lane measures only the RESTING tree — 20 `:hover` rules across five mocks repaint an ink or a surface, and no guard ever measures the pair they produce
- Planning bug: MOTIR-3933 was sized for the defect its author had REPRODUCED and carried a second one it had only described — 3 points for a one-attribute fix plus a 69-rule isolation problem
- (motir-core) The ORGANISATION tier vacates — the card, the PATCH arm, the service method, the panel's turn-on action, its settings link and its recording copyApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- 8.91 (motir-marketing) The design lane runs ONE of motir-core's eight asset guards, and its one guard is a literal file list — so an asset's addresses, its `.png` and its token layer are unchecked in the repository that now owns the /docs design of record
- (motir-core) The work item page's BREADCRUMB follows placement — led by the effective folder path, and repainted in place when the item's parent or folder changes on the pageFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) Story E2E (Playwright) + ACCEPTANCE VIDEO — a filed item's page shows and changes its folder, and a saved `/items` filter leaves a folder outFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) Story vitest GATE — coverage floor over the placement surface, the file → detail-read → filter seams, and the guards that a filed item stays a ROOT on the roadmap and in the public tree with no folder namesFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) Filter `/items` by FOLDER — the builder's Folder condition row over the project's folder paths, its stale-folder chip, and a saved filter that keeps 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 work item page's FOLDER field — below Parent, filing and un-filing through the shipped picker, reading None / No folder in step with 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 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