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
- prośby
- 4
- głosy
- 442
- zaplanowane
- 4442
- wydane
- 11.5.1 Decision — the CLI's v1 client contract: the type generator, where runtime validation happens, how the generated artifact stays fresh, the skew comparison, and the adapter boundaryPublic REST API — the versioned `/api/v1` integration surface every client shares
- Public REST API — the versioned `/api/v1` integration surface every client shares
- 11.5 `@motir/cli` migrates onto `/api/v1` — generated types replace the hand-mirrored interfacesPublic REST API — the versioned `/api/v1` integration surface every client shares
- The no-ungoverned-operation walk reads a RETURN TYPE's braces as the method body — and never follows a `this.` hop
- Story E2E (Playwright) — a viewer, a member and an admin walk the same four flows and are refused in exactly the right placesPermissions — a permission catalog, custom project roles, and permission-gated UI
- Story test gate (Vitest) — the coverage floor, the route→service→gate seams, and the guard that stops a second policy pathPermissions — a permission catalog, custom project roles, and permission-gated UI
- The unconfirmed gates (2/2) — the four public reads, the three ready-set routes and the two upload endpointsPermissions — a permission catalog, custom project roles, and permission-gated UI
- The unconfirmed gates (1/2) — the nine work-item, watcher and mention paths the inventory calls `existing` and the walk cannot seePermissions — a permission catalog, custom project roles, and permission-gated UI
- `ai:view_plan` — reading a generated plan, and the approve / decline / proposal-edit that turn it into work itemsPermissions — a permission catalog, custom project roles, and permission-gated UI
- The coding-convention four — the ONE row in this story that would LOOSEN a gate, decided rather than swept alongPermissions — a permission catalog, custom project roles, and permission-gated UI
- (motir-ai) `GET /v1/jobs/:id` and its stream become TENANT-SCOPED — a job that is not the caller's project's is a 404Permissions — a permission catalog, custom project roles, and permission-gated UI
- `ai:plan` (4/4) — the job status and the eight streams, which today read ANY job by its id alonePermissions — a permission catalog, custom project roles, and permission-gated UI
- `ai:plan` (3/4) — generation, sprint planning, the pre-plan read and the AI-access probePermissions — a permission catalog, custom project roles, and permission-gated UI
- `ai:plan` (2/4) — the plan-editing jobs: augment, expand, replan, the explanation drafter and the per-item plannerPermissions — a permission catalog, custom project roles, and permission-gated UI
- The model is fully enforced — `PLANNED_PERMISSIONS` empties, the guard's PENDING arm is deleted, and the inventory closesPermissions — a permission catalog, custom project roles, and permission-gated UI
- `ai:plan` (1/4) — the conversational planners: the discovery chat and the plan-change sessionPermissions — a permission catalog, custom project roles, and permission-gated UI
- `work_item:triage` + `work_item:delete` — accepting an inbound request, and destroying a subtree, stop being the same permission as editing a fieldPermissions — a permission catalog, custom project roles, and permission-gated UI
- `import:run` — the five project-scoped importer operations move from `work_item:edit` to an admin-only keyPermissions — a permission catalog, custom project roles, and permission-gated UI
- `saved_filter:manage` — authoring, owning, starring and subscribing to a project's saved queriesPermissions — a permission catalog, custom project roles, and permission-gated UI
- `report:view` — the roadmap, the velocity and the six analytics reads, plus the three sprint analytics the sprint card hands overPermissions — a permission catalog, custom project roles, and permission-gated UI