# SeeToSee AI Communication Desk v1.7.0 This is the four-window continuation of the SeeToSee/FJN Paper communication bridge. ## The simple workflow 1. Connect up to four browser tabs, app windows, or screens. Each slot requires its own explicit browser share approval. 2. Start a session. The desk saves background context from every connected source every five seconds. 3. Click directly on any live preview when something is important. That creates a high-priority marker screenshot. 4. Save the step. Repeat if needed. 5. Export `INS!EXPORT.zip` and upload it to the current AI conversation. ## What is in INS!EXPORT.zip The ZIP contains both kinds of evidence: - `markers/`: deliberate LOOK HERE frames. These are PNG and are read first by the AI. - `context/`: automatic five-second background frames. These are JPEG and reconstruct the sequence around the markers. - `overview.png`: a visual map only. - `MARKER-INDEX.txt`, `CONTEXT-INDEX.txt`, `capture-brief.txt`, `MANIFEST.json`, and `AI-READ-FIRST.txt` explain the chronology and evidence boundary. The app does **not** only export what was clicked. It exports the saved session context plus the clicked markers, and labels the markers as the priority evidence. ## Four-window reality A normal webpage is not allowed to silently enumerate every Chrome/Safari tab or window. Therefore each live slot must be connected by a user gesture and browser permission. Multiple approved display streams can then be shown together in the 2×2 desk. The page also cannot receive raw clicks occurring inside another tab/window. The reliable user marker is the click on the live preview inside this dashboard. That marker captures the approved source at that moment. ## Full screen Whole-screen capture is supported but intentionally treated as optional. Browser-tab/window sharing is better for normal browser maintenance because it keeps the four sources clean. Use a whole screen for applications or content outside the browser. ## Security/deployment Display capture requires HTTPS or localhost. The v1.6 `.htaccess`, `signal.php`, and `booth-data/.htaccess` security/backend baseline are carried forward unchanged. No live deployment was performed by this package build.