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
- richieste
- 4
- voti
- 468
- pianificate
- 4366
- rilasciate
- Planning bug: an incident card was authored from a single reconciliation read, and its own two printed timestamps disproved it — the remediation steps would have deleted a live customer's billing entity
- Planning bug: a TERMINAL card's blocked_by set is written once and never re-derived, so every sibling filed after it leaves the card reading `ready: true` while definitionally un-runnable
- A parent is STRANDED when its child finishes faster than derivation runs — the aggregate jumps to all-done and `todo → done` has no edge
- (nextjs-prisma-vercel-starter) The starter's acceptance lane has the same trigger blind spot MOTIR-2760 fixed in motir-core — every scaffolded project inherits it
- Planning bug: a card's FIX DIRECTION carries the authority of its root-cause evidence without the method — MOTIR-2763 mis-counted its referrer set (2 of 4) and named a test lane that cannot mount the element under test
- Nothing in the shell reserves clearance under the floating "M" orb — at the end of a scrolled page it covers the `/items` pager and `/home`'s Next, and both stop being clickable
- Planning bug: the `validate_work_item` post-condition is bound to a PLAN PASS, so no card created mid-run is ever checked by the mechanism built to catch exactly this — MOTIR-2011's family, ×7
- Planning bug: a test card's worked EXAMPLE contradicted the rung table its own story had just written
- `reconcile:orgs` reported a LIVE customer organization as unknown — the lookup cannot tell a current motir-core from a 22-day-old snapshot, and its report reads as an instruction to delete
- An APPROVAL racing a publish lands on a row the publish then supersedes — the same receipt loss through the other door (`decide` takes no lock)
- The acceptance-video lane is paths-filtered to the SPEC files, so an app change can break every acceptance spec and no PR runs them — the breakage waits for whoever next touches a spec
- The gateway honours run-attribution from ANY token — it must be trusted only on the motir-ai token the gateway itself minted
- Nothing in the database checks a work item's parent TENANCY — so the kind / depth / cycle triggers' in-context premise rests on the service check they exist to backstop
- Planning bug: a dedup card offered two owners for one write and neither option carried the ADR that one of them was gated by — and its criteria named one of the two collisions
- The `/home` landing surface lists DONE work — neither read carries a lifecycle predicate, so the page whose own copy says "waiting on you" is 87% finished items
- Planning bug: a card that NAMED its own blocker in prose and NAMED its own open decisions still shipped with no `blocked_by` edge and an acceptance criterion nobody could evaluate — the diagnosis was right and none of it was wired
- (motir-meta) Every pack's generated header still claims "VERBATIM … verify.py proves it" — false in four packs, and the split's own DO-NOT-EDIT banner blocks fixing it by handSelf-improvement — auto-reported quality bugs
- `workflowsService`'s READ SURFACE is unbound too — after the cutover the board renders no columns and every status picker is empty
- `core.md`'s 620-line cap has no room for the cross-reference index the split made necessary — and the pays-for-itself mechanism is unavailable to any card forbidden from editing `fixtures/`
- (motir-core) The sandbox digest table is transcribed BY HAND every release — the lane already computes the exact markdown rows and writes them somewhere only a human can reach