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
- 533
- planned
- 5,569
- shipped
- (motir-core) Story E2E — a push burst coalesces into ONE refresh run that boots, polls and settles on the engine, and survives a mid-index worker restartOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) Story gate — a supervisor RESUMES after a real worker restart, the debounce coalesces a burst, and the ledger contract and admission cap are untouchedOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) COLLAPSE the CI-RUNNER supervisor — `system.ci-runner-boot` converges onto `ciRunnerBootService.runIntent`, and the second composition goesOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) COLLAPSE the INDEX supervisor — `indexFleetSteps.ts` becomes one `while` loop over the service's own composition, and the `maxDuration` comments are CORRECTED rather than deletedOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) The engine's DEBOUNCE — a same-key `run_at` pushed forward on each arrival, so a push burst still coalesces into ONE run carrying the latest eventOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) Decision — what survives a WORKER RESTART mid-supervision: which waits stay durable steps, which become plain `await`sOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- Cut the container supervisors over — and COLLAPSE the stepped shape now that nothing times outOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- Record the never-fires lesson — an acceptance criterion that asks to OBSERVE something in production is unsatisfiable when the trigger has never fired (5 of MOTIR-3463's 20 ids, all_time=0)
- A revoked API token is never removed — the row stays in the credential list forever with no affordance to delete it, and the `revokedAt` it was kept for has no audit reader anywhere in the product
- 16 Roadmap: a level draws edges whose BLOCKED end is not on it — "Not in an epic" redraws the whole EPIC chain as 12 anonymous "blocked elsewhere" ghosts, and the root draws a grouped task as one
- `main` is RED on `Playwright E2E (bulk-5)` — a streaming boundary leaves TWO copies of the comments read-only notice in the DOM, and `jobs-fanout-engine`'s invite click times out at 120s on both attempts
- Planning bug: a mechanism-withdrawal amendment swept four of five dependents — the one it missed was the one whose SCOPE had not moved
- (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-3459Own the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) The operator jobs dashboard separates *accepted by the provider* from *delivered* — a `succeeded` run whose message bounced must stop reading as success
- (motir-core) The Resend delivery webhook — a signature-verified endpoint that turns `delivered` / `bounced` / `complained` / `delivery_delayed` into delivery state
- (motir-core) Keep Resend's message id — the send path returns it and `email.send` records one delivery row per message
- (motir-core) Transactional mail delivery is UNOBSERVABLE — Resend's message id is discarded, no delivery webhook exists, and the job ledger reads provider-acceptance as success
- (motir-core) Decision — where a NON-ADMIN's workspace-scoped settings live at one workspace, and §6d's amendment
- (motir-core) An org-scoped READ arm on `workspace` — the org's TRUE workspace count, readable inside a user-bound org transaction
- (motir-core) Hide the workspace-settings SURFACE at one workspace — fold Name / Members / Danger into org settings and 404 the area