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
- 145
- planned
- 1,361
- shipped
- ▸MOTIR-3414The Postgres job engine — tables, a worker process, durable steps, and a per-job cutover switchdone
- ▸MOTIR-3415Cut the EVENT-triggered jobs over — fan-out, the fast lane's latency budget, and the notification / automation / email pathsdone
- ▸MOTIR-3416Cut the 14 SCHEDULED jobs over — crontab, catch-up after downtime, and the sweeps that keep the platform tidydone
- ▸MOTIR-3417Cut the container supervisors over — and COLLAPSE the stepped shape now that nothing times outdone
- MOTIR-3418Retire Inngest — delete the SDK, the serve route and the dependency, and prove the substrate stands alonedone
- MOTIR-3425(motir-core) Provision the worker process group on Fly — `fly scale count`, read back from the platformdone
- MOTIR-3454(motir-core) The job listener LISTENs on the POOLED url — a transaction-mode pooler cannot hold a session, so the NOTIFY wake never arrivesdone
- MOTIR-3463(motir-core) Cut the 20 event-triggered jobs over IN PRODUCTION — `MOTIR_POSTGRES_JOB_IDS` in waves, read back from the ledgerdone
- MOTIR-3464(motir-core) Re-measure the fast lane on the engine and RECORD the figure — flip the honesty assertion, or say why it still standsdone
- MOTIR-3467(motir-core) Prove the PILOT job on the engine in production — route `email.send`, read the run row back, and close MOTIR-3414's stated scopedone
- MOTIR-3475(motir-core) Cut the 14 SCHEDULED jobs over IN PRODUCTION — ADD the ids to `MOTIR_POSTGRES_JOB_IDS`, read each cadence back from the ledgerdone
- MOTIR-3489(motir-core) Cut the THREE container supervisors over IN PRODUCTION — ADD the ids to `MOTIR_POSTGRES_JOB_IDS`, watch a real push coalesce, boot and indexdone
- MOTIR-3495(motir-core) Three dedup layers, none legible where a reader looks — `docs/jobs.md`'s canonical-job § and `JobEvent`'s index comment still name Inngest as the only enforcer after MOTIR-3459done
- MOTIR-3570(motir-core) Every deploy ends RED on a deploy that SUCCEEDED — `FLY_EXPECTED_MACHINE_COUNT` still says 2, and MOTIR-3425's worker group made the pool 4done
- MOTIR-3593(motir-core) The fast-lane latency probe reads the POOLED url and reports `samples: 0` — RLS hides every row, so it says "no fast-lane engine runs" while the engine is running the whole lanedone
- MOTIR-3594(motir-core) TAKE the fast-lane latency reading on the engine — the six figures, from inside the deployment, on a tail worth readingdone
- MOTIR-3606(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-03done
- MOTIR-3682(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" premisedone
- MOTIR-3683(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`done
- MOTIR-3684(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`done
- MOTIR-3688(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 themdone
- MOTIR-3692(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:50Zdone
- MOTIR-3707(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 brokedone
- MOTIR-3709(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 Inngestdone
- MOTIR-3710(motir-core) A free org CAN exceed its work-item cap — `lockByIdForUpdate` locks ZERO rows under `withWorkspaceContext`, and nobody reads the `false` it returnsdone
- MOTIR-3716(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 carddone
- MOTIR-3717(motir-core) Two concurrent first-workspace creates give ONE user TWO free orgs — the §4.5 org-creation gate takes no lock at alldone
- MOTIR-3730(motir-core) A double-click of Replay RAISES P2002 out of the dashboard action — the engine's DLQ replay enqueues by INSERT and does not treat the dedup violation as "already enqueued"done
- MOTIR-3731(motir-core) The engine has NO per-job concurrency, and a job that wanted one lost it silently — `account/data-export.requested` declared `{ limit: 1, key: userId }` and the engine never read the fielddone
- MOTIR-3739(motir-core) `code-graph-refresh-engine.spec.ts` hand-rolls a TRUNCATE that bypasses `db-reset.ts`'s 40P01 retry — it deadlocks against the E2E job worker and reds unrelated PRsdone
Showing 30 of 30