<aside> 💻

Document purpose: Make ISAC's first five minutes simple, memorable and understandable to non-technical users.

Document status: Architecture/design specification. Current implementation status is controlled by the roadmap and stage evidence.

</aside>

Initial Interface

The first interface should be a polished terminal. The terminal is the initial frontend rather than ISAC itself, allowing desktop, web, mobile and voice interfaces to be added later without changing the underlying system.

First-Run Flow

1. Start ISAC and initialise GCF.
2. Detect hardware and calculate the safe resource envelope.
3. Offer optional application scan.
4. Show inferred user/capability profile and allow confirm/edit/discard.
5. Recommend local model layout and optional Knowledge Vault content.
6. Download, verify, install and benchmark approved models with user approval.
7. Configure encrypted memory and recovery/2FA options.
8. Offer voice/accessibility setup.
9. Offer BYOK/custom provider setup.
10. Transition directly into the normal ISAC conversation.

Application Scan

Local, transparent, optional and reviewable. By default inspect installed app/tool names and runtimes, not personal documents, browser history, messages or passwords.

Normal vs Advanced

Normal users should never need to understand LLMs, quantisation, VRAM, GCF or API endpoints. Advanced controls remain available behind an explicit advanced path.

Setup Experience

Setup should feel like ISAC's first structured interaction with the person and the machine rather than a conventional installer wizard.