Production method

One playable piece. One clear result.

A documented working loop for turning the Q&A into testable software, while keeping concept, implementation and acceptance separate.

1. Capture the design

   Record Briana’s questions, answers and corrections. Keep confirmed choices distinct from ideas and unresolved details.

   Output: a dated decision record.

2. Bound the next piece

   Choose a finite playable change and its completion condition. For the current slice: shared mining, placement, inventory and saved terrain.

   Output: scope that can be built and checked.

3. Implement the change

   Develop in the existing Unity project. Preserve unrelated work and keep server ownership of shared resources explicit.

   Output: source changes and a Windows build.

4. Run repeatable checks

   Test pure state rules, then actual network clients and restart behaviour. Visual captures and hands-on play answer different questions.

   Output: reports tied to the tested build.

5. Correct and re-run

   Investigate failures, preserve the earlier evidence and repeat the relevant checks after correction. A failed test is not silently called a pass.

   Output: corrected build plus new results.

6. Review the playable result

   Briana evaluates the experience. Automated passing checks establish their narrow assertions, not overall fun, accessibility or production readiness.

   Output: human feedback and a bounded next decision.

7. Document and hand off

   Update the current status, open issues and reproducible instructions. Prepare public pages separately from private source/logs.

   Output: reviewable local files; Portfolio Master handles publication.