# macOS Builder and Runtime

This document describes how JackAILocal supports Mac users without changing the core product model.

## Product rule

The SaaS generates a builder package. The manifest is embedded in that package. The user does not manually select the manifest.

## Builder package contents

- `BUILD-USB-MAC.command`
- `macos/JackAILocal-USB-Builder.sh`
- `manifest/build-manifest.json`
- `webui/`
- `config/`
- `models/`
- `backends/`
- `bin/`

## Runtime package on the USB/SSD

- `START-HERE.command`
- `macos/Start-JackAILocal.sh`
- `macos/Stop-JackAILocal.sh`
- `config/jackailocal.macos.toml`
- `models/ollama/`
- `webui/`
- optional macOS `ollama` binary
- optional macOS `jackailocald` binary

## Backends

For Mac, backend priority should be:

1. Ollama for ease of use.
2. A local OpenAI-compatible `llama.cpp` server when explicitly supplied.

## Build command

```bash
./BUILD-LOCAL-MAC.command
./BUILD-USB-MAC.command
./BUILD-SSD-MAC.command
```

## Launch command on prepared USB/SSD

```bash
./START-HERE.command
```

## Commercial requirement

A production Mac product should be packaged as a signed and notarized `.app`. The `.command` files are acceptable for hackathon/MVP testing, not for a polished non-technical customer flow.