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
- 5
- 요청
- 4
- 추천
- 482
- 계획됨
- 4,345
- 출시됨
- Planning bug: a POST-DEPLOY verification child is discharged by the merge it exists to outlive — the story's completion cascades `done` onto it 27 seconds later
- The design-result publisher ships ONE `##` section of ONE notes file — a newly-added `design-notes.md` publishes only its first section, and a second area's note is dropped with no log line
- decision: does push-to-`main` get its own lane — Motir's fleet and/or a deploy-only main run — or did the ceiling lift and the fan-out cut already buy it?Self-improvement — auto-reported quality bugs
- The SIXTH tool registry is a hand list whose stated justification expired — a new MCP tool rots it at run time, not at compile time
- (motir-ai) Mirror the post-merge card's PLACEMENT limb into `SHARED_PLANNING_RULES` — the shipped planner has gate 14(c) and not its second half
- (motir-core) Cut the PR lane's job fan-out — path-filter the container-image jobs, take the at-scale E2E legs off the PR trigger, and replace the branch-NAME skips with diff predicatesSelf-improvement — auto-reported quality bugs
- A `modify` proposal cannot patch `explanationMd` — `PlanItemPatch` omits the field its `add` twin carries, so a re-plan's survivor keeps a stale WHY through the only door a run has
- (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