The prototype is the pitch.

The prototype demonstrates the self-hosted serving pattern — open weights behind an authenticated API, data on-prem. The model behind the router is a configuration change, not an architecture change.

The production recommendation is a non-Chinese frontier model (Mistral Large 4 class) for the sovereignty and licensing posture the entry argues for — the serving stack doesn't care which weights it loads.

• Nuclear — procedures, licensing docs, and engineering analysis that public AI tools are barred from touching.
• Cyber pentesting — recon analysis and payload research where a data leak ends careers.
• CII-restricted operations — grid/OT-adjacent data under handling obligations no cloud API can satisfy.

The value isn't cheaper tokens — it's AI eligibility for the workloads where a leak invites regulatory scrutiny.

API access is key-gated. Request a key through the contact on the competition entry — then:

copycurl https://api.fordmorris.com/v1/chat/completions \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "stable",
       "messages": [{"role": "user",
                     "content": "Hello from the judges"}]}'