What to try — a11-jarvis

# WHAT TO TRY — A-11 House Console ("House Console Slate")

**Open it:** double-click `index.html` in this folder (`stream-a/a11-jarvis/index.html`) in any browser. No install, no server, no internet needed. It is one single file.

**⚠ This is the console *slice*, not the wired house. The house is not connected — the page says so on its face. Every tile is SAMPLE state held inside the page; commands rearrange the simulation so you can judge the console itself: its grammar, its honesty, its feel. The rest of the job is the wiring packet (`WIRING-PACKET-A11.md` beside this note).**

## Try these (about 3 minutes)

1. **Type `status` and press Enter.** You get the whole SAMPLE house picture in one line — gateway, network, detector, locks, lights, climate — and the reply itself reminds you it's simulated. Watch the tiles: they are the same state the reply describes.
2. **Type `lights kitchen off`.** The kitchen line in the Lights tile flips to OFF and dims — the command visibly mutated the state. Type `lights kitchen on` to flip it back. (The gold chips under the command line run the same commands with one tap.)
3. **Type `lock up`, then `good night`.** `lock up` locks both SAMPLE locks in the Detector & Locks tile. `good night` runs the routine: all lights off, locks locked, thermostat target 70, and the house-mode pill at the top switches to NIGHT. `good morning` unwinds it; `reset` restores the starting state.
4. **Type `thermostat 70` — then try `thermostat 95`.** The first moves the Climate tile's target. The second is refused (this slice's range is 55–85) and nothing changes. Range guards are part of the grammar, not decoration.
5. **Try to break it: type something wild** — `play some music`, `open the pod bay doors`, anything. You should get the honest answer: **"I can't do that (yet)"** with a pointer to the wiring packet. Also try `unlock`: it refuses *on purpose*, even in simulation — in the wired house, unlocking is something you do, never something the assistant does.
6. **Look at the voice button.** It resolves one of two ways depending on your browser: **"Push to talk"** (your browser itself offers speech recognition — press it, say `lights kitchen off`, and the command runs) or **"Voice: UNAVAILABLE — typing only"** (your browser offers none, so the page prints that instead of pretending). Either outcome is the feature working: capability-gated, never faked. No microphone opens until you press the button.
7. **Check the six tiles once more.** Gateway · Network · Detector & Locks · Lights · Climate · Weather — every one stamped SAMPLE, every one saying **"not wired yet."** If you find any line that reads as if it were live, that's a defect — tell Muse where.

## Questions it would help to answer after looking

- Is this the command grammar you'd actually talk in — `lights kitchen off`, `lock up`, `good night` — or do you phrase the house differently? The grammar is cheap to change now and expensive after wiring.
- When wiring starts (the packet's order), is Home Assistant on the Pavilion the right step 2 — and which room's lights earn the first real entity?
- Does the actuation fence sit right: the assistant may report anything and propose anything, but locks and anything touching people stay your hands only?