chore: initialize K1 connector pre-production scaffold
This commit is contained in:
@@ -0,0 +1,134 @@
|
||||
# First lab runbook
|
||||
|
||||
Purpose: gather decisive evidence using only K1, the current MacBook and the
|
||||
existing TP-Link Deco/mesh network. This runbook contains no BLE writes, router
|
||||
changes, broad LAN scans or system package installation.
|
||||
|
||||
## Before powering K1
|
||||
|
||||
- Place K1 on a stable, ventilated surface.
|
||||
- Prepare its normal battery/charger and a known data-capable USB cable.
|
||||
- Ensure enough Mac disk space for one copied project and short captures.
|
||||
- Do not expose the Wi-Fi password in notes, terminal arguments or screenshots.
|
||||
- If the router model becomes visible in the Deco UI, record only the model and
|
||||
operating mode; do not change settings yet.
|
||||
|
||||
Create an ignored session directory outside ordinary Git, for example:
|
||||
|
||||
```text
|
||||
sessions/20260715T120000Z_gate1_baseline/
|
||||
```
|
||||
|
||||
The operator notes should use masked serials and relative timestamps.
|
||||
|
||||
## Experiment A — boot and activation state
|
||||
|
||||
1. Start a phone/Mac video focused on the LED if convenient.
|
||||
2. Power K1 on normally.
|
||||
3. Record LED colors and durations until stable.
|
||||
4. Record whether the final state is normal standby, activation warning or fault.
|
||||
5. Stop immediately on serious fault, unusual heat, smell, battery problem or
|
||||
undocumented state.
|
||||
|
||||
Expected output: `notes.md`, optional local video, and a redacted manifest.
|
||||
|
||||
## Experiment B — autonomous project
|
||||
|
||||
1. From normal standby, start scanning with the documented double-click.
|
||||
2. Keep K1 completely still for at least 20 seconds.
|
||||
3. Move slowly through a simple scene for about one minute.
|
||||
4. Stop scanning with the documented double-click and wait for stable standby.
|
||||
5. Enter USB mode using the physical shortcut only if its state is understood.
|
||||
6. Copy the project tree, `project.json`, `poses.csv`, `map.las` metadata and logs
|
||||
when present. Raw project data remains ignored and local.
|
||||
7. Generate a SHA-256 inventory; commit only a redacted report later.
|
||||
|
||||
Decision:
|
||||
|
||||
- GO if a valid autonomous project exists.
|
||||
- PAUSE USB analysis if recording works but USB is unavailable.
|
||||
- STOP on activation lock or device fault.
|
||||
|
||||
## Experiment C — passive BLE surface
|
||||
|
||||
Prerequisite: Stage 1 BLE commands implemented and reviewed.
|
||||
|
||||
1. Run a 30-second scan in standby.
|
||||
2. Save advertisement and manufacturer/service data.
|
||||
3. Connect for service discovery without writes.
|
||||
4. Read standard device-information/battery characteristics first.
|
||||
5. Repeat advertisement/GATT observation during scanning and USB mode.
|
||||
6. Subscribe to an individually selected notify/indicate characteristic only
|
||||
after its properties are recorded.
|
||||
|
||||
Decision:
|
||||
|
||||
- GO if K1 has a reproducible BLE identity and observable surface.
|
||||
- PAUSE if macOS asks for pairing/authentication that cannot be completed.
|
||||
|
||||
## Experiment D — current network, no router changes
|
||||
|
||||
1. Capture the Mac route/interface and its current neighbor table with K1 off.
|
||||
2. Note the Deco client list if accessible.
|
||||
3. Boot K1 and repeat in standby.
|
||||
4. Repeat during a button scan.
|
||||
5. Power-cycle K1 and confirm whether any candidate disappears/reappears.
|
||||
6. Check visible SSIDs for a K1-associated AP.
|
||||
|
||||
Do not infer identity from one unknown LAN client. Require power-state
|
||||
correlation or an independent device fingerprint.
|
||||
|
||||
Decision:
|
||||
|
||||
- remembered-LAN GO: confirmed K1 address appears;
|
||||
- device-AP GO: a repeatable K1 SSID appears;
|
||||
- provisioning BLOCKED: neither appears and no known GATT provisioning profile
|
||||
exists.
|
||||
|
||||
## About Guest/IoT networks on Deco
|
||||
|
||||
Do not create one during this first run. Depending on Deco model and Router/AP
|
||||
mode, Guest/IoT networks may isolate clients from the main LAN or from each
|
||||
other. A later dedicated SSID is useful only if both K1 and Mac can communicate
|
||||
and its password can be entered through a known provisioning profile.
|
||||
|
||||
## Minimum lab report
|
||||
|
||||
```markdown
|
||||
# K1 Lab Report 001
|
||||
|
||||
## Host
|
||||
macOS:
|
||||
Mac model/architecture:
|
||||
Router model/mode (if known):
|
||||
|
||||
## Device
|
||||
Model:
|
||||
Serial suffix only:
|
||||
Activation/LED state:
|
||||
Firmware evidence:
|
||||
|
||||
## Autonomous scan
|
||||
Start/stop behavior:
|
||||
Project created:
|
||||
USB accessible:
|
||||
Files observed:
|
||||
|
||||
## BLE
|
||||
Advertised name:
|
||||
macOS UUID: [redacted]
|
||||
Service fingerprint:
|
||||
Pairing/auth prompts:
|
||||
|
||||
## Network
|
||||
Remembered LAN candidate:
|
||||
Device AP candidate:
|
||||
Confirmed K1 IP: [redacted]
|
||||
|
||||
## Decision
|
||||
Current gate:
|
||||
GO / PAUSE / BLOCKED:
|
||||
Evidence:
|
||||
Next smallest experiment:
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user