1.9 KiB
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.
-
Current E1 scope follows the standing continue-work authorization relayed in Slack
1794651141.035699and Claude caps1794651169.320839: bounded CPU-only label-free preparation and synthetic checks may proceed after the count checkpoint, without another user approval loop. Total 16 CPU-hours / 25 GiB, at most 8 processes, per-job 30 min / 1.25 GiB tree RSS, at most 2000 registration pairs; the 10-part stage additionally stays sequential within 3 h / 5 GiB. Never read labels, fit models, use GPU, run pilot/full matrix, or exceed caps in this scope. Seedocs/s2-e1-budget-checkpoint-2026-11-14.md.