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
- solicitudes
- 4
- votos
- 442
- planificados
- 4442
- publicados
- PLANNING BUG — MOTIR-2279 was filed twice wrong: a deliberate omission called an oversight, and a cross-story dependency hung off the epic instead of a story-level edgePublic REST API — the versioned `/api/v1` integration surface every client shares
- The permission guards are RED on `main` — an inline object type in a parameter hides the gate, and one route is missing from the inventoryPermissions — a permission catalog, custom project roles, and permission-gated UI
- 8.3.1 Design — Motir brand mark (logomark + wordmark + favicon/app-icon + dark variant + OG template)Motir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- `/api/v1` ADVERTISES its contract version on every response — an `x-motir-api-version` header, so a client's skew gate costs nothingPublic REST API — the versioned `/api/v1` integration surface every client shares
- The no-ungoverned-operation guard — fail the build when an actor-initiated write reaches the DB with no permission gatePermissions — a permission catalog, custom project roles, and permission-gated UI
- Grow the catalog to the inventory — the full key set, its domains, and the `enforcement` markerPermissions — a permission catalog, custom project roles, and permission-gated UI
- `projectAccessService.getPermissions` — resolve an actor's permission set for a project in one round trip, and its DTOPermissions — a permission catalog, custom project roles, and permission-gated UI
- Built-in roles as permission SETS + `hasPermission` — re-express every predicate in `lib/projects/access.ts`, proven behaviour-neutral by a truth tablePermissions — a permission catalog, custom project roles, and permission-gated UI
- The permission CATALOG — `lib/permissions/catalog.ts`, its domain groups, and the totality guards that keep it honestPermissions — a permission catalog, custom project roles, and permission-gated UI
- The OPERATION INVENTORY — enumerate every gated operation in the product and map it to a permissionPermissions — a permission catalog, custom project roles, and permission-gated UI
- The permission MODEL — a catalog derived from the real operation surface, and a role becomes a permission SETPermissions — a permission catalog, custom project roles, and permission-gated UI
- 11.6.8 End-to-end conformance — drive BOTH live surfaces over real HTTP against the same rows and assert the payloads agreePublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.6.7 Story vitest gate — coverage floor, the DTO→schema→payload seams, and the guards the alignment owesPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.6.6 The DRIFT GUARD in CI — a field added on one surface and forgotten on the other fails the buildPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.6.5 Re-base the WORK-LOOP tools onto 11.7's schemas, and SEAL the exemption listPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.6.4 Re-base the PROJECT, SPRINT, BACKLOG and IDENTITY tools onto the shared schemasPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.6.3 Re-base the WORK-ITEM family onto the shared schemas — the reads that carried the founding defect, plus every write that returns an itemPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.6.2 The shared-schema seam + the TOTALITY mechanism in `toolOk` — proven on `get_work_item`, with the exemption registryPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.6.1 Decision — overturn the recorded no-`outputSchema` choice, pin where the shared schemas live, the zod v3→v4 boundary into `lib/mcp`, the totality mechanism, and the exemption listPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.6 MCP tool payloads derive from the v1 response schemas — the two surfaces cannot driftPublic REST API — the versioned `/api/v1` integration surface every client shares