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 MERGES the pull request — the `GitProvider` merge seam, the App the repository's PROVENANCE decides, and the queue when the repository has oneApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- Planning bug: MOTIR-4882's lay proposed contracts four sibling cards already contradicted — the planner searched for duplicates and never read the sibling stories' subtasks
- (motir-core) Design — `/items` for a project that holds only FOLDERS and no work items: the first-run empty state beside the seeded Bugs folderProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core · design) THE STATUS CONTROL SAYS SO — a message on the control while an approval holds a move, a Review & approve button straight into the full-screen overlay, the held option in the dropdown, and the reader who may only lookApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Design AMENDMENT — the Bugs room picks a FOLDER: the folder path, the shipped folder picker, and Project root as a named choiceProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) Story vitest gate — the SQL the generated client actually EMITS for every select-less `Workspace` read names no `subtaskPrMergeMode` while the column still exists, and the coverage floorApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) PHASE 2 — `@ignore` `Workspace.subtaskPrMergeMode` so the generated client stops selecting it; the column stays and no migration shipsApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- Retire `Workspace.subtaskPrMergeMode`, PHASE 2 — the generated client stops selecting the column and RELEASES with it still in place; the deploy check and the drop sit BESIDE this storyApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- Folders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) Canvas card titles never clamp — `line-clamp-N` beside `block` loses to `display: block`, so a long title spills past its line budget on plan / roadmap nodes
- 36 (motir-meta) The `motir-plan` walk never moves its target to `planning` — `create_plan` takes no lock and the runbook never opens a plan session, so the card stays pickable while it is being re-planned
- 37 (motir-meta) The `motir-log-bug` door files PLANNING bugs — its read-set item 4 routes any bug "about the PLANNER" to `run.md`'s MOTIR-1465 home, so a skill or runbook defect with no wrong card is logged as a planning bug
- (motir-core) PHASE 2 — `@ignore` `Organization.acceptanceVideoEnabled` so the generated client stops selecting it, and RELEASE with the column still in placeApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Approve MATERIALIZES folder placements — an `add` created filed, a `modify` re-parent that clears the other placement, and a folder deleted since the append refusing the approve by nameFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-ai) Story vitest GATE — coverage floor over the folder-aware tree reads and proposal executors, and the seam from a grounded folder set through `propose_node` to the `plan-proposals` payloadFolders — 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 — an integration files work into a folder over `/api/v1`, an agent proposes a card into a folder over the MCP, and a reviewer sees the folder on the plan and approves it into `/items`Folders — 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 folder API, MCP and proposal surface, the service → route → tool → materialize seams, and the guards that every folder code is mapped and every folder tool is documentedFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-ai) `SHARED_PLANNING_RULES` name a folder as a PLACEMENT, not a parent kind — THE MOTIR GRAMMAR and the reconcile rule, with the conservation, routing and register baselines holdingFolders — 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 plan review SHOWS where a card will be filed — folder crumbs on the canvas and the list, a move into or out of a folder under Show changes, and the stale-folder stateFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-meta) The runbook names folders as a place work is filed — `plan-procedure.md`'s ladder, `_shared.md`'s `move_to_parent` and proposal-`parentRef` notes, and `log-bug.md`'s forward ladder, beside the shipped planner's grammarFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own