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
- 요청
- 4
- 추천
- 385
- 계획됨
- 4,155
- 출시됨
- (motir-core) Story E2E — a planning bug filed through the marker appears in the tree INSIDE its folder, with no parent cardSelf-improvement — auto-reported quality bugs
- (motir-core) Story gate — integration vitest across the whole seam: pointer set → marker resolves → bug FILED into the folder → folder deleted → pointer carried upSelf-improvement — auto-reported quality bugs
- (motir-meta) The corpus stops calling the planner-bug home a STORY — `run.md`, `log-bug.md`, `kind-bug.md`, `core.md` gate 15, `plan-procedure.md`, `_shared.md`Self-improvement — auto-reported quality bugs
- (motir-core) MIGRATION — adopt the `Planning bugs` folder, point the project at it, move every home-story child into it, and ARCHIVE the storySelf-improvement — auto-reported quality bugs
- (motir-core) The RESOLVER — `@planner-bug-home` resolves to a FOLDER, `fileBug` FILES instead of parenting, and the not-provisioned 500 retires for a fallbackSelf-improvement — auto-reported quality bugs
- (motir-core) Deleting the destination folder carries the PLANNER-BUG pointer up too — `deleteFolder`’s carry-up covers BOTH pointers, not oneSelf-improvement — auto-reported quality bugs
- (motir-core) SCHEMA — the project’s nullable PLANNER-BUG destination folder pointer, its migration, its tenancy trigger and its indexSelf-improvement — auto-reported quality bugs
- Planning 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
- (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
- (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
- Planning bug: a settings control was planned for a value only ONE tenant's code path reads — five cards of UI for an inert switch
- (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
- (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
- (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
- (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
- (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
- (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
- (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
- (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
- (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