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
- 賛成票
- 462
- 計画済み
- 4,328
- リリース済み
- Planning bug: the two-homes obligation is stated only in `CORPUS-MAINTENANCE.md`, which no planning pass loads — six occurrences, five sibling cards, no gate
- Planning bug MIRROR: (motir-ai) carry the widened deferral surfaces + the placeholder triggers into `SHARED_PLANNING_RULES`
- Planning bug: (motir-meta) a deferral written in a DESIGN ASSET or a source COMMENT is invisible to the deferral-is-a-card rule — the AI orb shipped a mock "M" for 18 days with no card
- Planning bug: a card's "Read and deliberately LEFT" section states a COMPLETENESS claim ("every other literal was read") that a re-run falsifies — a false absence the next card inherits
- Planning bug: the totality rule (#29) cannot reach a renderer keyed on a DATABASE-defined set — a `Record<Union, …>` is total against a union that is itself the hand-authored subset, so the compiler certifies the lie
- Planning bug: a card's SCOPE-PROXY criterion contradicted its own instruction criterion — "no `app/` path" forbade the very file another criterion required a comment in
- (motir-ai) Mirror the sweep-is-not-its-grep-pattern limb into `SHARED_PLANNING_RULES` — a pattern's silence is a result, never a scope verdict
- (motir-core) The E2E job worker sends email through the CONSOLE provider, so no engine-routed send ever reaches the outbox — `jobs-postgres-engine.spec.ts` is red on `main`
- (motir-core) Story E2E — one transition fans out to all four fast-lane consumers on the engine, and a repeated invite emails onceOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) Story gate — vitest coverage floor, the emit-to-run seams, and the totality guards a percentage cannot seeOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) `docs/jobs.md` — the emit seam, engine-side idempotency, and what "cut over" means to an operatorOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) Event-level IDEMPOTENCY on the engine — carry `defineJob`'s key through and dedupe on it, so `email.send` still sends onceOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) Make the subscriber set reachable from the emit path, with a guard that fails when it is notOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) The engine's fast-lane latency probe — event to run p95, read from the ledger instead of a vendor APIOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) Route every emitter through `sendEvent`, and make the ESLint boundary enforce itOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) Decide how the EMIT PATH learns the subscriber set — the engine registry is empty on a web requestOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- Cut the EVENT-triggered jobs over — fan-out, the fast lane's latency budget, and the notification / automation / email pathsOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- 15 3D / Immersive leaves 199 of 280 interactive controls flat — the physical-key rule matches `rounded-(--radius-btn)` only, so Plan with AI, Re-plan, the 3-dots menu and the roadmap search have no depth (motir-core)
- Planning bug: MOTIR-3440 NAMED `PageSkeleton` as unowned and created no card, so MOTIR-3443 shipped `ready` with an acceptance criterion nothing could satisfy
- (motir-core) Design — the DELIVERY state on the operator jobs dashboard (`/settings/workspace/jobs` has no design asset at all)