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
- solicitações
- 4
- votos
- 462
- planejadas
- 4.328
- entregues
- (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
- (motir-core) Org add joins the org's SOLE workspace — the count-1 arm §5 and §6 never reconciled
- 14 Progressive disclosure is half-shipped at ONE workspace — the workspace-settings surface is still exposed, and an org invite lands the invitee in ZERO workspaces with no way in
- Planning bug: a card was sealed carrying a heading that said "split it", and criteria duplicating a still-open operator card's DNS records — where the duplicate would have BROKEN the card that owns them
- Planning bug: a card RELOCATED a surface without checking that its destination is reachable by everyone the source was
- Planning bug: a card specified a write + its guarding read inside an existing transaction without checking that the transaction's SECURITY BINDING admits either
- Planning bug: MOTIR-3462 asks an E2E to assert same-key idempotency on a journey that mints a FRESH key each time — the criterion cannot be run at all
- Planning bug: MOTIR-3455's evidence grep was never RUN — it reports 3 files where its own named ref returns 19
- Planning bug: a defect was verified against `origin/main` and filed 47 minutes after the card fixing it went `implemented` — the pre-flight never searched the PLAN
- Planning bug: two of MOTIR-3451's acceptance criteria were never RUN before they were written — one quotes markup the file has never carried, the other asserts an output that was already false
- Planning bug: run.md says a card at `todo` is structurally safe from a PR naming it — the sync WALKS the hops, and a one-criterion PR closed a four-criterion card
- Planning bug: MOTIR-3264 imported a suspend delay measured on OTHER endpoints and stated it as its own subject's property — in the title, while its body correctly forbade exactly that
- Planning bug: a bug card's MECHANISM was taken from an untested code comment, and three candidate fixes were planned off it
- Planning bug: MOTIR-3274 closed `done` on criteria written over ONE project while its own Context refs named a SECOND consumer — the credential meant to unblock MOTIR-3264 cannot reach the gateway