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
- 519
- planned
- 5,600
- shipped
- (motir-core) The whole-tree structural guards are lint, not tests — they flake because they run inside the sharded database suite and inherit its contention
- (motir-core) The design-result publisher's changed-file diff is TWO-DOT, so a PR publishes design assets it did not author — silently onto its own card, or fatally when the branch names a story
- (motir-core) `acceptance_trace` rows are LISTED in the attachments panel — the schema documents them as excluded, and both panel queries' denylist omits them
- Widen the mock scanner to structural selectors — and sweep the 391 MUTED violations it un-blinds, which the enforced arm has been green on since it shipped
- CI infra flake, 7 legs in one day across 3 PRs: MOTIR-2970 bounded `install-deps` but left the apt dependency — the durable fix is to stop using apt
- (motir-core) Settings → Repositories tells a project with five repositories that it has none — the room reads only `project_repository`, so MOTIR-3086's layered domain is invisible to every surface that renders it
- The workflow status DOT renders as a 2px sliver, not a 10px dot — `Combobox`'s icon slot leaves the dot `display: inline`
- The design-result leaf check reads KIND, not whether the card has CHILDREN — so a `bug` CONTAINER slips past MOTIR-3124's no-op and reds the build with a 500
- The Mono-Technical specimen and its doc are ONE ROLE behind the pairing they specify — the 2026-06-19 whole-UI re-typing decision landed in the CSS and in neither document
- (manual) Raise the GitHub plan above `free` — the org's 20-job concurrency ceiling is what starves BOTH the PR lane and `main`Self-improvement — auto-reported quality bugs
- `design/auth` and `design/typography` ship assets with no `design-notes.md` — the other half of the three-file rule, exempted by name in the new guard
- `debounce-burst` flakes as a STALE `n`, not as two runs — the length assertion above it cannot see the split its own comment predicts
- `waitForWindowHeadroom(w, w)` does NOT sleep on a boundary millisecond — the case asserting it always does is wrong 1 run in 200
- (motir-core) `main` is RED — MOTIR-3086 widened the repo-pin domain after MOTIR-3078's migration test asserted the old rejection, and neither PR could see the other
- The design-result publisher red-lights every PARENT-RUN pull request that touches `design/**` — a container-addressed publish fails instead of no-opping
- (motir-core) Read a proposal with the SHIPPED quick view (editing disabled), REMOVE the proposal edit modal, and hold `PlanReviewItemDto` against `PlanItemProposedFields`
- (motir-core) The plan canvas renders the parent's ROADMAP LEVEL — breadcrumb + real siblings, with proposals overlaid in `add` style
- The plan review surface is NARROWER than the proposal it reviews — an out-of-plan parent renders as a root, and there is no read view for a proposed card
- Seven design mocks have never had a `.png` export — the three-file rule is stated in `CLAUDE.md` and enforced by nothing
- (motir-core) The deploy is STARVED, not lost — `ci.yml`'s workflow-level `cancel-in-progress` lets each merge kill the run in flight, so no run on `main` ever survives to reach Fly