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
- 賛成票
- 417
- 計画済み
- 4,241
- リリース済み
- 2200.19 (motir-ai) The container must REFUSE a restored snapshot its own engine calls stale — the guard, landed before anything starts offering one
- (motir-core) The universal approval FRAME — three bands, a kind-supplied verb set, seven states — and the Design result section BECOMES itApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) `link_pull_request` flips a card to `implemented` even when the pull request is a DRAFT — `resyncLinkedPullRequest` hard-codes the lifecycle and the stored row records no draft-ness
- (motir-core) A GitLab DRAFT merge request never reaches `implemented` — the un-draft event is `action: 'update'`, which `HANDLED_MR_ACTIONS` deliberately does not handle
- 2200.15 (motir-core) The SCOPED run never opens its session PR mid-run — `openPrEagerly` is a lane gate `scopeDrain.ts` cannot take, so point 1 of the decided lifecycle is unimplemented for the lane it was decided for
- 2200.13 (motir-core) The organisation surface still promises the RETIRED workspace rung — two strings say a set-less project "can also reach" a repository, and one of them is reassurance on the DISCONNECT dialogue
- (motir-core) RETENTION — an approved version's bytes are PINNED, a superseded subject retires its awaiting gate, and neither races a concurrent publishApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The gate's AUDIT columns — the approved version, the surviving actor label, the routed-to, the permission, the source, the outcome, and the immutability guardApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) A linked pull request cannot be REMOVED from a work item in the product — `unlink_pull_request` exists only on the MCP, so the hold note's own remedy is unreachableApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The scoped run's session PR opens READY FOR REVIEW mid-run — it must open as a DRAFT and be marked ready at close-out
- (motir-core) The DECIDE door — one service and route that records a decision on ANY gate, with the registry and the `design_result` handler as its first memberApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Design — REMOVING a linked pull request: the Development row's remove control, its confirm, and the copy that says the pull request is untouchedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) A MERGE does not complete its card when a SIBLING delivery was closed unmerged — the delivery-set gate reads `merged` alone, so an abandoned pull request counts as "still open" for ever
- Planning bug: an acceptance criterion cited a RECORD for a sentence the record never carried — the quote was taken second-hand from a code comment
- Planning bug: a bug card's error count was measured against a stale generated Prisma client — 175 phantom errors, 1 real
- (motir-core) The status machine cannot see a DRAFT — it flips a card to `implemented` when a draft OPENS, and never when the draft becomes ready
- 28 (motir-core) A committed card blocked_by a card the plan MOVES ONTO its level keeps the red `cross` arrow — the canvas says "blocked elsewhere" about a card drawn right beside it
- Planning bug: a story encoded an IDENTITY question as a stored marker after the user had said, during planning, that it must be a judgement — and four cards shipped correcting the level below it
- Planning bug: two cards of one story asserted a state of shipped reality that one grep falsifies — a design asset's rail, and a sibling's merge status
- Planning bug: MOTIR-4727 asserted an ARCHIVED key is a 404 on a read it also specifies as an unchanged pass-through — the two clauses contradict, and only the shipped code says which wins