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
- 514
- planned
- 5,093
- shipped
- (motir-core) Register `acceptance_result` as a gate KIND — the enum row + migration, the handler and the renderer, raised on the STORY whatever the run target, and the bespoke acceptance flip retires into the contractApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The FOUR SEAM callers that mint without their repository — the reconcile worker among them, whose per-pass token cache is keyed on the installation aloneApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- The ACCEPTANCE-VIDEO gate — a story's receipt becomes a decision ON THE STORY in the ONE approve language, and on a story run it leads a double gate whose one press also merges the story's codeApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The plan-review read carries each proposal's FOLDER TRAIL — `folderTrail: { id, name }[]`, root first, for its own folder or its root-most committed ancestor's, from one batched read
- (motir-core) E2E — folders on both planning canvases: the root draws folder cards and no filed item, a folder drills to its folders then its items, a folder-filed proposal is drawn where the design places it, and the folder crumb navigates back
- (motir-core) The plan-review canvas (`PlanReviewCanvas`, `/plans/[id]`) draws FOLDERS — the folder read at the root, a folder's own level, the empty-folder state and the navigable folder crumb, with folder-filed proposals placed as the design settles
- (motir-core) The plan-change overlay canvas (`PlanChangeCanvas`) draws FOLDERS — the folder read at the root, a folder's own level, the empty-folder state and the navigable folder crumb, with folder-filed proposals placed as the design settles
- 40 (motir-core) The planning canvases never draw a FOLDER — MOTIR-5710 opted `/roadmap` into the folder read, and the planning overlay (`PlanChangeCanvas`) and plan review (`PlanReviewCanvas`) still draw every filed item loose at the root
- (motir-core) The `Failed jobs` health signal counts dead letters over a 24-HOUR window, so 1,381 standing unreplayed rows render as a green `0 dead-lettered · 24h`
- 42 (motir-core) A LOST check completion strands a green pull request at `ci: running` for ever — every reconcile path skips a set that still holds a pending row, so the card never reaches In Review and no approve-to-merge gate is ever raised
- (motir-core) The pull-request webhook's changed-path capture mints through the user-facing App for a HOSTED repository, so a hosted repository's pull requests never record their pathsApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) RUN the CI-state backfill on PRODUCTION — dry run, read the counts, apply, re-run dry, and record all three on this cardApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) A required integration secret can be absent from the deployment with nothing detecting it — `SENTRY_APP_CLIENT_SECRET` was missing for 7 days after MOTIR-5257 recorded it set, and only a human clicking Connect would ever have found out
- (motir-core) Story E2E — a planning bug filed through the marker appears in the tree INSIDE its folder, with no parent cardSelf-improvement — auto-reported quality bugs
- (motir-core) Story gate — integration vitest across the whole seam: pointer set → marker resolves → bug FILED into the folder → folder deleted → pointer carried upSelf-improvement — auto-reported quality bugs
- (motir-meta) The corpus stops calling the planner-bug home a STORY — `run.md`, `log-bug.md`, `kind-bug.md`, `core.md` gate 15, `plan-procedure.md`, `_shared.md`Self-improvement — auto-reported quality bugs
- (motir-core) MIGRATION — adopt the `Planning bugs` folder, point the project at it, move every home-story child into it, and ARCHIVE the storySelf-improvement — auto-reported quality bugs
- (motir-core) The RESOLVER — `@planner-bug-home` resolves to a FOLDER, `fileBug` FILES instead of parenting, and the not-provisioned 500 retires for a fallbackSelf-improvement — auto-reported quality bugs
- (motir-core) Deleting the destination folder carries the PLANNER-BUG pointer up too — `deleteFolder`’s carry-up covers BOTH pointers, not oneSelf-improvement — auto-reported quality bugs
- (motir-core) SCHEMA — the project’s nullable PLANNER-BUG destination folder pointer, its migration, its tenancy trigger and its indexSelf-improvement — auto-reported quality bugs