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
- 賛成票
- 380
- 計画済み
- 4,121
- リリース済み
- (motir-core) `backlog.test.tsx`'s EDITOR_ONLY case waits for the SPRINT header, then reads the BACKLOG's Create row synchronously — a race that ejected an unrelated PR from the merge queue
- (motir-core) `gatedSurfacesStoryGate`'s VIEWER case waits for the BOARD, then asserts on the BACKLOG — a race that ejected an unrelated PR from the merge queue, and its absence checks can pass vacuously
- (motir-gateway) A catalog refresh whose providers changed their lists can never go green — the generator needs two passes, a newly listed id arrives with an unsourced hand price, and ~20 tests are pinned to today's real models
- (motir-gateway) The catalog refresh regenerates from the COMPILED-IN provider listings, not the ones it just wrote — every run whose listing moved commits generated files that disagree with it, and its own PR fails TestGeneratedFilesAreUpToDate
- (motir-core · design) The permission-gated rule for the surfaces its table does not rule on — a list or tree inline cell, the inline estimate badge, and the Resume-onboarding door, for an actor who cannot writeRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core) The planning surface does not refresh a plan's HELD state when the rewrite was started elsewhere — its verbs stay enabled until the reader navigates, and the press is then refused
- (motir-core) The item page's pull-request LINK and UNLINK assert no permission key — a browse-only actor links or unlinks a PR (and withdraws its merge gate) by calling the action directly; only the MCP tool's copy checks `work_item:edit`
- Q5's `plan_submitted` finding is probably never recorded for a real dispatched refusal: the leg is settled `replanned` and the run closed before the plan reaches `planned`
- (motir-gateway) The derived allowlist intersects on native id, so a model the provider and OpenRouter name DIFFERENTLY is invisible to both sides — `deepseek-flash` vs `deepseek-v4.1-flash`, reported in no section
- (motir-gateway) The catalog-refresh E2E golden AGES — `pricecheckOffline` pins `-read-on` but not `-asof`, so the provenance table's `age` column counts from the wall clock and `TestCase1ANewsDayProducesTheBodyAReviewerReads` fails on `main` every day after it was recorded
- (motir-core · design) The Mine / Project tabs on Plans, Approvals and Runs — the tab strip, each tab's empty state, the Project-only room for a reader who cannot act, the Mine-only room for one without the view key, and the nav door that hides a room with neitherRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core · test) The story's E2E — a Viewer and a Member walk the work item, quick view, board, list, tree, Approvals, Plans, Runs and settings, and the Viewer meets no write control and no empty roomRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core · test) The story's INTEGRATION gate — each gated surface rendered as a Viewer and as a Member against the real resolver, the coverage floor over the changed surfaces, and nothing a Member could do taken awayRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core · test) The GUARD — a CI test that fails when a control that writes renders for an actor without its permission key, naming the file and the key, at zero from day oneRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core) Navigation offers no room closed to the actor — sidebar, command palette, reports and settings doors gated on the key that opens them, for every gap the inventory listsRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core) The board, list, tree, backlog and sprint surfaces offer no write to a read-only actor — create, inline edit, drag, bulk actions and row menus gated to the rule, for every gap the inventory listsRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core) The work item page and quick view offer no editor an actor cannot use — every field picker, links, labels, watchers, to-dos and custom fields read-only with the reason, closing the MOTIR-4822 pathRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core) The gating INVENTORY — every page under app/(authed) and every control that writes, with the key it needs, the treatment the permission-gated UI rule gives it, and whether it follows the rule todayRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- Every surface offers a role only what it can use — a scan of each page and control against the actor's permissions, the gaps fixed to the permission-gated UI rule, and a guard that keeps new surfaces honestRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- Code and test comments cite MOTIR-6033's plan-decide design as "Part XX §20.N" — in the ai-planning notes that resolves to the DIFFICULTY design; it landed as Part XXII