KITT Voice — wiring packet

# WIRING-PACKET-A13 — A-13 KITT Voice (communicator) · the sensor half

**Horizon Works · Q-Branch Item A-13 · 2026-10-31 · Theme: "Console Ember"**
**Status: the voice/chat half is BUILT as a staged slice (`index.html`, over SAMPLE state only).
The car-sensor half is NOT wired. This packet is the staged path, in order.**

> **Safety line, printed on the packet and the slice: read-only — this system never writes to the car, never touches the tune.**

**Never present the slice as a connected car.** Its face says so itself:
"Demonstration state. Not connected to any real car."

---

## 0. What this packet rides on — the Valet dossier's filed facts

All sensor facts below are cited from `../../08-valet/DOSSIER-8.md` (gadget #8, the Valet Log),
which graded its claims VERIFIED / REPORTED / UNKNOWN against the house record. This packet
inherits those grades and upgrades none of them. It names no real car, model, tune, or figure
of the owner's — the slice runs on an invented "Sample Sedan," and this packet speaks of
sources, not vehicles.

| Source (DOSSIER-8 §) | What it can sense | What it cannot / has not proven | Grade in dossier |
|---|---|---|---|
| **MHD logs (§2.1)** | A running-engine witness: the full logged channel set while a log is running, **including a battery-voltage channel inside the log**; logs are the owner's own files | Parked: **nothing.** MHD speaks to the car only when the car is awake, a phone is connected, and a log is running. No parked, background, or sentry mode appears in any record checked | VERIFIED (running) · VERIFIED-as-absence (parked) |
| **Dragy (§2.2)** | A session instrument, independent of the car (no OBD connection): GPS speed/position and performance times while a session the driver started is running | Parked sentry use is **UNKNOWN**: no tamper/sentry/geofence feature in any source checked; unattended parked recording unproven; the house unit's model itself unconfirmed | REPORTED (session) · UNKNOWN (parked) |
| **Generic OBD-II dongle (§2.3)** | One genuine parked signal in principle: the OBD port carries constant battery power (pin 16), so an awake dongle *can* read **battery voltage while parked** | Dongle ownership is **UNKNOWN — not inventoried as owned**. Most consumer dongles either sleep when the car's modules sleep (reading nothing) or stay awake as a parasitic draw. Doors/locks/motion are not readable through a generic dongle on a sleeping bus in any source checked | REPORTED (voltage, conditional) · UNKNOWN (ownership, bus reads) |
| **Maker telematics (§2.4)** | The car's factory telematics exist physically | **Not adopted as a source.** It is the maker's cloud holding the car's data on the maker's terms — outside house custody, against the local-first spine. Its state for any house car is UNKNOWN and was not investigated | Not adopted (dossier §2.4) |
| **Spare handset (§§3, 6)** | The phone-as-sensor pattern the house has already proven in-car in another program: its own accelerometer (jolt/motion), its own battery heartbeat, its own GPS — emitting in the house's event language, over the LAN when home, no vendor cloud | The **parked-overnight** part has never been tested: endurance, thermal behaviour in a hot parked cabin, and false-jolt rate are all unmeasured. That unmeasured part is the named blocker | Pattern VERIFIED in-car (driven) · UNKNOWN (parked overnight) |

**Field-by-field honesty — which console fields any filed source could ever fill:**

| Console field (sample today) | Plausible filed source | Honest state |
|---|---|---|
| Fuel level | A running log / an awake OBD read | Only while awake and logging/reading — never a parked read on any filed source |
| Battery voltage | MHD log channel (running) · OBD pin-16 read (parked, conditional) | Running: filed. Parked: conditional on a dongle that may not exist and may sleep |
| Mileage | A running log / an awake OBD read | Awake-only, same as fuel |
| Tire pressures | **None filed.** No source in DOSSIER-8 proves a tire-pressure read in any state | **GAP — stays SAMPLE until a source is proven, never filled by assumption** |
| Last trip | MHD log files (a drive that was logged) · Dragy session files (a session that was run) | Real only for drives/sessions that were actually recorded; an unlogged trip leaves no state |
| Parked jolt / motion | Spare handset accelerometer (§3 pattern) | Only after Step 1's fixture measures it |

---

## 1. THE STAGED PATH — in order, no step skipped

### Step 1 — The Valet overnight fixture runs first
**Mark: NEEDS THE FIXTURE**

- **What:** DOSSIER-8 §6, exactly as proposed there and not executed by that dossier:
  one spare fleet handset, fully charged, running a $0 sensor-logging app cleared first,
  placed in the parked car's center console at home for one night; two scripted,
  owner-performed, timed touches in the first ten minutes (one firm door close, one
  deliberate rock) as ground truth; a morning read on (a) continuous logging + ending
  battery, (b) both scripted touches visible above the night's noise floor + the
  false-jolt count printed whatever it is, (c) handset temperature / any thermal
  warning on pickup.
- **Needs:** the owner's word, and a charged spare handset in the car. An agent does
  not stage hardware in a car.
- **Why first:** it is the dossier's named blocker (§5) for the whole parked-sensor
  idea. It proves only whether the phone-as-sensor form survives a parked night and
  can tell a touch from a quiet night — nothing about away-from-home use or live car
  state, and its report must say so.
- **A-13 consequence:** until this runs, A-13 has no honest parked producer at all,
  and the console stays on SAMPLE state. The voice half does not wait for it — it is
  already built, over sample data, honestly labeled.

### Step 2 — Log-import path: existing exports → the console's state
**Mark: EXISTS TODAY** *(inputs and target shape exist today; the adapter itself is a small later build, not built in this slice)*

- **What exists today:** the owner's existing MHD log exports and Dragy session
  exports as files (DOSSIER-8 §§2.1–2.2 — the logs are real house files), and the
  console's state shape, defined in `index.html` (fuel · battery · mileage · tires ·
  last trip, each field carrying a SAMPLE/provenance stamp).
- **The path, when commissioned:** owner picks a log file locally in the browser
  (file input, no upload, no network) → a local parser maps the channels/fields the
  file actually carries into the console state → every imported figure prints its
  source file name and its as-of time beside it, and any field the file does not
  carry (tire pressures, on the filed evidence) stays SAMPLE and says why.
- **Discipline:** an imported state is a picture of the last *recorded drive*, never
  a live car. The console face must change its line for this mode to name the source
  file and date — the current "not connected" line is replaced by an equally plain
  "state from file X, recorded [date]" line, never by silence.
- **Why second:** it rides files the house already has, needs no hardware in the car,
  no ruling, and no parked sensor — and it converts the slice from sample to
  owner-filed history without ever claiming a connection.

### Step 3 — Live OBD read path
**Mark: NEEDS A RULING** *(a later, separately-ruled step — not part of this build)*

- **What it would be:** a read-only OBD reader, awake-state reads first (fuel,
  battery voltage, mileage-class fields), with the parked voltage read attempted
  only after the dongle's sleep behaviour is measured on the owner's own car.
- **What it needs before anyone builds it:** (a) a ruling of the owner's naming this
  step, in that moment; (b) an adapter inventoried as actually owned (DOSSIER-8 §2.3:
  ownership is UNKNOWN today — no dongle is asserted); (c) a read-before-write /
  read-only posture read for the specific tool, since the safety line above is
  absolute: read-only — this system never writes to the car, never touches the tune;
  (d) the parked-draw question answered with a measurement (a dongle that stays
  awake is a load on the battery it would be guarding).
- **Explicitly not this step:** maker telematics as a live source (§2.4, not adopted),
  any write, flash, coding, or clearing function, and any continuous location stream.

---

## 2. What never changes, at any step

- Read-only toward any car, forever. No step in this packet writes, flashes, codes,
  clears, or commands anything in a vehicle.
- No person's location, identity, or occupancy is a console input, at any step —
  the Valet fence (the car reports on itself only) binds A-13 exactly as it binds #8.
- Local-first: state lives as local files on house devices; no account, no cloud,
  no telemetry, $0.
- Provenance travels with every figure: SAMPLE, file-imported (file + date), or —
  only if Step 3 is ever ruled and built — live-read (with its as-of time). A figure
  whose provenance is lost is deleted from the console, not relabeled.

*Filed by Horizon Works, Q-Branch A-13, 2026-10-31. Companions: `index.html` (the built
voice/chat slice over sample state) · `BUILD-RECORD-A13.md` · `FIXTURES-A13.md` ·
`WHAT-TO-TRY-A13.md` · `CUTLIST-A13.md`. No car was touched, no device was placed,
no log was imported, no fixture was run.*