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
- solicitudes
- 4
- votos
- 489
- planificados
- 4378
- publicados
- Planning bug: an acceptance criterion keyed on a COUNT that the code's own idempotency argument forbids — the falsifying comment sat one file from the card's own context refs
- The repository-set design assets specify a FAILING ink/surface pair — muted on `--el-surface-soft` (4.34:1), which the ink lint forbids in code but does not scan for in `design/**`
- `statusDerivation.ts` records the REFUTED debounce mechanism as the warrant for its not-debounced decision — three comment blocks survived MOTIR-2994's measurement
- The Development section shows "No pull request yet" for a repository whose pull request is listed directly above it
- (motir-core) `rateLimit/guard.test.ts` never aligns its window — the LAST unswept member of the epoch-boundary class, and the alignment guard is structurally blind to it
- Planning bug: MOTIR-2757 sat `todo`/`high`/ready for two days after MOTIR-2796's sweep shipped its entire deliverable — every readiness signal read green
- (motir-ai) Mirror the ALREADY-LINKED-KEY clause into `SHARED_PLANNING_RULES` — an existing edge to a key is not evidence its status was resolved
- 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`