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
- Anfragen
- 0
- Stimmen
- 369
- geplant
- 4.052
- ausgeliefert
- (motir-core) The hosting ADR, `.env.example` and the index-fleet ADR still say production `MOTIR_AI_URL` is `http://motir-ai.internal:8080`, and it is the public origin since motir-ai's pool started suspending
- (motir-core) Story E2E — the `/pages` tree: folder, page, sub-page; drag and Move up/down; the sidebar tree and breadcrumb; a refused move; folder delete; a viewer read-only — recorded as the paced acceptance videoPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) Story VITEST gate — the coverage floor over the tree's package and app modules, the move / subtree-rewrite / folder-delete seams on real Postgres, concurrent moves, and RLS isolationPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) DRAG-AND-DROP in the `/pages` tree — reorder among pages and drop onto a folder, page or the root, with the drop target shown and a refused drop snapping backPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The page's PLACE on its own route — the sidebar tree with the page selected and its ancestors expanded, and the folder › page breadcrumb replacing "← Pages"Pages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) MOVING in the `/pages` tree — Move to… (folder, page or root), Move up / Move down, each refusal shown, and folder rows' New folder / Rename / Move / Delete from the shared folder commandsPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The `/pages` TREE — folder and page rows, lazy expand and load-more per level, New page / New page here / New sub-page, and its empty, loading, error and read-only statesPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The page TREE ROUTES — the level read, create with a parent, and the move route, with every tree refusal mapped to its HTTP statusPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) A FOLDER holds PAGES too — `deleteFolder` moves its pages up, and the folder level / contents counts and the delete dialog count pagesPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) `pagesService` tree — create under a parent, `movePage` in one transaction, the `/pages` tree level (folders then pages, keyset paged) and the page's trail for its breadcrumbPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) Page PLACEMENT in `pageRepository` and the `PageStore` adapter — per-parent sibling locks and positions, the subtree read and ancestor rewrite, folder lookup, and the keyset level read of a parent's pagesPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) MOVE and PLACE in `@motir/pages` — create under a page or folder, the `movePage` procedure with cycle, depth and cross-project refusals, and the `PageStore` placement portPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- Pages in the project tree — a `/pages` tree of folders and pages, sub-pages, filing into the shared folders, moving and reordering, and the page's own sidebar tree and breadcrumbPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- PrismaClientKnownRequestError:
- PrismaClientKnownRequestError:
- PrismaClientKnownRequestError:
- PrismaClientKnownRequestError: Transaction API error: A commit cannot be executed on an expired transaction. The timeout for this transaction was 5000 ms, however 5108 ms passed since the start of th…
- PrismaClientKnownRequestError:
- PrismaClientKnownRequestError: Transaction API error: Unable to start a transaction in the given time.
- PrismaClientKnownRequestError: Transaction API error: Unable to start a transaction in the given time.