Ask Fish
User sends one normal chat/API request.

Flow
User sends one normal chat/API request.
Fish chooses the best available route.
The request shows what it used.
The UI says how the answer was made.
Active route
Demo answers stay inside the local app process.
Proof tag
Marked as a demo estimate so nobody confuses it with provider work.
Local answer for the first version.
No outside provider is called.
Demo usage record.
Real AI through an outside provider.
Outside provider policy applies.
Outside AI usage record.
Selected Ocean providers run jobs.
Provider terms and Fish routing policy apply.
Signed provider proof.
Ocean provider with reviewed privacy rules.
Provider commits to no prompt/output retention.
Policy review plus usage records.
Controlled runner with tighter isolation.
Runner-level storage and access controls.
Runner logs without raw prompt text.
Hardware-backed route much later.
Hardware-backed execution boundary.
Hardware proof plus provider proof.
Harbor rules
Demo, outside AI, and Ocean provider work must be labeled differently.
Fish must not claim Ocean routing until selected providers run jobs.
Usage records keep hashes, costs, and provider ids, not raw prompts or outputs.
Outside AI can help launch, but that provider's privacy policy applies.