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
- solicitações
- 4
- votos
- 392
- planejadas
- 4.208
- entregues
- (motir-core) RAISE and WITHDRAW merge gates — one awaiting pull_request_merge per green pull request on the run target in a manual project, superseded when its head moves or its link goesApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) `GitProvider.mergeChangeRequest` — the seam method and GitHub's merge, normalized to merged or a typed refusalApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The approval frame's SETTINGS DOOR — a kind-supplied link to the project's merge-mode setting, rendered only for a viewer holding workflow:manageApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The MERGE refusals render in ApprovalGateControl — five new members of the refusal union, each with next-action copy (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The GitHub App chosen by repository PROVENANCE — a hosted repository mints through motir-studio, an imported one through motir-integrationApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) AMEND approval-gates.md §4 for the MERGE gate — one per pull request on the run target, raised on green, merge-or-enqueue outcome, the refusal union, and what an auto merge recordsApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Register `pull_request_merge` — the handler over one pull request, the `work_item:merge_pull_request` permission, and the kind's settings doorApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- 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