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
- 442
- planifiés
- 4 442
- livrés
- PLANNING BUG — 11.5 was decomposed by METHOD GROUP behind a "no command file" boundary, which cannot hold for a client portPublic REST API — the versioned `/api/v1` integration surface every client shares
- (motir-core) Raw / Tier-0 RADIUS escapes from the shape-swap layer are repo-wide — route them, then GUARD the radius axis like `swapLayerLint` guards colourEpic 1: Foundation
- The guard's gate pattern is a NAME WHITELIST — three privately-named gates are invisible, and three domain cards are sized against the opposite of the truthPermissions — a permission catalog, custom project roles, and permission-gated UI
- Story E2E (Playwright) — every settings page as an admin, then as a member: nothing an admin could do broke, nothing a member could do was takenPermissions — a permission catalog, custom project roles, and permission-gated UI
- Story test gate (Vitest) — the coverage floor, the route→service→gate seams, and the guards that stop a second policy implementationPermissions — a permission catalog, custom project roles, and permission-gated UI
- `ai:configure` — the project's AI-planning cadence and planner model (the settings write only, not the planner itself)Permissions — a permission catalog, custom project roles, and permission-gated UI
- `repository:manage` + `repository:manage_access` — the project's repository SET, and who may clone it (self-connect stays open)Permissions — a permission catalog, custom project roles, and permission-gated UI
- `field:manage` + `component:manage` + `label:manage` + `estimation:manage` — the four project vocabularies, with their READS left where they arePermissions — a permission catalog, custom project roles, and permission-gated UI
- `workflow:manage` + `automation:manage` — the statuses a column projects, the automation rules, and the status-derivation switchesPermissions — a permission catalog, custom project roles, and permission-gated UI
- `board:configure` — the boards, their columns, swimlanes and WIP limits (and NOT the card drag, which stays `work_item:edit`)Permissions — a permission catalog, custom project roles, and permission-gated UI
- `member:manage` + `project:manage_access` — and the second admin check `projectMembersService` re-implements privatelyPermissions — a permission catalog, custom project roles, and permission-gated UI
- Retire `repository:connect` — the provider connection binds an installation to a WORKSPACE, so no project permission can govern itPermissions — a permission catalog, custom project roles, and permission-gated UI
- `assertPermission` — one gate per catalog key, its typed refusal, and the twelve administrative keys entering the built-in role setsPermissions — a permission catalog, custom project roles, and permission-gated UI
- Per-domain administrative permissions — split `project:administer` so a role can hold one settings domain without the restPermissions — a permission catalog, custom project roles, and permission-gated UI
- A route rename updates the code, the tests and the E2E — and silently leaves the design asset of record two generations stale, with no guard
- 8.3.2 Final logomark approval (brand-designer / founder decision)Motir's public web presence — one host per audience, and an open-core line through motir-core (motir.co · app.motir.co)
- PLANNING BUG — three domain cards were sized on "ungated", and the gates were there and TIGHTER; the guard's name whitelist produced the inversionPermissions — a permission catalog, custom project roles, and permission-gated UI
- (motir-core) `ChildList`'s row radius is a raw `rounded-md` — a Tier-0 escape the shape-swap rule forbids
- `lib/apiDocs/sandbox.ts` sits at 50% branch coverage against its own ≥90% gate — the `docs/*` CI skip meant the branch that introduced it never ran the coverage job
- 11.5.13 Decision, then implement — does a `/api/v1` collection row embed a minimal ACTOR object? (the ready row's assignee, `targetRepo`, and `excludeIds` without an internal id)Public REST API — the versioned `/api/v1` integration surface every client shares