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
- 520
- planned
- 5,600
- shipped
- Planning bug: a `notes.html` #27 filing writes `relates_to` where gate 4 also owes `blocked_by` — when the found-in card IS the consumed card, one edge hides the other
- Planning bug: a card asserted a MECHANISM from a log line, and the run that ran the probe could not reproduce it
- Planning bug: a card specified a state check by pointing at an EVENT check — the completion gate's default-branch comparison reads a live payload field the mirror never persists
- Planning bug: a design child's deliverable is a PUBLISHED artifact, and the artifact-obtainable rule's example list read as a membership test that excluded it — the run reported In Review on a PR link while the card showed nothing
- Planning bug: a bug card was authored with a DIAGNOSIS the fixed lock order already excludes — the observation was read as a leak, not as a winner-order artifact
- Planning bug: a coverage card measured its own DENOMINATOR off the FILE that declares the constant, not off the constant — and the two differ by 14%
- CI infra flake, 3rd leg in 6 hours: `playwright install-deps` HANGS on the Ubuntu apt mirror and burns the whole 6-hour job budget, because its 3-attempt retry has no per-attempt `timeout`
- A REFUSED multi-anchor plan open leaves a lease behind on the anchors it already took — `acquireForScope`'s all-or-nothing contract does not hold under a real race
- `work-item-type-taxonomy.md` Amendment 1's follow-up table has no row for `motir-ai`'s `SHARED_PLANNING_RULES` — the sweep list that missed the mirror still misses it
- `corpusConservation.ts` carries the `. **⚠️` limb of MOTIR-2969 unfixed — the port dropped clause (3) but kept clause (1), so the next rule added before a `⚠️` marker reds the mirror
- Planning bug: invariant C's verdict rides the DIFFER'S ALIGNMENT — a run boundary landing on a markdown marker reds a pack no fixture span can fix
- Nothing conserves the ROUTING — `SHARED_PLANNING_RULES` drops the pack tag, so re-tagging a rule silently changes which cells receive it while every check stays green
- The hosted planner still sweeps the PRE-taxonomy work-type list — `SHARED_PLANNING_RULES` offers `doc`/`spike`/`human`, which are unsettable, and never offers `chore`
- The DOWNWARD cascade is CANCELLED by a racing rung-4 recompute — the parent settles at To Do with every child untouched, and `status-derivation.spec.ts` flakes on it
- 8.5.16 Platform-staff gate FOUNDATION — the `platformRole` flag, `requirePlatformStaff()`, the 404-gated `/admin` segment, and the `PlatformAuditLog` record
- The FOURTH short enumeration — 13 failures in 10 files the flip surfaced, twelve mechanical and one a `moveCard` mode-split MOTIR-2919's ADR forbids
- Three packs stay `[FAIL]` on invariant C for the MID-SENTENCE WIDENING shape — the remedy is decided and nobody owns the sweep
- A user's own `→ Done` is REFUSED (422) when rung 4 lands between their two clicks — the parent they just started is silently back at To Do
- CI feedback posts ONE COMMENT PER CHECK NAME — a motir-core PR buries its work item under ~34 comments, several of which contradict each other while the run is still going
- `SHARED_PLANNING_RULES` has NO historical baseline — invariant B compares the rebuild to itself, and the 58 phrase assertions pin 1.20% of it, so a re-wording of the shipped planner corpus passes every test