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
- 528
- planned
- 5,566
- shipped
- Planning bug: a card's rung-2 evidence asserted an absent workflow edge that ships — the decision survived, the argument's KIND did not
- Planning bug: a card whose precondition is a DEPLOY was gated by a `blocked_by` edge, which discharges at MERGE — the RULE half (the lesson shipped)
- Planning bug: the delivery-reader inventory's own re-measurement was short by two — its grep cannot match `?.workItemId`
- Planning bug: a story was authored with a DEPLOYED-tenant verification card inside it, gating three siblings that ship at merge — so the story's own pull request could never open
- Planning bug: the corpus CONTRADICTS ITSELF on what approve does to a proposal's status — `_shared.md` and `run.md` say it derives nothing and cite the code, `plan-procedure.md` says it derives from the edges, and the shipped `materialize` agrees with `plan-procedure.md`
- Planning bug: a card that ENUMERATES the homes of a symbol quotes a grep it did not run — MOTIR-3777 named seven of ten
- Planning bug: MOTIR-3750's measurement block secured the SET and left the CAUSAL sentence beside it unmeasured — the file it blames the classifier for was last touched two days BEFORE the classifier existed (and the count was one high)
- Planning bug: the CORRECTION to MOTIR-3721's inventory was itself scoped by a one-file grep, so nine is short by seven in the same shape as five was short by four
- Planning bug: MOTIR-3634's own TEST asserts a property of sibling MOTIR-3635's output, and the split left the two edge-free
- Planning bug: a bug card's root cause was derived from a STALE COMMENT and from a call path a memo makes unreachable — two mechanisms, both falsified at the first grep
- Planning bug: a card's second half was inferred from a MODULE PATH — `lib/ai/codeContext` was read as "calls motir-ai" while its whole import closure is Prisma
- Planning bug: MOTIR-3739 called a neighbouring line "protected" without reading its call chain, and named ONE instance of a copy-pasted pattern as the population
- Planning bug: MOTIR-3721 inherited its reader inventory from the ADR that authorised the retirement, so the readers the replacement CANNOT serve were never counted
- Planning bug: MOTIR-3721's dependency on a sibling's OPEN pull request was written as prose, not a `blocked_by` — and two cards in the same story shipped with a null `explanationMd`
- (motir-core) A `modify` proposal's body cannot carry an intra-plan CHIP — materialize rewrites `motir-ref:planItem:` on `add`s only, so an amendment naming a card the same plan proposes ships an inert link
- 8.51 (motir-core) `worker-fairness-story-gate.test.ts` polls the LEDGER row and then asserts on the QUEUE row — `settle()` writes them in that order, so Vitest shard 3 is red on `main`
- 8.3.6 Build the motir-marketing landing (new repo) — THREE cross-origin doors: idea hero · import existing · start freeMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- 8.3.13 Publish `@motir/brand@0.1.0` to npm by hand + configure its Trusted Publisher (manual)Motir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- 8.4.30 The deletion confirmation still promises that signing in cancels the erasure — MOTIR-3742 swept four carriers of that claim and left the shipped copy and panel 3 standing
- Planning bug: a card's post-merge PUBLISH obligation was recorded as a comment and offered as a question ("say so and I will propose one") instead of filed as a card — MOTIR-1456 went `done` with `@motir/brand` unpublished, and MOTIR-1152 hit it eight hours later