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-3308Done

Restate phase-deepen.md's 15 units in positive form, with a per-unit keep/migrate table

Rewrite the source pack so it says what to DO. The mirror and the lesson rows follow on sibling cards; this one owns the wording.

Go unit by unit. For each of the 15, decide keep (it is method — state it positively, 5-8 lines) or migrate (it is an incident — its body leaves, and a one-line prescriptive residue may stay if the method inside it is real). The four already known to be method: BOTH content axes, AC satisfiable inside the boundary, one update_plan_item per card, no shortcuts. The precondition-verification head is the fifth — name the preconditions this card leans on, verify each against shipped reality, cite where you checked — and its five limbs plus the asserted-absence limb and the context-ref gate are the migration candidates.

Write the table as you go, one row per unit: unit, keep or migrate, and for a keep the line count before and after. The table is the deliverable a reviewer actually reads — a 600-line prose diff is not auditable any other way, and the only question anyone will ask is what got dropped.

Do not delete a paragraph whose lesson row does not exist yet. The sibling card writes those; where they are not written, leave the text and mark the row pending rather than shipping a gap.

Acceptance criteria

  • All 15 units appear in the table with a keep/migrate disposition; the row count is 15.
  • Every kept unit is stated as an instruction — what to do, in the imperative — and carries no incident narrative, no fixture and no warrant tag.
  • The precondition head survives as a rule; its limbs are marked migrate with the target sourceRef named per limb.
  • phase-deepen.md's cautionary-register count is below 61 and its prescriptive count above 2, measured with the epic's script and both numbers quoted in the PR body.
  • No unit is marked migrate without a named destination row or an explicit pending.
  • The change lands via a branch and PR; no direct commit to main.

Context refs

  • motir-meta prompts/plan-rules/phase-deepen.md — the 15 units.
  • motir-meta prompts/plan-rules/CORPUS-MAINTENANCE.md — RULES vs LESSONS, the routing rule this executes.
  • motir-meta prompts/plan-rules/kind-container.md, type-code.md — the two packs already close to the target register, as models for the restated voice.
  • MOTIR-3305 — the backfill whose sourceRef list this card's migrate rows point into.