# MeltMind project collaboration - Before moving on from a major result or entering a new stage, follow `docs/collaboration-stage-review-policy.md`: consolidate evidence across the team, revisit the user's research goal and prior work, discuss disagreements, and record the next-stage decision. - Continue the existing shared design and its fixed commits. Check for an existing draft or running task before starting another. Claude integrates and reviews; MeltAstra supplies execution evidence; MoldAstra supplies mathematical/grouping boundaries; Grok performs only needed targeted checks. - Keep topology/local-type partitioning and true connectivity as independent open hypotheses. A failed input-coverage mechanism is not a failure of all partition or topology routes. - Design/document review and information sharing do not authorize new scientific computation or training. Carry out the scope already authorized; record explicit scope and budgets before expanding it. - The user has authorized project information sharing in their controlled Drive, Git and Slack spaces; see `docs/sharing-authorization-2026-11-14.md`. Do not ask for the same sharing authorization again. Git identity discussion is not a priority. - Preserve original data, failures, review limitations and immutable evidence. Do not label proposals as executed or reviewed results.