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
- 6
- requests
- 4
- upvotes
- 597
- planned
- 5,376
- shipped
- (motir-core) Story vitest gate — the coverage floor, the backfill on a populated database, the provenance matrix including MIXED, and the establish → DTO → control seamApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The SETTING in Project settings → Approvals — two merge modes in the reader's words, manage-only like the roomApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-meta) `prompts/` cites `subtask_pr_merge_mode` at FIVE sites — gate 14 axis (c) in `core.md`, its twin in `phase-author.md`, and three runbook steps in `run.md` — the citation moves to `Project.prMergeMode`Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The READERS move off `Workspace` — `ProjectDTO.prMergeMode`, the read/write service, the workspace DTO losing the field, and every prose comment that cites the old nameApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The provenance DEFAULT at ESTABLISHMENT — all-Motir-hosted seeds `auto`; imported, MIXED and empty seed `manual`Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) SCHEMA — `Project.prMergeMode`, the `SubtaskPrMergeMode` → `PrMergeMode` enum rename, and the backfill from every workspace's current valueApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The ADR §7 AS-BUILT amendment — WHEN the provenance default is seeded, what a MIXED project gets, and why the workspace column's retirement left this storyApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- `prMergeMode` — the merge setting is renamed off `subtask`, moves to the PROJECT, defaults by repository PROVENANCE, and becomes something a person can find and changeApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- 8.89 (motir-core) `design/shell/context-row` still DRAWS the retired no-project tier — Panel C's third column and Panel E, against a design-notes section that says there are two states
- 2200.37 (motir-core) Every entitlement-cap refusal reaches a `zh` reader in ENGLISH — `EntitlementExceededError` builds its own message, and all five consumers surface that string verbatim
- Planning bug: MOTIR-5060 inferred "the majority go silently GREEN" from a count of `expect(length).toBeGreaterThan(0)` guards — the measured majority goes RED (35/40), and the card's own three sampled files are all in the red set
- Planning bug: MOTIR-4898 asked the runner to CHOOSE between two options on a mechanism it had never observed — no case in that file records `locale`, and one probe run falsifies it
- Planning bug: MOTIR-4413's AC 5 forbade what its AC 1 required — a "tests pass unchanged" clause on a card whose deliverable is a new field on an output that eleven `toEqual`s pin
- Planning bug: MOTIR-4375's children asserted THREE fields that do not exist — a 12-property body that has 14, a catalogue `examples` field, and a 4-key grant that has 6
- Planning bug: a bug card asserted a check "does not have one" three days after the check merged — the negative was never grepped, and the card cites the shipping story's own sibling
- Planning bug: MOTIR-5295 told the run to gate a new MCP tool on one key and "let the service's role check decide" — which would have handed a narrowed token its owner's moderation reach
- Planning bug: a pass that LAYS SEVERAL cards searched the lesson store ONCE, so the rarest risk in the set — a destructive migration with a recorded three-phase protocol — was never ranked for
- Planning bug: a card BLOCKED BY a design pre-specified that design's OUTPUT as its own acceptance criteria — so the design's arrival read as a wording nit, and the card sat at exactly the over-sizing threshold
- Planning bug: an acceptance criterion asked a run to open author sessions "only for the proposals the request touches" — nothing on the seed can carry that, because the sessions open before the model says what it is touching
- Planning bug: the dispatched agent's re-plan door was planned as a CLI shell-out, while every other instruction in the SAME protocol is an MCP tool call