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
- 588
- planned
- 5,392
- shipped
- (motir-core) The ACCEPTANCE gate's decision has the same missing server half as MOTIR-5118 — and nothing anywhere asserts its status surface repaints in place
- Planning bug: `MIRROR.map.py --check` has been RED on `origin/main` since the SUBJECT axis landed — its twin parser only recognises a backtick template literal, so it exits before comparing a single unit
- Planning bug: `MIRROR.check.py` assertion 5 has been RED since the SUBJECT axis landed — four packs that did not exist at the baseline carry 6 cautionary / 0 prescriptive markers, and the register guard has no owner
- Planning bug: `core.md`'s gate index routes gate 13 to `phase-author.md`, which carries none of the artifact-obtainable gate — MOTIR-4382 moved it to `type-runtime.md` and the index was not swept
- Planning bug: `core.md`'s gate index routes gates 4 and 20 to `phase-author.md`, but THE ESTIMATION GATE is 101 lines in `type-runtime.md` — which 8 of the 14 author cells never load
- (motir-core) The story's E2E — land on `?tab=approvals`, decide a routed gate, and watch the strip count and the list agree in ONE refresh (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The story's INTEGRATION test — the routing predicate's NEGATIVE case, an access fixture whose population differs from the reader's view, count-vs-list, and the pager at a boundaryApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The APPROVALS TAB on the Workbench — the rows, the composed approval control, the strip count, and the nothing-awaits-you state (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The pending-approvals READ — every open gate awaiting THIS person in the active project, with the subject each row is about, access-gated server-side and pagedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- The Approvals tab — every decision waiting on YOU, in one place on the WorkbenchApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Story E2E + acceptance video — a person walks a card In Review → Approved → Done, and watches the board, the counts and the parent agree that approved is not shippedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Story coverage + integration gate — the refused hop, the rollup that must not complete, the dependent that stays blocked, and OPEN proven per surface rather than inferred from the categoryApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The APPROVED chip — the Pill tone, the CircleCheck glyph, and the canvas's SEVENTH tintApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) `approved` is a LADDER RUNG, not just a category — the sixth rung between In Review and Done, the third resolved lifecycle key, the container-claim bar, and the §3 amendmentApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The `approved` status — the constants, its three declared transitions, the seed, the two labels, and the backfill that adds the status, its edges and a board column to every existing default-workflow projectApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- A person's YES is a STATUS — `approved` joins the workflow between `in_review` and `done`, in the in-progress categoryApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-ai) MIRROR the swept corpus into `SHARED_PLANNING_RULES` — gate 19's second home, clause by clause, with every removal accounted forSelf-improvement — auto-reported quality bugs
- (motir-ai) PERFORM the DEMOTES — every demoted clause into the lesson store with its SUBJECT, scope decided per clause, after a dedup against what is already thereSelf-improvement — auto-reported quality bugs
- (motir-meta) PERFORM the MOVES and DELETES — trim into the member packs, delete the convention index to its pointer, and SWEEP EVERY REFERRERSelf-improvement — auto-reported quality bugs
- Disposition — `core.md`, 25 clauses in 873 lines, the pack EVERY cell loadsSelf-improvement — auto-reported quality bugs