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
- verzoeken
- 4
- upvotes
- 392
- gepland
- 4.211
- uitgebracht
- (motir-core) Approve MATERIALIZES folder placements — an `add` created filed, a `modify` re-parent that clears the other placement, and a folder deleted since the append refusing the approve by nameFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-ai) Story vitest GATE — coverage floor over the folder-aware tree reads and proposal executors, and the seam from a grounded folder set through `propose_node` to the `plan-proposals` payloadFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) Story E2E (Playwright) + ACCEPTANCE VIDEO — an integration files work into a folder over `/api/v1`, an agent proposes a card into a folder over the MCP, and a reviewer sees the folder on the plan and approves it into `/items`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) Story vitest GATE — coverage floor over the folder API, MCP and proposal surface, the service → route → tool → materialize seams, and the guards that every folder code is mapped and every folder tool is documentedFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-ai) `SHARED_PLANNING_RULES` name a folder as a PLACEMENT, not a parent kind — THE MOTIR GRAMMAR and the reconcile rule, with the conservation, routing and register baselines holdingFolders — 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 plan review SHOWS where a card will be filed — folder crumbs on the canvas and the list, a move into or out of a folder under Show changes, and the stale-folder stateFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-meta) The runbook names folders as a place work is filed — `plan-procedure.md`'s ladder, `_shared.md`'s `move_to_parent` and proposal-`parentRef` notes, and `log-bug.md`'s forward ladder, beside the shipped planner's grammarFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-ai) The planner PROPOSES into a folder — `folder:<id>` accepted by `propose_node`, `author` and `place_node`, validated against the grounded folder set, and passed through the registry, author sessions and revise passFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) A plan READS its folder placements — the review model's folder trail, `get_plan` grouping under the folder path, and `folderPath` on the `/api/v1` plan proposalFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) Plan proposals may NAME a folder — `folder:<id>` accepted as an `add`'s `parentRef`, a `modify`'s `patch.parentRef` and `update_plan_proposal`'s, validated at append on the MCP and internal doorsFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) MCP work-item tools PLACE into folders — `create_work_item` and `move_to_parent` take a `folderId`, and `get_work_item` declares `folderId` + `folderPath` instead of leaking the id through a spreadFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) `/api/v1` work items report and take a FOLDER — `folderId` + `folderPath` on the detail read, `folderId` on create and PATCH refused beside `parentKey`, and `motir show` printing the folderFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-ai) The planner READS folders — `folderId` and the folder set on its tree reads and grounding, `docs/contract.md` §6, the skeleton tool rendering a filed item's path, and `contextualScope` reading placement off skeleton rowsFolders — 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 planner's TREE READ carries folders — `PlanTreeSkeletonItem.folderId` and a `folders` list on `readPlanTree`, served by MCP `skeleton` and the internal `plan-tree` / `skeleton` / `get-subtree` routesFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) MCP FOLDER TOOLS — `list_folders`, `create_folder`, `update_folder`, `delete_folder`: permissions, registry, tool-doc catalogue, `docs/mcp.md`, generated schemas, and folder refusals as typed tool errorsFolders — 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 `/api/v1` FOLDERS resource — list a level (keyset-paged), create, rename / move / reorder, delete with contents moved up; every folder refusal mapped to its status and code; OpenAPI operations and the contract versionFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) PLACEMENT in the service — `createWorkItem` takes a `folderId`, a re-parent through `updateWorkItem` clears the folder instead of tripping the XOR CHECK, and one placement rule that lets a filed subtask be a rootFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- Agents and integrations file into folders — `/api/v1` and MCP folder doors, folders on `skeleton`, and plans that propose into a folder with the reviewer seeing where each card landsFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) Turning the acceptance video on still fails to repaint ~1 press in 16 WITH the server half in place — and the trace excludes the MOTIR-5118 race
- (platform, manual) Raise the `motir-integration` GitHub App to `contents: write` and re-consent its installations — merging a pull request needs it, and the granted set is read back from the App's own APIApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join