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
- 521
- planned
- 5,600
- shipped
- Planning bug: a dedup wrote its blocker's new position in PROSE and left the card parented in a LATER epic — a permanent deadlock that `validate_work_item` reported and nothing read
- (motir-ai) Mirror the PROSPECTIVE LIMB into `VERIFY_EVERY_PRECONDITION` — a counted set, a named test home, and an unchecked NEGATIVE are precondition claimsSelf-improvement — auto-reported quality bugs
- Planning bug: MOTIR-2903 specified its mechanism against a "PR set" that carries no diff — the precondition was asserted as already-shipped ("this is the same read"), in a clause whose job was to price the card
- `MOTIR_AI_TO_CORE_SERVICE_TOKEN` is set in NEITHER production deployment — the whole ai → core service channel cannot authenticate, so a real Stripe subscription event throws before it is recorded and Stripe retries it forever
- The offboarding BACKSTOP has no invoker — `codeGraphReconcileService.reconcile` is referenced by nothing but its own tests, so the dry-run numbers MOTIR-2169 deferred its destructive arm behind cannot be produced at all
- (motir-ai) Mirror W5 into `SHARED_PLANNING_RULES` — the taker inherits the donor's blockersSelf-improvement — auto-reported quality bugs
- (nextjs-prisma-vercel-starter) The PR that RETIRES a project's last acceptance spec red-lights its own lane — `test:e2e:acceptance` carries no `--pass-with-no-tests`
- `/boards` renders the server-error page on the CLOUD-ON lane — no board spec rides that lane, so nothing has ever exercised the board under `MOTIR_CLOUD=true`
- Planning bug: a bug card's COVERAGE NEGATIVE ("no board spec rides that lane") went unchecked and is false — and its 500 does not reproduce at the reporter's own base commit
- (motir-meta) W5 — the dedup limb: a taker inherits the loser's BLOCKERS, not only its scope (`op-replan.md`)Self-improvement — auto-reported quality bugs
- (motir-ai) Mirror the TERMINAL-card limb into `SHARED_PLANNING_RULES` — a `blocked_by` set is a function of the child set, not a snapshotSelf-improvement — auto-reported quality bugs
- The acceptance lane still fans out to 4 shards for a lane that now holds 0–2 specs — the fan-out is pure setup cost
- 8.5.17 Decision — the platform-staff auth model: `PlatformRole` separate from `MemberRole`, audited cross-tenant read, where `/admin` lives
- Planning bug: an incident card was authored from a single reconciliation read, and its own two printed timestamps disproved it — the remediation steps would have deleted a live customer's billing entity
- Planning bug: a TERMINAL card's blocked_by set is written once and never re-derived, so every sibling filed after it leaves the card reading `ready: true` while definitionally un-runnable
- A parent is STRANDED when its child finishes faster than derivation runs — the aggregate jumps to all-done and `todo → done` has no edge
- (nextjs-prisma-vercel-starter) The starter's acceptance lane has the same trigger blind spot MOTIR-2760 fixed in motir-core — every scaffolded project inherits it
- Planning bug: a card's FIX DIRECTION carries the authority of its root-cause evidence without the method — MOTIR-2763 mis-counted its referrer set (2 of 4) and named a test lane that cannot mount the element under test
- Nothing in the shell reserves clearance under the floating "M" orb — at the end of a scrolled page it covers the `/items` pager and `/home`'s Next, and both stop being clickable
- Planning bug: the `validate_work_item` post-condition is bound to a PLAN PASS, so no card created mid-run is ever checked by the mechanism built to catch exactly this — MOTIR-2011's family, ×7