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
- suggestions
- 4
- votes
- 458
- planifiés
- 4 424
- livrés
- `sprint:manage` — the sprint lifecycle, the backlog rank and a work item's sprint, with the sprint READS left at `project:browse`Permissions — a permission catalog, custom project roles, and permission-gated UI
- The eight keys enter the built-in role sets — and the 64-row parity table records exactly what each one takes awayPermissions — a permission catalog, custom project roles, and permission-gated UI
- DECISION — which built-in role holds each of the eight member-facing keys, and what a workspace member with no project membership keepsPermissions — a permission catalog, custom project roles, and permission-gated UI
- The nine rows no project permission can govern — the importer OAuth legs, the pre-auth idea draft, and the canvas layoutPermissions — a permission catalog, custom project roles, and permission-gated UI
- Close the ungoverned-operation gap — the member-facing permissions, and the gates the guard cannot confirmPermissions — a permission catalog, custom project roles, and permission-gated UI
- Mirror the request-COUNT precondition limb into `SHARED_PLANNING_RULES` — the shipped planner must refuse an uncited request budget tooPublic REST API — the versioned `/api/v1` integration surface every client shares
- `main` is RED — the roles design asset names four forward references the address guard rejects, and the `design/*` branch prefix skipped the guard that would have caught it
- Design — the Roles & permissions page: the read-only permission grid for the three built-in rolesPermissions — a permission catalog, custom project roles, and permission-gated UI
- Eight design-asset citations name repo source paths that do not resolve — `app/(authed)/board`, `components/plans`, `components/automation`, `PublicFrontDoor.tsx`, `story-6.16.ts`, `app/icon-<size>.png`
- (motir-core) `outputFileTracingExcludes` excludes nothing — the standalone artifact ships 181 MB of `design/`, and the config says otherwise
- `fly.toml`'s line-12 comment names the same non-existent Fly org — the one site outside `docs/` that still says `zhu-yue`
- (planning) A sibling's run DEFERRED work to MOTIR-2395 in a CODE COMMENT and never amended the card — the `grep every MOTIR-<n> you just wrote` discharge exists only for `design` assets
- CodeQL high alert #35 — the path-to-RegExp escape in `sandbox-truth.test.tsx` omits the backslash, and lands on innocent PRs
- Eleven design assets cite `app/(authed)/issues/**` source paths — a directory the work-item rename replaced with `items/`, and the address guard structurally cannot see it
- Thirteen design assets still address `/issues*` and `/login` — routes the app has not served since the work-item rename
- 8.3.5 Apply the brand mark across the app (shell / auth / email / public chrome / favicon-manifest / OG)Motir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- The guard's `KNOWN` table carries EIGHT duplicated rows — MOTIR-2348 and MOTIR-2370 fixed the same eight addresses in parallel and both merged
- (motir-ai) MIRROR-GAP — the CARDINALITY gate is the ONE per-card gate absent from `SHARED_PLANNING_RULES`: its repo corollaries crossed, its general "how many can there be?" trigger did not
- `main` is RED — the design-asset address guard fires on 8 pairs in `design/mcp-server/` + `design/cli-guide/`, which merged AFTER the guard and never added their `KNOWN` rows
- PLANNING BUG — MOTIR-2306 bundled two axes of very different tractability and sized BOTH from a one-directory sample, and its AC pointed at a token that cannot hold the values it was routingEpic 1: Foundation