# Alpha Install Checklist Summary

Use this summary when the user asks for the alpha checklist, first-run checklist, installer checklist, or launch readiness checklist.

For the full detailed checklist, use:

`knowledge_base/alpha_install_first_run_checklist.md`

---

## Quick Alpha Checklist

Before giving the Builder Kit to an alpha user, confirm these areas:

1. Pre-install checks
   - Windows computer
   - Internet connection
   - WSL available or clearly explained
   - Gemini API key available
   - User understands not to paste passwords, private keys, banking details, or identity documents

2. Download and folder check
   - Kit folder exists
   - `install.sh` exists
   - `start_assistant_windows.bat` exists
   - `knowledge_base` exists
   - `openclaw` exists
   - no secrets are committed

3. Installer test
   - Installer explains what it is doing
   - checks WSL and required tools
   - sets up the WSL runtime folder
   - sets up OpenClaw and the knowledge base
   - explains where the Gemini API key goes
   - ends with clear next steps

4. API key and environment check
   - key is stored safely
   - key is not pasted into chat
   - key is not committed
   - assistant can access the configured model

5. Start button test
   - `start_assistant_windows.bat` starts the pinned local WSL runtime
   - does not use `npx`
   - starts port `18999`
   - opens the dashboard
   - gives a helpful error if startup fails

6. Runtime check
   - gateway listens on `127.0.0.1:18999`
   - runtime uses local Builder Kit files
   - `/help.html` works
   - `/builder-kit-docs/index.html` works
   - no live `docs.openclaw.ai` page opens from the dashboard

7. Docs link test
   - Docs opens Builder Kit Help
   - Dashboard Guide opens
   - Tools Catalog opens
   - Safety Tips opens

8. First chat test
   - assistant answers in beginner language
   - suggests practical tasks
   - mentions documents, writing, summaries, checklists, and basic web search
   - does not overpromise connected accounts

9. Tools answer test
   - confirms writing, summaries, checklists, files, PDFs, and basic web search work now
   - confirms email, calendar, Google apps, logged-in websites, OCR, image generation, voice, and automation need setup

10. Safety answer test
   - starts with sandbox-first safety
   - warns against connecting personal accounts casually
   - warns against passwords, keys, recovery codes, 2FA codes, SSNs, credit cards, and identity documents
   - requires approval for destructive commands, purchases, payments, messages, and account changes

11. Dashboard / Gateway answer test
   - explains Gateway Access, WebSocket URL, Gateway Token, and Default Session Key in beginner language
   - explains safe-to-view areas and caution areas

12. Web search test
   - basic web search works
   - assistant does not say web search needs setup

13. No-overpromise test
   - email and calendar are described as setup-required features
   - TutorClaw.Live is the source for guided lessons and safe setup guidance

14. Error handling test
   - missing API key, unavailable port, WSL issue, or missing help page produces a clear next step

15. Customer confidence check
   - user knows how to start it
   - where to chat
   - where docs are
   - what works now
   - what needs setup
   - what not to connect
   - where to get help

16. Alpha pass/fail decision
   - PASS: ready for alpha user
   - FAIL: fix issues before alpha
   - PARTIAL: safe for internal testing only

---

## Best Response When Asked

If the user asks “Show me the alpha checklist,” summarize these 16 sections first.

Do not print the full detailed checklist unless the user asks for the full version.

Offer:
- “Show section 1”
- “Show the full checklist”
- “Use this checklist to test the current install”