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
- 415
- planifiés
- 4 223
- livrés
- (motir-core) The folder SERVICE — create, rename, move, reorder and delete-moves-contents-up, and filing a work item into or out of a folder, each gated on `work_item:edit`Folders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) SCHEMA — the `folder` table and `work_item.folderId`: migration, RLS policy pair, parent-XOR-folder CHECK, same-project trigger, and both Prisma relationsFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- A person tidies the project tree into folders — create, name, nest, reorder and delete folders in `/items`, and move any work item into and out of themFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) The approval DECIDE door's escape hatch is a ROLE — only a workspace owner/admin can decide a gate they were not routed, so no custom role (and not even a project Admin) can ever take that responsibility over
- (motir-meta) `run.md` stops telling every run that a pull request's CI runs the full suite and the coverage gate — the PR runs the affected subset, the merge queue runs the restSelf-improvement — auto-reported quality bugs
- (motir-core) On a pull request the Vitest legs run only the affected files, with a force-full path set that fails open; the merge queue keeps the full suite and takes the coverage gateSelf-improvement — auto-reported quality bugs
- (motir-core) Gate the `cli`, `orchestrator` and `design-system` lanes on their own package paths — the `changes` classifier emits one flag per package, as `app-shell-over-packages.md` §1.4 requiresSelf-improvement — auto-reported quality bugs
- (motir-core) MEASURE what `vitest --changed` would select on real pull-request diffs, and find the tests its import graph cannot see — recorded as the decision that amends `merge-queue.md` §3Self-improvement — auto-reported quality bugs
- (motir-core) A pull request runs the tests its diff can reach — package lanes gated by path, the Vitest lane narrowed to the affected files, and the merge queue keeps the full gateSelf-improvement — auto-reported quality bugs
- (motir-core) The saved-filter "admin" tier is a ROLE — seeing and managing other people's filters is `owner||admin` or project role `admin`, so no custom role can ever be granted it, and the permission guard whitelists it by name
- (motir-core) The Approvals room opens to every project browser — `approvals` declares `viewPermission: 'project:browse'`, its READ takes the view key, its switch reads the WRITE key off the registry, and the "a member is offered no settings area" suites are amended on the recordApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The gate record band's `Files kept` line has no in-browser path either — and once MOTIR-5212 makes the rail optimistic it becomes the SOLE detector of a lost RSC apply, on a 5 s budget
- (motir-core) The Sentry PROJECT PICKER — choose which of the grant's projects to monitor: filter, locked rows, multi-bind with a per-row partial result, and the degraded pickerProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The story's E2E — connect, list, degrade and disconnect in the browser against the fake provider, recorded as the acceptance videoProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The story's VITEST gate — the coverage floor over the connection surface, the writer→consumer seams the units mock, and the guards coverage cannot seeProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The `Monitoring` settings room — the rail entry, the grant and its rows, the degraded row with re-check, disconnect with confirmation, the return banners, loading / error, and both localesProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The credential STAYS ALIVE, or says it is broken — the eight-hourly token refresh, the on-demand health probe, and the stored `degraded` verdictProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) CONNECT and DISCONNECT — the grant exchange, verify-install, the connection service and its routes, behind a new `integration:manage` permissionProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The `MonitorProvider` seam and its FIRST implementation — the Sentry adapter, plus the fake provider the suite runs againstProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) The monitor-connection SET — schema, migration, RLS and repository for a project's bound monitored projects and their encrypted credentialProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back