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
- 500
- planned
- 5,029
- shipped
- (motir-core) A ROW'S TITLE OPENS THE QUICK VIEW — the work item's title in the sentence becomes the `?peek=` door on To approve and in the Approvals room, and the rest of the row still opens the approvalApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) THE OVERLAY KEEPS YOU IN PLACE — its title opens the work item's quick view stacked above it, and every Open work item opens a new tabApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) THE ROW READS AS A SENTENCE — `ApprovalRow` frames each kind around the work item's title ("Design for X", "Acceptance video for story X", "X is finished"), with no host vocabulary, in both lists and the user doc (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) EVERY approval on one tab — `listAwaitingMe` reads the whole awaiting set under a stated ceiling, and the To-approve list drops its pagerApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- TO APPROVE SAYS WHAT IS WAITING IN PLAIN WORDS — "Design for X", "X is finished", never "pull request" — lists every approval with no pager, and a title opens the work item's quick view, over the full-screen approval tooApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- VERIFY on app.motir.co that the evidence sweep reached the pre-enrichment bugs — MOTIR-5865 shows its exception and in-app frames on the page and over `get_work_item`, and its body was authored by `author_bug`Production errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- MotirIntegrationDemoError: Demo error for the Motir integration publication review (MOTIR-6004) — safe to resolve
- Connecting Sentry throws away a successful grant when a follow-up call is slow — `completeGrant` spends the one-time code, then a 5 s verify/describe timeout discards the tokens and leaves Sentry holding an install Motir has no credential forProduction 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 ROW AS A SENTENCE and THE TITLE AS A DOOR — a delta of the To-approve row per kind ("Design for X", "X is finished", no pager) and of the overlay's exit row (the title opens the quick view above it, Open work item opens a new tab)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-ai) Story VITEST gate — the coverage floor over the rule and the carve-out, a re-plan of each shape through the same path, a first plan refused the card, and the epic's body never patchedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Playwright E2E + ACCEPTANCE VIDEO — a decision confirmed, one overturned with its note, one confirmed with no record, a defective body, and a read-only viewer who sees no controlsApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Story VITEST gate — the coverage floor, the body → parse → raise → confirm → `done` and overturn seams on real Postgres, two decisions on one epic both current, the epic's body untouched, the boundary stamp and the prompt fixtureApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-ai) A RE-PLAN may lay the decision work item AT THE EPIC — the palette carve-out keyed on the plan changing committed work, and the committed context keeping each decision's stamp, ordered oldest firstApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) A decision WAITING and a decision DECIDED in the lists — `ApprovalRow`'s `decision_confirmation` branch on To approve and in the Approvals room, confirmed or overturned on a decided row (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) THE CONFIRM PORT in the frame — the item page and the overlay, Confirm · Overturn, the record link, the confirmed / overturned / no-record bands, defect and read-only states, and the user doc (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The DISPATCHED prompt hands a run its epic's CONFIRMED decisions, oldest first with their dates, and the CALENDAR rule: code newer than a decision that contradicts it is REPORTED, never repairedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The AI boundary carries a decision's CONFIRMATION — `get-item` and `get-subtree` return a decision work item's gate state and its confirmed-at / overturned-at stamp, so the planner can date and order themApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-ai) THE SAME RULE in `SHARED_PLANNING_RULES` — the decision-work-item segment, `type-decision`'s record bar and the rung-3 CALENDAR limb, in `motir-meta`'s wordsApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) OVERTURN — the refusal arm built, not described: the decide door's `overturn` verb with its required note, the stamped `overturned` record, its terminal effect, and the re-plan it records as OWEDApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-meta) THE RULE in the runbook packs — a re-plan that moves approved work by WORKFLOW, MORE or LESS lays ONE decision work item at the epic; decisions ACCUMULATE; the rung-3 CALENDAR limb; `type-decision.md`'s record bar; MANIFEST regeneratedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join