# Project start: goals, structure and durable knowledge

Use this once when nobrainer-tech-flow first enters a project, and revisit only
when the relevant facts change.

1. Read the actual tree, maintained architecture and nearest instructions.
   Identify the layers the project already has. Recommend a missing layer only
   when an acceptance need justifies its cost; do not scaffold by default.
2. Read the owner's current long-term direction or roadmap when supplied.
   Derive one short-term outcome, acceptance and next milestone for substantial
   work. Keep the full agreed outcome visible; accepting a milestone does not
   silently close the larger goal. Set the outcome and DoD as a native goal when
   the host supports one and its tool contract allows it.
3. Discover an existing project or global wiki from instructions and local
   evidence. Query only relevant decisions, brand facts, lessons and sources.
   Ask once when the correct wiki boundary is material and not settled.
   Reuse the current wiki when it fits. If no wiki exists and durable
   cross-task knowledge justifies one, recommend a project wiki and create it
   only through `nobrainer-wiki` SETUP within established authorization.
4. When the resolved wiki is global, record its verified path or portable
   discovery rule in the supported client instructions. Do not invent a
   machine path, expose restricted content or store transient task state there.