| # JackAILocal Default Model Policy |
|
|
| JackAILocal must include the same product idea expressed in the referenced market discussion: the bundled models are a sensible default for general offline use, not the product boundary. |
|
|
| ## Required policy |
|
|
| 1. Ship or build a default model pack that works on a normal laptop. |
| 2. Do not market JackAILocal as only a single 9B model. |
| 3. Let users keep, remove, or add compatible models. |
| 4. The SaaS builder selects a model set from detected hardware. |
| 5. Normal USB insertion must not download models. |
| 6. Model downloads happen during factory preparation, customer build, model-add workflow, or signed update. |
| 7. The value proposition is the turnkey offline package: runtime, model policy, UI, diagnostics, support bundle, presets, and content packs. |
|
|
| ## Product wording |
|
|
| Use: |
|
|
| "JackAILocal ships with a practical offline default pack sized for normal laptops. It is not locked to that pack. The builder can prepare larger model sets when the target machine supports them." |
|
|
| Avoid: |
|
|
| "JackAILocal is a 9B model on a USB." |
|
|
| ## Hackathon rule |
|
|
| For the Hugging Face Build Small submission, keep all selectable models under or equal to the 32B parameter constraint. Avoid ambiguous models whose upstream card reports more than 32B parameters. |
|
|
