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: 514
planned: 5,093
shipped

Follow Request a feature Atom feed

19 Sept 2026Planning bugs are FILED into the Planning bugs folder — the planner-bug destination becomes a per-project folder pointer, and the home story is emptied and archivedSelf-improvement — auto-reported quality bugs
19 Sept 2026(motir-core) A FINISHED pull request whose last check rows are stuck at `pending` still folds to `running` for ever — MOTIR-5786 dropped only the no-rows arm; the backfill would still flip 40 done cards `passing → running`Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
19 Sept 2026(motir-core · design) The UN-LANDED merge, by REASON CLASS — RETRYABLE and BLOCKED-BY-A-SETTING re-ask at In Review with *Retry merge* / *Queue again* on the pull-request row AS the approve, CAN'T-LAND at Implemented with `motir fix` only, a host refusal at the press, on the page AND in the approval overlay — a revision of `approve-and-merge--ejected--reasked.mock.html`Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
19 Sept 2026Planning bug: a settings control was planned for a value only ONE tenant's code path reads — five cards of UI for an inert switch
19 Sept 2026(motir-core) The agent's DECISION LANE — the dispatch prompt's `decision` steps require ONE `docs/decisions/<slug>.md` in the target repository and a pull request that carries it, and say the decision waits for a personApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
19 Sept 2026(motir-core) Playwright acceptance E2E + VIDEO — an agent's decision in a pull request waits for a person, one Approve accepts it and merges, a missing document cannot be approved, and a human decision card offers no gateApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
19 Sept 2026(motir-core) Story VITEST gate — the coverage floor over the decision arm, the capture → gate set → decide → merge seam on real Postgres, the resolver swap, and the guards the percentage cannot seeApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
19 Sept 2026(motir-core) The To-approve tab's DECISION row — the kind's glyph and the document's heading as its subject line replace "Not built yet" (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
19 Sept 2026(motir-core) THE DECISION PORT — the decision document rendered as the PRIMARY question in the Development frame, the overlay and the item page, every state 5673 draws, and the user doc's entry (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
19 Sept 2026(motir-core) The GATE SET asks the decision question — `resolveGateSet` learns `decision_approval` as the PRIMARY, a push that changes the document supersedes it, its approval carries the merge once, and an awaiting decision HOLDS an `auto` mergeApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
19 Sept 2026(motir-core) REGISTER `decision_approval` — the handler over the document at the pull request's head, read through a RESOLVER interface a second implementation proves, its subject summary, and the promotion out of the registry's holesApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
19 Sept 2026(motir-core) CAPTURE the decision document's identity at the pull request's HEAD — the mirror columns, the opened / synchronize / reopened capture off the host's file list, and the expand-only migrationApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
19 Sept 2026(motir-core) AMEND `approval-gates.md` for the DECISION gate — its subject is the `docs/decisions/*.md` file in the card's MANDATORY pull request, it is PRIMARY over the merge like the design gate, and one press accepts it and mergesApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
19 Sept 2026The DECISION gate — an agent's decision ships as a `docs/decisions/` file in a MANDATORY pull request, a person accepts it as the primary question, and one press accepts it and mergesApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
19 Sept 2026The rollout is VERIFIED on the live deployment — the backfill ran, and a real production error files and closes end to endProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
19 Sept 2026(motir-core, production) READ the monitor jobs' real run history from production's job ledger — the reconcile tick has run and succeeded, the polls and the resolve succeeded, and no connection sits degraded or carrying an unread sync errorProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
19 Sept 2026A REAL production error in the connected `motir` project files exactly ONE bug into its destination folder, and completing that bug RESOLVES the issue — read in Sentry, not inferred from MotirProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
19 Sept 2026Error: MOTIR-4941 production verification probe — safe to resolve
19 Sept 2026CONNECT Sentry org `motir` to the `motir` project on app.motir.co — authorise the install in Sentry, return to the Monitoring room, and observe the row reading `connected`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
19 Sept 2026(motir-core · design) The acceptance gate as PRIMARY — the receipt leads, the story's pull requests and How to test sit beneath it as what the one press merges, and the single-card-run shape where the story stands aloneApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join

Subscribe by Atom