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
- 需求
- 4
- 贊同
- 481
- 已規劃
- 5,576
- 已發布
- The sandbox guide never tells the reader to `docker pull` — `docker run` reuses a stale `:claude`, so anyone who followed it before 2026-08-05 is still on a CLI with no `motir login` while step 4 tells them to run itSelf-improvement — auto-reported quality bugs
- Mirror the two new gates into `SHARED_PLANNING_RULES` — the released-ref absence check and reproduce-before-you-call-it-broken, worded GENERICALLY because the shipped planner plans other people's productsSelf-improvement — auto-reported quality bugs
- Two in-process limiter Maps survive 8.5.9 — the upload and public-submit throttles are still `max × instances`
- 8.5.10 Move `/api/v1`'s rate-limit counter off the PER-PROCESS store onto the shared one — the ceiling is currently `limit × instances`
- PLANNING BUG — MOTIR-2611 measured only `main`, inferred the TAG's tree from that, and shipped the inference as a fact: every row of its evidence table was about the branch the defect could not be inSelf-improvement — auto-reported quality bugs
- 8.5.9 left the job-submitting `/api/ai/*` routes unlimited — the biggest spenders are still uncapped
- `main` does not compile — the project prop left the rail and one test still passes it, so every open PR is red on TypeScript
- The platform-admin mock's inlined token block aliases `--el-accent` to `--color-primary` where theme.css says `--color-primary-fill` — identical in the default palette, wrong in most others
- 8.5.9 App-level rate limiting on auth + public-write + AI endpoints (429 + Retry-After)
- 8.5.3 Wire lib/email.ts to the real email provider (transactional-email backend)
- 8.5.2 Provision transactional-email provider + authenticate motir.co sending domain
- 8.5.10 Design: the two day-1 operator panels the shipped platform-admin console defers — health glance + support action
- 8.5.1 Decide production service stack (email · monitoring · analytics · rate-limit)
- A receipt sat 0.8s under the watchable floor and only failed when an UNRELATED test in its file was edited — acceptance ownership is per-FILE, so a one-line edit republishes every story in it
- Every page under `/docs` publishes the API reference's `<title>` and description — the shell's `generateMetadata` is the only one in the tree, so the CLI, MCP and sandbox pages all announce themselves as "Motir API reference"
- PLANNING BUG — a card read a migration's stated INTENT as the database's enforced STATE, so "nothing needs to be created, only adopted" survived every gate
- The roles mock still DRAWS the two-fill checkbox its own notes deleted — panel 3 contradicts § A role is its name and its setPermissions — a permission catalog, custom project roles, and permission-gated UI
- Story E2E (Playwright) — an admin authors a role, puts someone on it, watches it bite, then deletes it with a reassign; and records the acceptance videoPermissions — a permission catalog, custom project roles, and permission-gated UI
- Story test gate (Vitest) — the coverage floor, the write→resolve seams, and the guards that stop a second role-writing pathPermissions — a permission catalog, custom project roles, and permission-gated UI
- Assigning a custom role — the Members picker, the `PATCH` that accepts a role definition, and the chip that names itPermissions — a permission catalog, custom project roles, and permission-gated UI