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
- 요청
- 4
- 추천
- 404
- 계획됨
- 4,190
- 출시됨
- (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
- (motir-core) The surfaces SAY IT HAPPENED ON GITHUB — the record band, the Development frame and the Approvals room name the GitHub reviewer, say when they are not a member, and show each pull request's review while the gate waits (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The WEBHOOK ARM — a `pull_request_review` delivery, submitted or dismissed, is recorded idempotently and evaluated; a pull request linked to no work item is ignored without errorApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) A review DECIDES THE SET — the evaluator approves the run target's gate only when every member's latest countable review at its current head approves, and requests changes on the first that does notApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The decide door takes a SYNCED actor — `approvalGatesService.decide` records a GitHub review with no Motir session: `decisionSource: github`, the resolved member or none, the login as the label, `github_review` authority, and a decided gate left standingApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The review SEAM — `parseReviewEvent` normalises a `pull_request_review` delivery and `getRepositoryPermission` reads whether a reviewer can write, both through `GitProvider`Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) SCHEMA — `github_pull_request_review` rows keyed on GitHub's review id, the repository leaf, and `github_review` joins `ApprovalGateAuthority`Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (manual) Subscribe the `motir-integration` App to the `pull_request_review` event, and read its event list back from GitHub's own APIApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) AMEND `approval-gates.md` for the GitHub review SYNC — every member approved at its current head by a writer decides the card's ONE gate AND merges it, changes requested on any member, the synced actor and its authority, first decision stands, nothing posted backApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- A GitHub approval SYNCS into Motir — every pull request approved on GitHub at its current commit decides the card's ONE approve-to-merge gate, so the card reaches `approved` and its pull requests merge, and the record names the reviewer even when they are not a memberApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Playwright acceptance E2E + VIDEO — red and running cards are visible on the board, the list and the Workbench, found by the *Checks* filter, and flip as a fix is pushed and goes green (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Story VITEST gate — the card-level CI state across link, pending, terminal and concurrent events on real Postgres, the filter and all projections agreeing, and the backfill convergingApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The CI BADGE on Workbench rows — `ciState` on `HomeWorkItemRowDto`, drawn through the shared badge and done-category rule on every tab (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The CI BADGE on board cards and `/items` List + Tree rows — `ciState` on `BoardCardDto`, `WorkItemListItemDto` and the tree node, one shared badge and one done-category rule (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join