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.49 (motir-core) A PLANNED plan flags an edge-less `add` as "Out of date" for every unrelated card logged under its parent — `siblingsAddedRule`'s one excuse is an edge the proposal cannot have written
- 8.3.4 Content — motir-marketing landing copy + positioning (idea · import-existing · tracker-first audiences)Motir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- 8.3.3 Design — motir-marketing landing (motir.co): THREE entry doors (idea hero · import existing · start free) + descriptive blocksMotir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- 8.45 `motir-marketing` publishes no DESIGN RESULT — it has no publish lane at all, and a `<name>.design-notes.md` basename is invisible to the classifier in either repo
- (motir-core) `acceptance-plans-surface` is RED on `main` — the fifth PlanStatus made a hardcoded tab count wrong, and it blocks every open PR
- Planning bug: a card proposed 'restore the yield, not the stepping' — the two are not separable, and the record it cited already said so
- (motir-core) 11 of ci.yml's 14 jobs declare NO `timeout-minutes`, so a hung job burns SIX HOURS and is indistinguishable from a slow one — the same gap MOTIR-2970 closed at one call site
- 8.4.29 The account-data design asset draws a DELETED group with no export row — the design of record now under-draws the shipped ledger
- 8.44 (motir-core) `--el-accent-on-surface` is 4.41:1 on `--el-surface-soft` in DARK — `ExploreTopBar`'s current-page nav item fails AA, and the ink lint has no accent arm
- 8.46 (motir-core) Adding a repo from GitHub's OWN installation settings always shows "We couldn't finish setting up the GitHub App" — the install SUCCEEDED, and only the signed `state` is missing
- 8.43 `motir-marketing` is provisioned but NOT connected to Motir — `targetRepo` is refused and a merge on that repo moves no card
- Own the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- The plan-target-lock RACE test truncates the database five times inside one 15s timeout, and has red-flagged four unrelated PRs
- (motir-core) `jobs-scheduled-engine.spec.ts:164` reads an ARBITRARY ledger row — `findFirstOrThrow` with no `lane` filter and no `orderBy`, over a table that holds one row per attempt AND per lane
- The CI-fix loop never says to MERGE the default branch FIRST — so a fixing agent diagnoses a tree CI never judged and spends attempts on a red it did not cause
- (motir-core) `code-graph-refresh-engine.spec.ts` hand-rolls a TRUNCATE that bypasses `db-reset.ts`'s 40P01 retry — it deadlocks against the E2E job worker and reds unrelated PRs
- 8.42 `org-admin.spec.ts` is the SECOND site of the double-mount locator class — `getByLabel('Organization name')` matches the outgoing subtree too
- Spectrum DARK fails AA on the danger button itself — `#ffffff` on `#f0555f` is 3.40:1, the only one of 20 palette×theme pairs under the bar
- (motir-core) A double-click of Replay RAISES P2002 out of the dashboard action — the engine's DLQ replay enqueues by INSERT and does not treat the dedup violation as "already enqueued"
- `--el-danger-text` carries error text on a plain surface at 14 sites — 1.00:1 in EVERY palette's light theme, and the ink guard has no danger arm