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
- 추천
- 396
- 계획됨
- 4,215
- 출시됨
- Planning bug: two cards filed against ONE contradiction resolved it in OPPOSITE directions, wired only `relates_to` — both read `ready`, and the second to run built on the first's deleted premise
- Planning bug: a surface EXEMPT from the tier-hiding rule was planned around as an exception instead of read as a missing fold-in — so the plan defended a workspace row inside the PROJECT rail
- Planning bug: two sibling design cards were laid as INDEPENDENT while one's acceptance criteria cite the other's file by PATH — in a repo whose design lane enforces that cited paths resolve
- Planning bug: a gate was planned onto a session that had neither the TOOL nor the FACTS — and its citation resolved, because the shipped code preserves the struck reasoning
- Planning bug: a control surface was copied from a comparable of a DIFFERENT product kind, and one axis was copied in a shape that comparable does not use — the residency switch promised EU and resolved to two US providers
- Planning bug: MOTIR-4408's population was measured with a command narrower than its own claim — five of eight members were invisible to it, three of them predating the card
- Planning bug: two cards for one race, filed 12h apart with mutually exclusive remedies on the same four lines — gate 8 sweeps who CLAIMS a deliverable, never who has declared it OFF-LIMITS
- Planning bug: MOTIR-4269's headline count was measured with a PROXY predicate — `grep -c 'descriptionFingerprint:'` counts the interface's own field declaration as a tool
- Planning bug: MOTIR-4363 set a 75% heap target without measuring the FIXED share of the cost it was partitioning — and its own criterion 2 forbade the only partition that could have reached it
- Planning bug: MOTIR-4363 enumerated FOUR vitest suites importing into `tests/e2e/`; there are NINE, and every one of the five it missed predates the card
- Planning bug: a card AUDITING a stale count copied the count from the wrong source — MOTIR-3580's "THREE rows behind" was five, and its table's first row was another card's state
- Planning bug: a card's *Measured* block quoted a `grep -c .` of 4 that returns 5 — the count was retyped from a partial read, not run
- Planning bug: MOTIR-4237 chose a UI destination from Motir's OWN surface inventory and never ran rung 1 — its "alternatives weighed and rejected" table listed three existing surfaces and no mirror product
- Planning bug: MOTIR-4193's acceptance criterion defers a decision to "the design pass" that has no card — a prose reference the advisory detector cannot see, and the card sealed ready: true
- Planning bug: MOTIR-3942 planned the conversation's whole CONTRACT and no PRODUCER — the pack, the value and the rules all ship, and nothing runs a conversation
- Planning bug: an interim UI defect card was ready with four visible dispositions and no design prerequisite
- Planning bug: a card's scope-boundary OUT list named the sibling that BUILDS the surface its criteria assert against — and the `blocked_by` edge pointed the other way
- Planning bug: `blocks` does not cross the AI boundary either — MOTIR-4055 enumerates THREE missing link kinds and there are FOUR
- Planning bug: MOTIR-3999 re-combined the publish + the re-pin on one card and omitted the 0.1.3 bump — the exact release-shape MOTIR-3965 was re-scoped out of, one release later
- Planning bug: MOTIR-3932's /explore and /docs scope items have no cards after the host-branch cards were archived