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
- 528
- planned
- 5,567
- shipped
- (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 indexOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) Two concurrent first-workspace creates give ONE user TWO free orgs — the §4.5 org-creation gate takes no lock at all
- (motir-core) Eight more muted labels fail AA on a tint their COMPONENT never sees — the ink arm the widened scanner un-blinds, and the switch that turns it on
- Planning bug: MOTIR-2508 asserts "ONE PR, one file" in two criteria and then requires a second file in a third
- Planning bug: `motir run <id>` step 0a CLAIMED an archived card — `transition_status` does not reject one, and no gate before the worktree reads `archivedAt` or `readiness.ready`
- Planning bug: a STACKED design PR merged into its already-merged base branch, so its deliverable never reached main while the card read done
- Planning bug: MOTIR-3595 plans a cross-repo READ seam no card creates — "read the plan's proposals through core" has no producer
- Planning bug: MOTIR-3573's criteria asserted a violation the API cannot express — the input type was never read before two ACs were written about it
- Planning bug: MOTIR-3560 was sealed at 5 pts / 60 min carrying its OWN six enumerated deliverables — the sizing advisory is blind to a card whose numbers are present and wrong
- Planning bug: MOTIR-3557's AC 3 forbade a behaviour a shipped test deliberately guarantees — a criterion phrased as a NEGATIVE about rendered output carries an ungrepped code claim
- Planning bug: MOTIR-3487 claims an E2E lane 'already has every piece' from a sibling spec's SUBJECT — the spec seeds the ledger and its own header says the writer path has no seam
- Planning bug: MOTIR-3547 was sealed UN-SIZED at ~5h across three repos, and asserted a code fact read from ONE of a tool's TWO return channels
- Planning bug: the COLLAPSED supervisors run on Inngest between MOTIR-3417's merge and MOTIR-3489's flip, holding one invocation for the container's whole life
- Planning bug: MOTIR-3626 recorded the over-gate advisory as "REAL" and declined it IN WRITING — an advisory ACKNOWLEDGED is not an advisory DISCHARGED, and the acknowledgement makes the card read as careful
- (motir-core) Re-measure the fast lane on the engine and RECORD the figure — flip the honesty assertion, or say why it still standsOwn the job substrate — a Postgres-backed queue replaces Inngest, and the serverless-shaped stepping goes with it
- (motir-core) A free org CAN exceed its work-item cap — `lockByIdForUpdate` locks ZERO rows under `withWorkspaceContext`, and nobody reads the `false` it returns
- (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 card
- 8.39 A mock's nested-theme re-emit block, appended at the END of the stylesheet, CLOBBERS the concrete-hex `--el-*` its `[data-theme='dark']` block declares for dark only
- 8.4 (motir-core) The re-consent gate bounces every E2E `signIn` to /re-consent — the acceptance lane is RED on `main` and red-lights every open PR
- 8.38 The ink-contrast guards model tinted surfaces BY TOKEN NAME, so `--el-sidebar-bg` — an alias of `--el-surface` — is unmeasured, and six design assets fail AA on the rail