Spaces:
Sleeping
Sleeping
| # Builder ZIP Auto-Capture Policy | |
| The user must not manually extract a manifest ZIP, find a JSON file, or pass command-line arguments. | |
| ## Correct SaaS output | |
| The Gradio/SaaS layer should generate a platform-specific builder package: | |
| - `JackAILocal-Windows-Builder.zip` | |
| - `JackAILocal-macOS-Builder.zip` | |
| Each builder ZIP contains: | |
| - the build manifest already embedded under `manifest/build-manifest.json` | |
| - the one-click builder script for the target OS | |
| - the runtime template | |
| - the UI | |
| - the config | |
| - the model policy | |
| ## Correct user flow | |
| 1. Download builder ZIP. | |
| 2. Open/extract ZIP. | |
| 3. Insert USB/SSD. | |
| 4. Double-click the builder. | |
| 5. Confirm target drive. | |
| 6. Wait. | |
| 7. Launch JackAILocal from the prepared USB/SSD. | |
| ## Incorrect user flow | |
| - Download manifest ZIP. | |
| - Extract manifest manually. | |
| - Copy JSON into another folder. | |
| - Run PowerShell with a manifest path. | |
| - Understand model IDs. | |
| - Understand runtime folders. | |
| The manifest exists, but it is an internal input to the builder, not a user-facing artifact. | |