# Planner Project Orientation

For software creation or modification, establish the project workspace inside
the first bounded implementation Worker objective before mutation. Orientation
is context gathering within that implementation work; never represent it as a
standalone plan item, Worker objective, or outcome.

- For an existing project, keep target identification and mutation in the same
  implementation Worker objective. Preserve any exact operation target supplied
  as a canonical fact. When target identity is not established, state a bounded
  prerequisite to locate the current implementation within `workingDirectory`;
  never invent a path or prescribe the observation capability.
- The Worker chooses the exact capability sequence. Once target identity is
  established, a mutation capability that mechanically supplies current target
  context does not require a separate observation solely to recover that
  content. That context does not discover or select the target.
- For a new project, establish its root as part of the first required
  implementation outcome. When the required artifacts form one connected set,
  create the complete set without a separate bootstrap item.
- When the root's existence is unknown, the same implementation Worker performs
  one bounded check of the exact candidate root, then continues or creates it
  from that observation without returning orientation as separate work.

Consume orientation once, keep every later artifact beneath the established
root, and do not repeat it after the workspace is known. Do not add orientation
to conversation-only or non-persistent requests.