moooon
Motir
Vibe your whole 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
- 1
- requests
- 0
- upvotes
- 142
- planned
- 1,379
- shipped
- Planning bug: MOTIR-3487 claims an E2E lane 'already has every piece' from a sibling spec's SUBJECT — the spec seeds the ledger and its own header says the writer path has no seamPlanner self-improvement — auto-reported quality bugs
- Planning bug: MOTIR-3547 was sealed UN-SIZED at ~5h across three repos, and asserted a code fact read from ONE of a tool's TWO return channelsPlanner self-improvement — auto-reported quality bugs
- Planning bug: the COLLAPSED supervisors run on Inngest between MOTIR-3417's merge and MOTIR-3489's flip, holding one invocation for the container's whole lifePlanner self-improvement — auto-reported quality bugs
- Planning bug: MOTIR-3626 recorded the over-gate advisory as "REAL" and declined it IN WRITING — an advisory ACKNOWLEDGED is not an advisory DISCHARGED, and the acknowledgement makes the card read as carefulPlanner self-improvement — auto-reported quality bugs
- (motir-core) Re-measure the fast lane on the engine and RECORD the figure — flip the honesty assertion, or say why it still standsOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) A free org CAN exceed its work-item cap — `lockByIdForUpdate` locks ZERO rows under `withWorkspaceContext`, and nobody reads the `false` it returnsOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) NOTHING reconciles the census against the live secret — `MIGRATED_TO_ENGINE` and `MOTIR_POSTGRES_JOB_IDS` drift silently, and each newly-routed job costs one more operator cardOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) A FOURTH job landed mid-cutover and is unrouted — `system.job-run-reap` declares `MIGRATED_TO_ENGINE` in the census while the live secret does not carry it, so it will run on InngestOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) The entitlements FOR-UPDATE race test has gone red three times on unrelated diffs, and it THROWS AWAY the one measurement that would say whether the lock brokeOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) TWO event-triggered jobs landed after MOTIR-3463's wave and are still unrouted — `plan-drift/transitioned` and `public-follow/digest` are on Inngest and no card owns themOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) One failed run writes TWO `job_run` rows and neither is legible — the `running` row never resolves and the failure lands on a second row with an unattributable `event_id`Own the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) `main` cannot deploy — the `billing-cloud` at-scale leg has been red since 07:18Z on the transient double-subtree strict-mode class at `/settings/project/ai-planning`, and no production deploy has gone out since 01:50ZOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) `system.code-graph-refresh` fails ~32% of the time — 62 of 194 runs in 7 days die on `admission_deferred: index admission was refused for 60 attempts`Own the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) A 15th scheduled job landed mid-cutover and is still on Inngest — `system.public-follow-digest-tick` breaks MOTIR-3418's "nothing remains on Inngest" premiseOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) The daily health check has been RED for 23 days and nobody noticed — `IndexFleetImageUnpullableError` every night since 2026-08-04, last success 2026-08-03Own the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) TAKE the fast-lane latency reading on the engine — the six figures, from inside the deployment, on a tail worth readingOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) Cut the 14 SCHEDULED jobs over IN PRODUCTION — ADD the ids to `MOTIR_POSTGRES_JOB_IDS`, read each cadence back from the ledgerOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- Planning bug: the `subsumption` advisory only sees MERGED pull requests — a defect filed 48 min into the OPEN window of the PR fixing it is invisible to every checkPlanner self-improvement — auto-reported quality bugs
- (motir-core) `coverage-gate-globs` is a whole-tree scan MOTIR-3144's lane left behind — it globs 483 files in 0.8 s and times out at 15 s on a loaded coverage shard, twice in three daysPlanner self-improvement — auto-reported quality bugs
- Planning bug: three 8.4 legal cards were typed `coding_agent` while their acceptance required counsel review — and the human-sized estimate was the tell nobody readPlanner self-improvement — auto-reported quality bugs