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
- solicitações
- 4
- votos
- 411
- planejadas
- 4.235
- entregues
- (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
- Disposition — `phase-author.md`, 43 clauses, the pack every authoring cell already pays forSelf-improvement — auto-reported quality bugs
- Disposition — `type-seam.md` + `type-runtime.md`, 32 clauses about composition contracts and deployment realitySelf-improvement — auto-reported quality bugs
- Disposition — `type-code.md` + `type-migration.md`, the 12 clauses where the whole story's yield is concentratedSelf-improvement — auto-reported quality bugs
- The clause INVENTORY and the four-disposition rubric — enumerate every `code`-reaching clause by command, then calibrate on 15 of themSelf-improvement — auto-reported quality bugs
- Sweep the rule corpus onto the SUBJECT axis — every `code`-reaching clause TRIMMED to its obligation, re-homed, DEMOTED to a lesson, or DELETED to a pointerSelf-improvement — auto-reported quality bugs
- Planning bug: a card that ADDS a member to a set a derived guard measures cannot be scoped apart from the member's token — MOTIR-5139 as drawn could not merge green
- (motir-core) Deciding an approval gate leaves the item page STALE — the status rail and the gate's own record band keep the pre-decision render until a reloadApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-ai) The story's gate — a tagged lesson is filtered IN and OUT correctly, an UNTAGGED one is returned for both, and an unconstrained query returns TODAY's candidate set unchangedSelf-improvement — auto-reported quality bugs
- (motir-core) `add_lesson` carries `subjects` — and the tool description's HOMES enumerated by a COMMAND pasted into the pull request, never a recalled countSelf-improvement — auto-reported quality bugs
- (motir-ai) The WRITE and READ wiring — `LessonAxes` and the `app.ts` parse carry `subjects`, the capture path records it, and the injection caller passes the cell's subjectSelf-improvement — auto-reported quality bugs
- (motir-ai) `subject String?` on `Lesson` — SINGULAR, unlike its three set-valued neighbours, and the read arm that keeps an untagged lesson universalSelf-improvement — auto-reported quality bugs
- (motir-ai) ADR amendment to `lesson-routing-axes.md` — the fourth axis is SCALAR and not an enum, and both departures follow from the ADR's own argumentsSelf-improvement — auto-reported quality bugs
- The lesson store gains the SUBJECT axis — SCALAR, on a filter-then-rank retrieval that already exists, so the two corpora keep ONE routing modelSelf-improvement — auto-reported quality bugs