# BOS Lite 15-minute tester checklist

Please test with ordinary work data you are already allowed to access. Do not paste secrets or confidential raw records into the feedback report.

## Setup

- [ ] Open or create one native Project in Codex/ChatGPT or Claude Cowork.
- [ ] Confirm at least one useful connection is available; calendar and email are the recommended starter pair.
- [ ] Start BOS and complete the Core Setup interview.
- [ ] Confirm BOS asks before creating a Project or enabling any write action.

## Experience

- [ ] Check Business Pulse in the Executive Lobby and the Email Triage queue; confirm each is clearly labeled (for example `Demo` or `Unavailable` when no source is connected).
- [ ] Find the ghosted `Full BOS` panels in Team Floor, Task Board, Office, and Integrations; confirm they are descriptive only, with no working controls.
- [ ] Find the `Chat history import` row in Integrations; confirm it explains the export-and-add-to-Project step and offers no toggle.
- [ ] Open all eight rooms: Executive Lobby, Office, Projects, Advisory Board, Team Floor, Task Board, Integrations, and Settings.
- [ ] Confirm the Projects room points back to native host Projects instead of creating a second project database.
- [ ] Confirm each connected-data surface says `Live`, `Snapshot`, `Demo`, or `Unavailable`.
- [ ] Try Agent Outputs, Calendar Brief, or Memory Search and confirm its state is honest.
- [ ] Ask BOS to plan one module that would make your real work easier.
- [ ] Resize the window or try a narrow view and note anything difficult to read or use.

## Feedback

Run `Run the BOS Lite pilot feedback interview` in Codex or `/bos-lite:give-feedback` in Claude. Please return the generated `bos-lite-feedback.md` file.

The most useful feedback answers three questions:

1. What became easier or clearer?
2. What still felt like a demo instead of a daily operating system?
3. Which missing capability would make the full BOS worth adopting?