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
- prośby
- 4
- głosy
- 392
- zaplanowane
- 4214
- wydane
- (motir-core) The board and the list REFUSE IN PLACE — a refused drag or inline status edit shows the pending-decision refusal where it happened, with the door, instead of the snap-back toast (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The item page, quick view and edit page SAY SO ON THE STATUS CONTROL — "Status can't be moved to {status} directly" with a Review & approve button into the overlay, and the held option in the dropdown (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) PULLING THE WORK BACK WITHDRAWS THE QUESTION — a hand move out of review, or to Cancelled, supersedes the item's `awaiting` gates in the funnel's own transaction, taking the gate lock in the decide door's orderApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) THE GUARD — `applyStatusTransition` refuses the transition an `awaiting` gate owns, read from the registry, with the decide door's own write exempt, and `APPROVAL_GATE_PENDING` answers identically on every doorApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) AMEND `approval-gates.md` §6d — the manual-flip GUARD: the transition a gate owns, `awaiting` as the key, the decide door's own write exempt, and a hand move that pulls the work back WITHDRAWS the questionApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core · design) THE ITEM PAGE HANDS IT OVER — the gate section becomes a call-to-action band with ONE control, the three states the page KEEPS, and the no-gate case stated as unchangedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core · design) The approve-and-merge verbs and their states — Panel 12c's band 3 through press, merging or queued, one PR refused, withdrawn by a push, and the To-approve rowApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core · design) THE APPROVALS ROOM, drawn — its two scopes, the pending-then-decided order, the row it COMPOSES rather than redraws, the four states' words, and its ENTRANCE in the project railApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) A design card with an open linked pull request raises no `design_result` gate — the publish reads the delivery set, and linking a pull request supersedes an awaiting design gateApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Decision — AMENDMENT 4 gains Q8: a design card with an open linked pull request shows its result INSIDE the Development block, raises no `design_result` gate, and is decided by the approve-to-merge gateApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- Story-level E2E (Playwright) + ACCEPTANCE VIDEO — publish a mock and its note, review it on the card and in the approval overlay, and watch a screenshot and a non-gating publish refusedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- Story-level vitest gate (motir-core) — the coverage floor over the story's changed surface, the publish → panel seam, the gating refusal against real edges, and the two-file guard's fixture casesApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The design result renders WHAT TO REVIEW — mock frame(s) with the note as a link, older results as file links — and inside the Development block, with the PR rows and How to test, when the card has open linked pull requestsApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-ai) `THE_DESIGN_GATE` in `SHARED_PLANNING_RULES` stops requiring the `.png` and gains the delta-mock and publish-only-when-work-waits clauses — the shipped planner's twin of the pack editApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (starter) `design/README.md` and the README's design section describe the two-file set, the delta mock, the note published as a link, and publishing only when work waits on the designApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The design dispatch prompt — two files, a change drawn as a new delta mock, and the PUBLISH step only when the server finds an open work item `blocked_by` the cardApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Design — the design result as WHAT TO REVIEW: the mock frame(s), the note as a link, older results as file links — and on a card with linked pull requests, INSIDE the Development block with the PR rows and How to test, one sectionApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-marketing) Its design convention and `designThreeFileSet` guard stop requiring the `.png` — the two-file set and the delta-mock rule, in this repository's own copyApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-meta) The runbook and the plan-rules packs teach the new design result — two files, a delta mock for a change, and publish only when an open work item is `blocked_by` the designApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The publish contract — `publish_design_result` and the design-evidence routes refuse an `image`, a `noteMd`, a result without a mock and its note file, and a publish to a design card no open work item is `blocked_by`Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join