BUILDGOBLIN — FEATURE-TO-BUILD LAB
Preview 0.1 | Windows x64 | Unity 6000.3.17f1

Start with GUIDE.html. It opens locally in your browser.

WHAT THIS IS
A small original firing-range project and an AI-assisted development exercise,
with readable checks for a native Windows build. It is a worked example, not a
complete game-studio agent, Unity certification or a guarantee about your game.

FAST PATH
1. Extract the entire archive to a local folder. Do not run inside the ZIP.
2. In the source-only preview, first build using BUILD FROM SOURCE below and
   seal the build. Then open Build/BuildGoblin.exe to play. Click a target,
   reload, and pause. A source-only archive does not include an executable.
3. Open PowerShell in this folder and run:
   & ./tools/Verify-Build.ps1 -IncludeSeededFaults
4. Read Evidence/latest-summary.json and the associated run reports.
5. Open SampleProject using Unity 6000.3.17f1 for the guided code exercise.

EXPECTED RESULT
none: PASS
pause: EXPECTED FAILURE DETECTED
input: EXPECTED FAILURE DETECTED

The intentionally broken scenarios are included to prove the checker notices
the declared failures. They are not bugs in the reference scenario.

REQUIREMENTS
Windows x64. PowerShell 7 (tested on 7.6.9). Windows PowerShell 5.1 was not
qualified. A graphics-capable machine that runs Unity
6 Windows players. Source editing/building requires your own activated Unity
6000.3.17f1 Editor and Windows build support. AI usage is optional and supplied
by your own coding-agent account. No API subscription or credits are included.
No Python or Node installation is needed for the buyer's verifier.

SCRIPT TRUST
Read tools/*.ps1 before running them. They hash the supplied Build folder,
launch its player with synthetic-test arguments, and write Evidence next to it.
They do not install services or change Windows security policy. If Windows
blocks a downloaded script, review it before unblocking the individual trusted
file (Properties > Unblock). Do not disable system-wide protections.

BUILD FROM SOURCE
Open SampleProject in the stated Editor. Use BuildGoblin > 2 - Build Windows
sample. This regenerates the supplied sample scene; don't use that menu to
overwrite an unrelated scene with unsaved work. Output is the sibling Build
folder. In PowerShell run ./tools/Seal-Build.ps1, then Verify-Build.ps1.
Sealing records the files you just built. Never reseal an unexplained modified
download merely to silence a mismatch.

LIMITS
The 12 automated checks use synthetic commands through the sample's gameplay
path. They do not certify physical keyboards/controllers, visual quality,
networking, unrelated mechanics, or compatibility with another project.
Hashes detect accidental changes relative to a manifest; a manifest packaged
with files is not a cryptographic publisher signature or a defense against an
attacker replacing both. Keep your trusted baseline separately.

SUPPORT
This is a pre-release validation build. No commercial support response-time
promise is in force yet. Keep reports local; don't send full projects or keys.
Before submitting a report, remove local usernames/paths from logs.

Read LICENSES.txt for source and third-party terms.