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
- 요청
- 4
- 추천
- 373
- 계획됨
- 4,134
- 출시됨
- (motir-core) After a merge-queue CONFLICT is fixed by a push, the re-asked gate's pull-request row still reads "cannot land" — the approval members read counts a queue exit from the OLD head as standing
- (motir-core) A shape advisory for a BODY-ONLY edit sitting above a field move — the fields and the prose contradict and nothing validates that
- (motir-ai) A global lesson still tells authors to find ordering violations by scanning for merge/release/deploy WORDS, the lexical test MOTIR-5426 measured at about 1 in 9
- (motir-meta) run.md's parent run ends on a design stopper without re-reading its gate — an approval that lands mid-run leaves the released chain unbuilt until someone re-runs
- 41 (motir-core) On the plan-review canvas the breadcrumb runs UNDER the top-right search box — from the third crumb on, "Search this plan" covers the crumbs and swallows their clicks
- (motir-core) A COUNTED claim about a card's own blockers is checkable against the graph — `likely-missing-edge` reads keys, and "all four", "every member", "the siblings this card is blocked_by" carry none
- (motir-ai) The `laidLevel` removal note carries a false count as its REASON — "30+ test files drive `lay` and `propose_node` together" measured 57 files that MENTION both; 7 drive both, and the sweep it justified cost nothing
- (motir-core) A reference advisory over PATHS — a criterion naming a sibling’s unbuilt file is a missing blocked_by that no key-based detector can see
- (motir-meta) REGISTER.count.py --ref reads TODAY’s pack set at an OLD commit — the ratchet’s historical arm raises on every ref before the newest pack
- (motir-core) Approving a DESIGN or DECISION primary that also merges draws no per-row outcome on its pull requests — the frame counts the merge set out of the primary's own version, which is not a set
- (motir-core) A scoped `motir run <story>` dispatches a `decision` child onto the SESSION pull request, so approving that decision can merge the whole story's code
- 35 (motir-core) A plan that DELETES the only `cross` edge into a card leaves that edge's ghost anchor standing on the review canvas — `mergePlanLevel` subtracts the dep from `deps` but passes the anchor node through `committed.nodes`
- 38 (motir-meta) The runbook's guard halts say "nothing claims or dispatches a Blocked card" — `blocked` is in the `todo` category both claim doors take, and the halt's edge exists only on the unapproved plan, so a halted card is ready and claimable for the whole review
- (motir-meta) run.md's parent run has no rule for a DECISION child — its gate needs a pull request that delivers the decision card, and linking the story's PR to it would let the decision's approval merge the whole story
- (motir-meta) MIRROR.md goes RED the moment MOTIR-2963 merges — retire the W8 IN-FLIGHT rows and record the one new ranking-artifact pairing
- (motir-core) Approving a story's acceptance video in the approval overlay leaves the pull-request rows beneath it unchanged — the overlay never hands the frame the merge gate's version, so it counts zero members
- Self-improvement — auto-reported quality bugs
- (motir-ai) Mirror W8 into `SHARED_PLANNING_RULES` — a decision's close-out asks BOTH directions, and its *Consumed by* header is the inward worklistSelf-improvement — auto-reported quality bugs
- How to test shows a per-commit "Stale · Written for <sha> — <repo> is now at <sha>" line, but the record belongs to the work item — and no run is told to refresh it after a new commit
- Declining a plan leaves a hand-parked target at Planning — it should rest at To do / Blocked, as approving does