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
- 추천
- 466
- 계획됨
- 4,366
- 출시됨
- `POST /v1/stripe/checkout-session` can NEVER create a session — motir-core sends a price LOOKUP KEY, motir-ai passes it straight into `line_items[].price`, and every catalog key 404s `No such price`
- Planning bug: the correction was posted as a COMMENT and the description kept the false claim — second instance, and both times the run that wrote the comment also wrote the card that asserted it was applied
- Planning bug: MOTIR-2939 attributed a count rise to two specs from what LANDED RECENTLY, not from measuring — one of the two was already inside the baseline
- Planning bug: an acceptance criterion asserted a PIPELINE's outcome ("the PR is green") when the card owned one STAGE of it — the other stages were never verified
- `main` is RED — MOTIR-2918 landed `UNCONVERTED_E2E_CEILING = 454` against a tree that already measured 457, so the ratchet it added fails on its own merge commit
- Planning bug: MOTIR-2919 called MOTIR-2911's conversions "landed" two minutes before their PR existed, and wired the edge `relates_to` — its "0 failures" criterion is unreachable from `origin/main`
- Planning bug: a decision forbade every in-product path that could write the column it governs, and no card owned the one path left — a dev-only seed criterion made it look owned
- 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