Gigio Project Setup

Keep the project's purpose, direction, constraints, current understanding, and next important question available to later sessions. A project is an objective, not necessarily a Git repository. Its code, data, experiments, documents, and live jobs may span several locations.

Recover the context

Inspect the existing intent document, project instructions, relevant decisions, current results, and resource locations. Reuse an equivalent maintained document instead of introducing a competing PROJECT.md. Ask only for missing user judgments that materially change the setup.

Separate user decisions from observations and agent proposals. Preserve the user's wording for goals and important limits where available; a useful synthesis may connect those statements without upgrading an inference into consent. Do not require a failure anecdote, a fixed number of pillars, or a negated definition for every goal.

Write the smallest useful project record

Use PROJECT.md, or the project's existing equivalent, for two kinds of content:

• User-owned direction: why the work matters, the question or outcome being pursued, priorities, meaningful exclusions, constraints, and the choices the user has settled. Mark this section clearly. A change of direction needs the user's decision; a previously accepted grant does not need repeating.
• Maintained understanding: what the work currently supports, important competing explanations, what has not been established, relevant abandoned approaches and why, the next decision, and links to the results that matter. Update this digest during authorized work without asking the user to approve every observation. Findings may challenge a decision; they do not silently replace it.

Give each material decision a concise reason and its source. Supersede outdated entries rather than making an old result look current. Record uncertainty where it affects the next action, not as a mandatory label on every sentence.