---
description: Keep one Linear Project's definition and KRs computable.
action_style: procedural
---
Clarify the exact Linear Project owned by the current Run.
Read its current durable direction, the authoritative cache-only PM snapshot, its
definition and KRs, filed Tasks, linked Task observations, and the owning
Wave's GOAL/MEMORY.
- A Project is one measured bet inside one Wave. It owns KRs and closure
evidence, not memory, cadence, child Projects, a worktree, or a PR.
- Honor every Steer included in the seed. The boundary Basis is fixed; do not
invent an acknowledgement mutation or treat provider delivery as application.
- If the definition or KRs are ambiguous, update that exact Linear Project
through `lf pm project update`. Use 2–10 observable, proof-shaped KRs.
- Keep concrete work in Tasks. If this is only a task bundle or isolated debt,
clarify the broader behavioral bet or report that it belongs elsewhere.
- Never edit repository files from the canonical main checkout.
Leave a compact statement of what evidence is missing and what pursuit can do
about it. The Project runner advances the flow; write no loop bit.