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) 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
- Planning bug: MOTIR-3371 turned "toHaveLength(1) passed, SO a second window opened" into an acceptance criterion — a second mechanism produces that presentation and reproduces 2 in 10
- Planning bug: the MID-SENTENCE WIDENING sweep is owed AGAIN — three packs red for the third time, so MOTIR-2966's remedy collects the debt without stopping it accruing
- Planning bug: an acceptance criterion demanded evidence from a substrate on the OTHER side of a service boundary — "asserted against a real database" for an HTTP seam
- Planning bug: a story scoped its population from where a corpus "STOPS" — but the coverage was a SET, not a prefix, so 44 entries below the boundary were invisible to every check
- Planning bug: a card forbade the only layer at which its own acceptance criterion was implementable — a prescribed layer is a CLAIM about that layer, and it owes the ADR check
- Planning bug: a test card's fixture table encoded axis semantics that contradict the three-axes-are-independent rule its own parent story states in prose
- Planning rule: NEVER reopen a `done` work item — plan forward, and log a bug or a new story instead