Skip to content

moooon

Motir

Vibe your whole 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
1
requests
0
upvotes
145
planned
1,361
shipped

Motir · Work items

MOTIR-4088To Do

(motir-meta) Retire the limb from `plan-rules/phase-skeleton.md` — the RUNBOOK planner's copy

prompts/plan-rules/phase-skeleton.md:49 carries the same no-lift limb:

⚠️ AND WHEN NO LIFT IS LEGAL, WIRE THE LEAF EDGE AND RECORD THE REASON ON …

This is the runbook planner's copy — a different reader from motir-ai's packs, which is why both carry it and why this is a second card rather than a mirror sweep ([[planner-rule-corpora-dont-mirror]]).

The correction

A blocked_by is always between siblings of the same kind under the same parent. A cross-parent need is lifted — the dependency, or the card itself. There is no case where no lift is legal; the three the limb enumerates are symptoms of a mis-shaped tree, and each has a real answer:

  1. the lift would be too coarse ⇒ the cards are in the wrong places — lift the CARD
  2. the lift makes a cycle ⇒ the cycle is the planning error — fix the structure
  3. only one child needs it ⇒ the container is doing two jobs — split it

⚠️ Answer them; do not merely delete the escape hatch. A runbook planner meeting case 2 with no guidance will invent something, and inventing is what the limb was there to prevent.

Acceptance criteria

  • grep -rain "no lift is legal\|cannot be lifted\|wire the leaf edge" prompts/ returns nothing.
  • The invariant is stated without an exception, and the three cases are answered with what to do instead.
  • The rest of the rule is untouched — the chain / fan / same-level shapes are correct.
  • Any REGISTER / clause-count or corpus-measurement artefact that counts this file is updated in the same change, so a deletion does not leave a count that no longer matches.
  • ⚠️ Branch + PR, never a direct commit to main — the standing rule for this repo.

Scope BOUNDARY

  • IN: phase-skeleton.md's limb and the guidance replacing it, plus any counter this file feeds.
  • OUT: motir-ai — the pack and the seeded lesson are MOTIR-4087's. Different planner, different repo, one subtask each.
  • OUT: the VALIDATORMOTIR-4086's named follow-on.
  • OUT: re-wording anything else in this file. One rule, one correction.

Context refs

  • motir-meta prompts/plan-rules/phase-skeleton.md :49 — the limb.
  • motir-meta prompts/plan-rules/REGISTER.count.py · COMPRESSION.measure.py — the counters that may read this file.
  • MOTIR-4086 — the diagnosis, and why a blocked_by is always same-level.