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
- 588
- planned
- 5,171
- shipped
- (motir-core) Design delta — the Monitoring room learns INGESTION: a per-connection minimum level, the last poll's outcome on each row, and a poll failure that names itselfProduction 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 · design) The How-to-test FORM — Add and Edit doors, the rich-text body with code-block language, the preview path, the repository sections, refusals, Written by {person}, history of both kindsApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-meta) `run.md` publishes a design result ONCE, in the PARENT flow only — no amend/republish limb anywhere, and the LEAF flow has no publish step at all
- (motir-meta) `run.md`'s how-to-test rule carries TWO triggers — a parent run that ends at a STOPPER satisfies *before it finishes* by breaking *before the PR is marked ready*
- (motir-core · design) WHAT LIVE LOOKS LIKE — a row arriving, a count moving, reconnecting, the settled row that must NOT vanish, and the open approval that learns its subject movedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Story E2E — the built CLI dispatches a card waiting on an approved design and its agent finds the files in `$MOTIR_DESIGN_DIR`; `--print` names the fetch; a card waiting on an unapproved design is told to stopApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Story vitest gate — the coverage floor over the story's changed surface, the approve → read → prompt → v1 → CLI seams on real Postgres, and the guards a percentage cannot seeApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-ai) `THE_DESIGN_GATE` carries the same words — the published design result is the asset and a repository copy is optional, the twin of the pack editApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-meta) The runbook and the rule packs read the design from Motir — the design-reference rule, guard #3's run-time gate with propose-beside-and-relate, `_shared.md`'s source-of-truth row, and the precondition ladder's design clauseApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The dispatched prompt's DESIGN REFERENCE — the designs the card waits on, where their files are or how to fetch them, and the run-time design gate routed through THE CARD IS WRONG; `CLAUDE.md` stops naming the repository as the source of truthApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) `motir run` writes the approved design into the run's own directory and hands the agent `$MOTIR_DESIGN_DIR` — all or nothing, gone when the run endsApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The `get_design` and `list_designs` MCP tools — payloads derived from the v1 design component, on `project:browse`, and the design-evidence exemption reasons that stop being trueApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The `/api/v1` design operations — a work item's approved designs, one design card's approved design, and a project's approved-design list, with the design component in the emitted spec and the CLI types regeneratedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The approved-design READ — `designAccessService` resolves the approved design of each design card a work item waits on, lists and gets approved designs by key or path, and mints short-lived download links, one query per readApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Decision — `design-result.md` AMENDMENT 5: the published result is the design's source of truth, what "approved" means to a run, the version an agent is handed, what a run gets by default and where, and the run-time design gateApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- EVERY AGENT RUN IS HANDED THE APPROVED DESIGN IT BUILDS AGAINST — read from Motir, not from a repository: the design reference in the dispatched prompt, the files in the CLI run's directory, the MCP and v1 read doors, and the run-time design gateApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) A SYNCED approval MERGES THE SET — the decision a review made runs the same merge-or-enqueue path an *Approve and merge* press runs, per member, after the decision commitsApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The Development block's READ carries each pull request's GitHub review at its current head — the latest countable state, the reviewer's login, and whether a Motir memberApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Playwright acceptance E2E + VIDEO — signed review deliveries approve one pull request then the other, the card reaches Approved and both pull requests merge, an unmapped reviewer is named as not a member, and changes requested on GitHub is recordedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Story VITEST gate — the coverage floor over the sync, the delivery → review row → evaluator → synced decision → MERGE seam on real Postgres, and the guard that nothing posts a review to GitHubApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join