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
- suggestions
- 4
- votes
- 398
- planifiés
- 4 179
- livrés
- (motir-core) A merge-queue FAILURE at the pull request's current head folds into the card's `ciState` as `failing` — one shared predicate with the promotion hold, recomputed on the exit and on Queue againApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- An EJECTED card reads RED — the card's Checks badge counts a failed merge-queue exit, and `motir fix` claims a card the queue threw out for failed checks or a conflictApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) A request that imports ONE job definition leaves the emit path with a PARTIAL manifest — `ensureJobManifestLoaded` short-circuits on it, and every other event is silently dropped for the life of that module layerProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The story's E2E — completing a monitor-filed bug resolves its fake issue once and the next poll changes nothing, the switch turns it off, an assignment arrives, a failure shows on the row — recorded as the acceptance videoProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The story's VITEST gate — the coverage floor over the sync surface, the done → resolve → poll seam end to end through the fake on real Postgres, and the guards coverage cannot seeProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The Monitoring room shows SYNC — both direction switches on each row, the failed resolve-back line, and both localesProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The DIRECTION SWITCHES write — `setSyncDirections` under `integration:manage`, the connection PATCH accepting both switches, and the view DTO carrying them and the last sync failureProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) ASSIGNEE FROM THE MONITOR — a provider-side assignment becomes the bug's assignee by email match, on every reconcile visit and a bounded per-poll refresh of open links; team or unmatched is a recorded no-opProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The LOOP GUARD — the reconciler treats an issue Motir itself resolved, and has not seen since, as already reconciled, so resolve → poll never re-files or mutates the bugProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) RESOLVE BACK — a bug reaching a done-category status resolves each linked issue once, as a job off `work-item/transitioned`; a failure lands on the connection, and a deleted issue says so on the cardProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The provider seam reads ONE issue and its ASSIGNEE — `getIssue`, the normalized assignee on every issue, a deleted issue as a typed answer on read and resolve, and the fake honours all threeProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The sync STORE — the connection's two direction switches and last sync failure, and each `monitor_issue` link's resolve record and last-synced assignee, with its migration and repositoriesProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- Fixing the bug closes the error — resolution and assignee sync back to the monitor, configurable per directionProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) An ON Switch's track is under 3:1 against the page in the amber, citrine and candy light palettes — `--el-switch-on` on `--el-page-bg` is 1.80 / 1.47 / 1.57:1
- (motir-core · design) `motir fix` BESIDE *Queue again* on an ejected card — which one to use, and the card badge reusing *Checks failing* — a delta of `github--fix-callout.mock.html`Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) DELETE the repository sub-block from How to test — the read, the DTO, the block and both catalogsApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The Switch primitive's OFF knob is invisible against its own track — `--el-switch-knob` on `--el-muted` is 1.01:1 light and 1.00:1 dark, where WCAG 1.4.11 needs 3:1
- (motir-core · design) github--how-to-test-form.mock.html opens with a stray <p> BEFORE <!doctype> — the board renders in quirks mode
- (motir-core) A design card with an open pull request shows TWO rows in To approve — the queue lists every `awaiting` gate, so the design gate AND the merge gate it carries each appear, count twice, and the merge row can be pressed on its own
- (motir-ai) The DB-backed lesson suites run an O(corpus) seed under vitest's 5s DEFAULT — 299 rows, one embedding round-trip each, and the corpus only grows