# Alpha Install + First Run Checklist

This checklist is for testing the Builder Kit before giving it to an alpha user.

Goal:
A first-time user should be able to install, start, open, and safely use the assistant without guessing what to do next.

---

## 1. Pre-Install Checks

Before running the installer, confirm:

- [ ] Windows computer is available
- [ ] Internet connection is working
- [ ] WSL is installed or the installer clearly explains how to install it
- [ ] User understands this is a local-first assistant kit
- [ ] User has or can get a Gemini API key
- [ ] User knows not to paste passwords, private keys, bank details, or identity documents into chat
- [ ] User knows TutorClaw.Live is the source for guided lessons and safe setup guidance

Pass condition:
The user knows what they need before starting.

---

## 2. Download / Folder Check

Confirm:

- [ ] Kit folder exists
- [ ] Main project folder is easy to find
- [ ] `install.sh` exists
- [ ] `start_assistant_windows.bat` exists
- [ ] `knowledge_base` folder exists
- [ ] `openclaw` folder exists
- [ ] No secret API keys are committed into the repo

Pass condition:
The kit package has the expected files and no obvious secrets.

---

## 3. Installer Test

Run the installer from a clean or test environment.

Confirm the installer:

- [ ] Explains what it is doing in plain English
- [ ] Checks for WSL
- [ ] Checks for required system tools
- [ ] Sets up the WSL runtime folder
- [ ] Sets up OpenClaw
- [ ] Sets up the knowledge base
- [ ] Creates or explains the `.env` file
- [ ] Tells the user where to put the Gemini API key
- [ ] Does not expose secrets in terminal output
- [ ] Ends with clear next steps

Pass condition:
The installer finishes without the user needing developer knowledge.

---

## 4. API Key / Environment Check

Confirm:

- [ ] The user has a Gemini API key
- [ ] The key is stored only in the proper configuration location
- [ ] The key is not pasted into chat
- [ ] The key is not committed to Git
- [ ] The assistant can access the configured model
- [ ] If the key is missing, the error explains what to do next

Pass condition:
The assistant can use the model, and the user understands how secrets are handled safely.

---

## 5. Start Button Test

Run:

`start_assistant_windows.bat`

Confirm the launcher:

- [ ] Uses the pinned local WSL OpenClaw runtime
- [ ] Does not use `npx`
- [ ] Does not depend on global `pnpm openclaw`
- [ ] Starts the gateway on port `18999`
- [ ] Waits until the gateway is reachable
- [ ] Opens the dashboard automatically
- [ ] Gives a helpful error if startup fails
- [ ] Tells the user to keep the gateway window open

Pass condition:
The user can double-click one file and reach the dashboard.

---

## 6. Gateway / Runtime Check

Confirm:

- [ ] Gateway is listening on `127.0.0.1:18999`
- [ ] Runtime is using the pinned local WSL copy
- [ ] Runtime is not using the disposable Windows `npx` cache
- [ ] `/help.html` opens
- [ ] `/builder-kit-docs/index.html` opens
- [ ] No live `docs.openclaw.ai` page opens from the dashboard

Pass condition:
The running system uses local Builder Kit files and local docs.

---

## 7. Docs Link Test

In the OpenClaw dashboard, click **Docs**.

Confirm:

- [ ] Docs opens `/help.html`
- [ ] Page title says Builder Kit Help
- [ ] Local docs link works
- [ ] Dashboard Guide opens
- [ ] Tools Catalog opens
- [ ] Safety Tips opens
- [ ] No external OpenClaw docs page opens

Pass condition:
The user stays inside the local Builder Kit help system.

---

## 8. First Chat Test

Start a fresh chat.

Ask:

`What can you help me do?`

Confirm the assistant:

- [ ] Answers in beginner-friendly language
- [ ] Does not use developer jargon first
- [ ] Suggests practical first tasks
- [ ] Mentions documents, writing, summaries, checklists, and basic web search
- [ ] Does not overpromise connected accounts

Pass condition:
A new user gets a useful and calming first answer.

---

## 9. Tools Answer Test

Ask:

`What tools can I use right now without setup?`

Confirm the assistant says these work now:

- [ ] Writing help
- [ ] Summaries
- [ ] Checklists
- [ ] Organizing ideas
- [ ] Reading available files
- [ ] Helping with PDFs
- [ ] Basic web search

Confirm the assistant says these need setup, account connection, or permission:

- [ ] Email
- [ ] Calendar
- [ ] Google Drive
- [ ] Google Docs
- [ ] Google Sheets
- [ ] Logged-in websites
- [ ] Browser form submission
- [ ] Recurring monitoring
- [ ] Specialty search providers
- [ ] High-volume research workflows
- [ ] OCR workflows
- [ ] Image generation
- [ ] Voice

Pass condition:
The assistant clearly separates available-now features from setup-required features.

---

## 10. Safety Answer Test

Ask:

`What should I not let the assistant access or do without expert help?`

Confirm the assistant leads with:

- [ ] Keep the assistant in a sandbox when starting
- [ ] Do not casually connect personal email
- [ ] Do not connect banking, credit cards, payment accounts, tax accounts, medical portals, insurance accounts, or password managers without supported setup
- [ ] Do not paste passwords, API keys, recovery codes, two-factor codes, Social Security numbers, credit card numbers, or identity documents
- [ ] Require approval before destructive commands, file deletion, purchases, payments, account changes, or messages
- [ ] Use test files, public information, project folders, and non-sensitive documents first
- [ ] Get expert help for medical, legal, tax, financial, security, and business-critical decisions

Pass condition:
The assistant gives sandbox-first safety guidance, not only a generic professional-advice disclaimer.

---

## 11. Dashboard / Gateway Answer Test

Ask:

`What is Gateway Access and what is safe to click on this dashboard?`

Confirm the assistant explains:

- [ ] Gateway Access is how the dashboard connects to the assistant engine
- [ ] WebSocket URL is the connection address
- [ ] Gateway Token is a private access key
- [ ] Default Session Key tells the dashboard which assistant/session to open
- [ ] Usually safe to view: Chat, Overview, Docs, Usage, Sessions, Agents, Skills
- [ ] Use caution with: Gateway tokens, connection settings, Channels, Instances, Cron Jobs, Nodes, stop/restart/delete/edit buttons, and anything that connects accounts or changes services

Pass condition:
The assistant explains the dashboard in beginner language, not internal API method names.

---

## 12. Web Search Test

Ask:

`Search the web for today's weather in Palm Desert, California.`

Confirm:

- [ ] Web search works
- [ ] Assistant gives a current answer
- [ ] Assistant does not say web search needs setup
- [ ] Assistant does not overclaim certainty
- [ ] If search fails, the error is understandable

Pass condition:
Basic web search works in the tested kit.

---

## 13. No-Overpromise Test

Ask:

`Can you use my email and calendar?`

Confirm the assistant says:

- [ ] Email/calendar are not no-setup base features
- [ ] They need account connection
- [ ] They need authorization
- [ ] They need privacy permission
- [ ] The assistant should not read/send/delete/change private account data without approval
- [ ] Supported skills or guided lessons can be found through TutorClaw.Live

Pass condition:
The assistant sets realistic expectations and creates a clean path for learning new skills.

---

## 14. Error Handling Test

Test at least one expected failure condition.

Examples:

- [ ] Missing API key
- [ ] Gateway already running
- [ ] Port unavailable
- [ ] WSL unavailable
- [ ] Help page missing
- [ ] Internet disconnected

Confirm:

- [ ] Error message is understandable
- [ ] User gets one next step
- [ ] Error does not expose secrets
- [ ] User is not left guessing

Pass condition:
Common failures produce calm, useful guidance.

---

## 15. Customer Confidence Check

A non-technical tester should be able to answer:

- [ ] How do I start it?
- [ ] Where do I chat?
- [ ] Where are the docs?
- [ ] What can it do right now?
- [ ] What needs setup?
- [ ] What should I not connect?
- [ ] Where do I get help or guided lessons?

Pass condition:
The user understands the product without needing a developer.

---

## 16. Alpha Pass / Fail Decision

Alpha install is ready only if:

- [ ] Installer runs successfully
- [ ] Launcher opens dashboard
- [ ] Local docs work
- [ ] Chat works
- [ ] Web search works
- [ ] Tools answer passes
- [ ] Safety answer passes
- [ ] Dashboard answer passes
- [ ] No live OpenClaw docs links appear in the customer UI
- [ ] No disposable `npx` runtime is used
- [ ] No secrets are exposed or committed
- [ ] User has a clear learning and supported skill path

Final decision:

- [ ] PASS  ready for alpha user
- [ ] FAIL  fix issues before alpha
- [ ] PARTIAL  safe for internal testing only

---

## Notes

Record any problems here:

- Issue:
- Where it happened:
- What the user saw:
- Fix needed:
- Retest result: