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
- 561
- planned
- 5,466
- shipped
- (motir-core · test) `cloud-agent-runs`'s unscoped `getByText('Nothing has run yet')` hits strict mode in the MERGE QUEUE — green twice, red once, on app code that never changed
- (motir-core) `translateLinkViolation`'s P2002 fallback is UNCONDITIONALLY the name error — a lost repo-claim race is reported as "that name is taken", and it evicts merge-queue entries
- (motir-core) `Used by N projects` now OVER-reports — every set-less project is named against every connected repository, on the dialogue a disconnect leans on
- (motir-core) `Used by N projects` counts the repository SET only, so every connected repository reads “used by no project yet”
- (motir-core) `Code access` reads the repository SET only, so a project with connected repositories shows none — and nothing says how it differs from `Repositories`
- (motir-core) The project Repositories page names the ACTOR’s first organisation, not the project’s
- (motir-core) The shell brand mark links to `/dashboard`, not the landing — the product question MOTIR-3173 deliberately left, now answered; and the rail demotes `Dashboard` below `Backlog`
- 25 (motir-core) `publish_design_result` is unreachable for a real design asset — the door takes bytes INLINE, and the agent it is written for cannot emit them
- 24 (motir-core) The "Plan with AI" hero and the M orb render byte-identically in all 11 styles — the design's `[data-surface='ai-cta']` hook is emitted nowhere, and the fill is painted INLINE where no style rule can reach it
- 8.76 (motir-core) Sweep the E2E suite for the unguarded mutation→assert SHAPE — MOTIR-3694 swept one file, this card proposed to sweep the next one, and 770 candidate sites across 122 specs say the bound was never the file
- (motir-meta) MOTIR-4723 split the journey unit's APPLY STEPS in two and recorded only the half that MOVED — assertion 3 is RED on `origin/main`, one unrecorded divergence, for the clause that STAYED in `kind-container.md`
- (motir-meta) The SKILL doors cite nine pack paths that no guard checks — `MIRROR.check.py` assertion 7 sweeps `prompts/*.md` non-recursively, so the corpus's new front entrance can point at a retired pack under a green gate
- (motir-core) The ONBOARDING fact never crosses the wire — a `plan` submit carries no `context.onboarding`, so motir-ai guesses it from an EMPTY TREE and a migrate onboarding over an imported backlog is planned as continued work
- An `acceptance*.spec.ts` that imports the PROMOTED shim produces no receipt, and passes — nothing detects the swap
- `PLAN_ALONG_THE_USER_JOURNEY` is a rule about STORIES delivered to every container lay cell — `lay/project` lays epics and `lay/story` lays subtasks, and both are told to sequence stories; the discharge test narrows `kind-container` to the one cell that proposes them
- (motir-meta) The runbook MIRROR of MOTIR-4719 — `kind-container.md` back to `phase = lay`, `kind-story.md` split per unit by the discharge test into a lay pack and the both-phase count rule, the boundary clause to `kind-story-author.md`, and `split.py`'s SELECTOR, the MANIFEST and the 3866 note follow; five guards green
- (motir-core) An agent CANNOT publish an acceptance receipt over MCP — the tool the ADR names does not exist, the `test` dispatch prompt never asks for one, and a missing receipt looks exactly like a successful run
- (motir-ai) The container kind packs are routed by KIND alone at AUTHOR — `kind-container`'s one unit and three of `kind-story`'s four are discharged only by LAY tools, yet `author/epic` and `author/story` receive them; route per unit by the discharge test, and move the vertical-slice unit's BOUNDARY clause to the author pack
- (motir-ai) TWO identities in one system message — "You are Motir planning Motir's customers' products" and, on three of four situations, "You are Motir's work-item-tree GENERATION / AUGMENTATION / plan REVISION planner" (retired job kinds as self-description); and the TREE the planner builds is never defined
- 23 (motir-core) A missing work item's 404 is INVISIBLE — the stock not-found sets body colour from `prefers-color-scheme` while the ground behind it follows the app's own `data-theme`