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
- 8.3.17 motir.co serves `@motir/design-system@0.1.0`, which predates MOTIR-3745 AND MOTIR-3774 — five accent-ink cells fail AA on the live site, and `/design` is about to make every one of them reachable in one clickMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- 2200.3 (motir-core) The plan PROJECTION places a re-parented card under its OLD parent — `planProjectionService` reads `patch.parentRef` nowhere, so the agent checking the tree it proposed is shown the tree it did not
- A plan cannot RE-PARENT an existing work item — `PlanItemPatch` has no parent key, and motir-ai's `modify_node` advertises "re-parent" three times while carrying no parameter for it
- 8.3.15 Copy — the `/design` showcase page's words + the nav label, at the marketing register (motir-marketing)Motir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- 8.3.14 Design — the public design showcase at motir.co (`/design`): the composed specimen, the three axis pickers + theme toggle, and the site's first current-page nav entry (motir-marketing)Motir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- 2200.2 The INTERNAL proposal-correction route drops `explanationMd` and has no `targetRepoRole` — Motir's own planner cannot rewrite a proposal's WHY through a door an external MCP agent already has
- 8.54 `motir.co` serves NO favicon — the brand's front door has no mark in browser chrome, and the repo carries no icon file at all
- 2200.1 (motir-core) A Prisma DROP COLUMN needs THREE deploys, not two — the model DECLARATION is a reader, and removing it in the CONTRACT commit is what 500-ed `get_work_item` tenant-wide
- (motir-ai) `modify_node` is three keys behind `PlanItemPatch` — no `explanationMd`, `targetRepo` or `targetRepoRole`, so a generated re-plan cannot rewrite a survivor's WHY or re-pin its repo
- 8.53 (motir-core) `ciRunnerAdmissionWake.test.ts` seeds intents with a FIXED `runId`/`runAttempt` and a random `jobId` from 900 values — a birthday collision on the unique index, flaking Vitest shard 2
- 8.52 `@motir/design-system`'s `Spinner` ignores `prefers-reduced-motion` — `animate-spin` has no guard, in the package or in either consumer
- (motir-core) MOTIR-3569 bounded `ci.yml` and left 19 runner jobs across ELEVEN sibling workflows on the 6-hour default — including `sandbox-images.yml` and `runner-image.yml`, which `ci.yml` itself calls
- (motir-core) A card delivered by a repository with NO CI can never be promoted to In Review — `derivePrCiState` returns `null` for "no CI" and for "no verdict yet" alike, and the promotion treats both as not-green
- 8.3.7 Entity-signal SEO root at motir.co (motir-marketing) — Organization+WebSite JSON-LD, root OG, robots, GSCMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- Planning bug: the IMPORT door's `?intent=import` has no reader and no owning card — its tracker twin got MOTIR-3639 and the import half was never carved
- 8.48 (motir-core) `--el-accent-on-surface` is under AA on `--el-tint-lavender` in the LIGHT theme of four palettes — and the accent inks there are marginal against ANY light surface
- 8.50 (motir-core) The legal-materiality tripwire cannot fire — it compares a version to ITSELF, and CI skips the whole Vitest lane for the `content/legal/*.md` changes it guards
- Planning bug: MOTIR-3735 deliverable 2 asserted `schema.prisma`'s `sessionBranch` "carries no comment" — it carries a 12-line one at the cited ref
- Planning bug: an acceptance criterion's own COMMAND enumerated a strict superset of its claim, so the criterion was unpassable and its literal reading was destructive
- Planning bug: a card generalised the side-effects-outside-the-transaction rule onto the AUDIT ROW, which is the one write that must be inside it