The Valet Log — concept dossier (FORMING)

# DOSSIER-8 — THE VALET LOG: The Car That Reports Tampering

**The Horizon Works · Q-Branch Item 8 · Concept Dossier · 2026-10-31**
**Commission:** Chris, 2026-10-31 20:53 EDT — "Build everything" (the eight-item 007 menu). Per the program Catechism (`../CATECHISM.md`): *"no car build (Valet is FORMING; dossier only)."*
**Charge:** Horizon Works (HZW). **Cost:** $0. **Build:** none — this dossier is the deliverable.

**Headline grade: FORMING.**

**The fences, printed on the face:** owner's own cars only · the car reports on **itself** only — no tracking of any person, ever, and no location tracking of family members · no always-on telematics the house does not control is adopted by this dossier · $0.

**Grades used below, per house practice:** **VERIFIED** = read in a house record cited beside the claim · **REPORTED** = a secondary / vendor / community claim, or a general platform fact not proven on house hardware · **UNKNOWN** = not established by anything checked. A claim about what a device *could* do in a parked car is never upgraded because it sounds plausible.

---

## 1. THE FICTION VERSION — *IMAGINATION, LABELED*

> *This section is imagination. Nothing in it exists, and nothing in it is a claim.*

In the film, the car knows. Q's Aston sits silent in the hotel garage in Monte Carlo, and when the valet's mate leans on the quarter panel at 2 a.m., when a door handle is tried, when the car is rocked onto a tow dolly, a quiet line appears on Bond's phone before the tow truck has left the ramp: **the car was touched at 02:14, it was lifted, it is moving and it did not start.** The car carries a valet mode that caps its power, a log that no valet can erase, and a memory for hands that were not its owner's. It reports tampering the way a good watchdog does — specifically, immediately, and only about itself.

That is the fantasy shape: **a parked car with a witness's memory.** Sections 2–5 strip it down to what this house, with what it actually owns, could honestly approach — and where the honest version stops.

---

## 2. WHAT THIS HOUSE ACTUALLY OWNS — AND WHAT EACH SOURCE CAN REPORT WHILE PARKED

### 2.0 The cars, verified from the record first

| Car | State on record | Source |
|---|---|---|
| **2019 BMW 540i** (G30, RWD, B58) | MHD Stage 2 on ~E40 flex fuel, B58TU HPFP; Stage 3 planned, no Stage 3 hardware selected. The family drag-racing team car; street-driven. | **VERIFIED** — `~/workspace/goals/family-drag-racing-team-brand/files/racing-foundations-research.md` §head; `~/workspace/goals/bmw-and-audi-car-tooling-program/GOAL.md` |
| **2018 Audi SQ5** (B9, EA839 3.0T) | Forged rebuild in parts-collection phase — **"not assembled, not running"**; the car "has sat, engine out, through a Florida summer." | **VERIFIED** — `~/workspace/goals/sq5-forged-engine-rebuild/files/sq5-turbo-buy-sheet-2026-10-23.md`; `…/files/thermodynamics-desk-ea839-review.md` |

**Consequence printed plainly:** the SQ5 can report nothing. It has no running electrical story on record (its battery state is **UNKNOWN**), and any Valet Log concept is, today, a **540i-only** concept. The SQ5 rejoins the question only after its rebuild, as a fresh inventory question — not by assumption.

### 2.1 MHD (the tune + app + datalogs) — a running-engine witness, silent parked

What the house has, on record:

- The 540i runs an **MHD Stage 2** flash — **VERIFIED** (above).
- **Real MHD datalogs exist in the house:** seven owner logs from August 2026, parsed by Team Garage / the MHD reader; the MHD 5.26 export family on record carries a **`Battery volt. (V)` channel** among its ~58 channels — **VERIFIED** — `~/workspace/car-app/JOURNAL.md` (2026-10-22 entry); `~/workspace/annex/telemetry/MHD-LOG-FORMAT.md` §3.
- The MHD app connects over **WiFi / ENET adapters** — **VERIFIED as the app's connection model** (same format memo, §head). *Which adapter Chris owns is **UNKNOWN** — no adapter is inventoried anywhere in the car record checked; the logs prove an app session happened, not which hardware carried it.*

What it can sense, by ignition state:

| State | What MHD reports | Grade |
|---|---|---|
| Ignition ON / engine running | The full logged channel set at ~9–12.5 Hz in the logs on record — boost vs target, per-cylinder timing corrections, IAT, ethanol content, **battery voltage** — but only while a log is running, in short pulls (the seven real logs run 4.7–5.8 s each) | **VERIFIED** — car-app JOURNAL figures |
| Ignition OFF / parked | **Nothing.** MHD speaks to the DME when the car is awake and a phone is connected and logging. There is no parked, background, or sentry mode in any house record or MHD source checked. Battery voltage — the classic parked signal — exists in MHD only as one channel inside a running log; a parked car produces no log | **VERIFIED as absence-in-record** (the logs and memo are the whole MHD record); a hidden parked feature is **UNKNOWN**, never assumed |

**Valet verdict for MHD:** it is the car's best witness *to a drive* — if a valet drove the 540i hard, a later MHD log read + the tune's own history is a Crew Chief question. It is **not** a parked witness at all.

### 2.2 Dragy — a session instrument with its own battery; no sentry on record

What the house has, on record:

- Chris owns a Dragy unit **believed to be a Dragy Pro** — owner belief recorded 2026-10-20, **explicitly NOT confirmed**; model confirmation is still Step 0 of the Dragy Lab test plan — **REPORTED / UNCONFIRMED** — `~/workspace/dragy-lab/FEASIBILITY.md` §head, `TEST-PLAN.md`.
- If it is a Pro, the manufacturer's page (fetched 2026-10-20) confirms: u-blox 10th-gen GNSS up to 25 Hz, a **6-axis IMU**, 128 MB on-board storage (up to 30 h @ 10 Hz), **battery over 20 h** — **CONFIRMED as manufacturer's claims in that brief's grading**, which this dossier inherits as **REPORTED for this house's unit** until the model is confirmed.
- Dragy works **completely independently of the car** — no OBD connection; a smartphone over Bluetooth controls it — **CONFIRMED** (Dragy Motorsports FAQ, via the Dragy Lab brief).

What it can sense, by state:

| State | What Dragy reports | Grade |
|---|---|---|
| Session running (driver starts it) | GPS speed/position at up to 25 Hz, performance times; on-board recording on Pro/Lite | **REPORTED** (manufacturer, above) |
| Parked, left in the car, session running | *In principle* a recording unit with GPS + IMU would register the car being moved without being started. **But:** no tamper, sentry, geofence-alert, or parked-monitoring feature appears in any source the Dragy Lab checked; whether recording continues unattended, what the IMU data is even accessible as, and whether the unit would survive a Florida parked-car day are all unproven | **UNKNOWN** — a capability silhouette, not a feature |
| Parked, off / in a drawer | Nothing. And where the unit normally lives is **UNKNOWN** on record | — |

**Valet verdict for Dragy:** the most tantalizing silhouette in the drawer (own battery, own GPS, own IMU, no car power needed) and the least proven for this job. It is a *stopwatch*, not a *watchdog*, on every source checked. Building a valet concept on it today would be building on an unconfirmed model and an unclaimed feature.

### 2.3 A generic OBD-II dongle + app (BimmerLink class) — not inventoried as owned

- **Ownership: UNKNOWN.** The car-tooling record *researches* BimmerCode / BimmerLink-class tools and ENET cables in depth (`~/workspace/crew-chief-desk/car-tooling-briefs-2026-10-22.md`), and the charter's read-before-write ladder assumes an ENET read path — but **no OBD dongle, Bluetooth adapter, or ENET cable is inventoried as bought or owned** anywhere in the record checked. This dossier does not assert the house owns one.
- General platform behaviour, graded **REPORTED** (general knowledge, not house-verified): the OBD-II port carries constant battery power on pin 16 even with ignition off, so a plugged dongle *can* read **battery voltage while parked** — the one genuine parked signal in this whole section. Against that: most consumer dongles either sleep when the ECUs sleep (reading nothing until wake) or stay awake and become a parasitic draw on the very battery they'd be guarding; the car's modules are asleep parked, so doors/locks/motion are not readable through a generic dongle on a sleeping G30 bus in any source checked (**UNKNOWN** for this car specifically).
- **Valet verdict:** a voltage-only parked witness *if* a dongle exists and *if* its sleep behaviour cooperates — two unproven conditionals, and voltage alone says "the battery sagged," never "someone touched the car."

### 2.4 BMW ConnectedDrive / My BMW — BMW's telematics, not the house's

- The G30 left the factory with BMW's own telematics, and the house record touches ConnectedDrive only sideways: a ConnectedDrive subscription *usually* gates the car's Apps checkbox (**REPORTED** in `~/workspace/crew-chief-desk/research/HEAD-UNIT-AND-CAR-SOFTWARE-SWEEP-2026-10-25.md`), and the My BMW app is named as a fallback read for software version (**REPORTED**, `ID7-THREAD-ASSESSMENT-2026-10-27.md`).
- **This car's subscription status, remote-services state, and what its My BMW account shows today: UNKNOWN** — never read on record.
- Even where BMW's remote services report lock/vehicle state, that is **BMW's cloud holding the car's data on BMW's terms** — the opposite direction from this house's local-first, house-controlled spine, and outside the house's custody the moment it leaves the car. This dossier **does not adopt it as a source** (see BUILD-RECORD-8.md). It is named here so the gap is honest: the one always-on telematics the car physically has is the one the house does not control.

### 2.5 The summary the fiction has to survive

| Source | Parked: battery voltage | Parked: motion / jolt | Parked: position | House-controlled? | Owned, on record? |
|---|---|---|---|---|---|
| MHD | Only inside a running log — **no** | No | No | Yes (owner's logs) | App/tune **VERIFIED**; adapter **UNKNOWN** |
| Dragy | Its *own* battery only | IMU exists; no sentry feature — **UNKNOWN** | GPS, *if* a session runs — **UNKNOWN** parked | Yes (owner's device) | Unit **REPORTED** (model unconfirmed) |
| OBD dongle | **Yes, if** awake — **REPORTED** | No (bus asleep) | No | Yes | **UNKNOWN** — not inventoried |
| ConnectedDrive | Via BMW — **UNKNOWN** for this car | Via BMW — **UNKNOWN** | Via BMW — **UNKNOWN** | **No — BMW's cloud** | Subscription **UNKNOWN** |
| Spare phone (§3) | Its own battery + health | **Yes** — accelerometer | Its own GPS — *car's location only, see fence* | Yes | Fleet handsets **VERIFIED** (RF program) |

---

## 3. THE HONEST GAPS — AND THE ONE PATTERN THE HOUSE HAS ALREADY PROVEN

**Gap 1 — No always-on telematics the house controls.** §2 is the whole proof: every car-native source is ignition-gated (MHD, OBD), session-gated (Dragy), or someone else's cloud (ConnectedDrive). There is no house-owned sensor that is *awake in the parked car today*. That is the concept's central gap, and no copy in this dossier papers over it.

**Gap 2 — Florida heat vs. any battery left in a parked car.** Central Florida sun makes a parked cabin a hostile place for a lithium battery left inside for hours. Any phone/Dragy-in-car design carries a real thermal and battery-swelling question that a desk cannot answer — only a cautious, attended first test can bound it. Printed as a safety gap, not a footnote.

**Gap 3 — The correlator end is ruled and built as code, but a car producer has never fed it.** The fusion spine exists in law (Defense Ruling 1, adopted 2026-10-25) and as built code (`~/workspace/correlator/`, over `house.event/1`); no vehicle producer exists, and a car is a new *zone* the registry has never carried.

**The alternative that is not a gap — the phone-as-sensor pattern.** The house has already proven the shape this concept needs, in another uniform: **spare handsets as sensors.** The RF Detector program ran paired Samsung + Moto handsets *in the same car, on the same drive* (FIELD-LOG FL-028/FL-029, `~/workspace/field-ops-desk/`), sealed and graded their sessions; the adopted second-life table (D-2, 2026-10-25) assigns Galaxy-class handsets to RF Detector duty and a 7/8-class handset to a fixed-mount capture station. A spare Android handset left in the parked 540i is the same pattern stood still instead of driven:

- **Accelerometer** → jolt / rock / sustained-motion events (the tow-truck and door-slam signatures) — the phone's own sensor, no car integration needed.
- **Its own battery telemetry** → a heartbeat: a phone that stops reporting *is itself an event*.
- **GPS** → used, if at all, only as the *car's* position while the phone is assigned to the car — see the fence in §5; it is never a person's location, and the dossier's default design (§4) emits motion events **without** continuous position.
- It emits in the house's own language, §4, over the LAN when home — no vendor cloud anywhere in the path.

That pattern is why this dossier grades FORMING and not FAR: the sensor, the session discipline, and the event language all exist in the house. What has never been tested is the *parked overnight* part — endurance, heat, and false-jolt rate — which is exactly what §6's fixture is for.

---

## 4. EVENT SHAPES — WHAT A VALET PRODUCER WOULD EMIT

Under Defense Ruling 1, producers emit `house.event/1` (contract of record: `~/workspace/audio-sentry/EVENT-CONTRACT.md`); the correlator decides **CHECK / CONFIRM / RECORD** only, and the owner is the only actuator. A valet producer is **one sense (motion/heartbeat, one physics)** — so by the spine's own law its ceiling standing alone is **CHECK**; **CONFIRM would require a second, physics-independent sense agreeing within ±120 s in the same zone** (e.g. the house's Audio Sentry or a camera hearing the same moment at home), and most valet events should simply **RECORD**.

Proposed shapes (paper only — no producer is built; field names follow the contract exactly):

| `event_class` (producer-namespaced, e.g. `valet_log`) | Trigger | `level` carries | Expected decision |
|---|---|---|---|
| `parked_jolt` | Accelerometer spike above a stated threshold while parked-armed | peak acceleration, duration | RECORD; CHECK if repeated/clustered |
| `sustained_motion` | Motion continuing beyond a stated window with ignition never on (the tow signature) | duration, motion intensity | CHECK (alone); CONFIRM only with a second sense |
| `heartbeat_missed` | The parked handset misses its stated reporting interval | minutes since last heartbeat | RECORD (a dead/sleeping sensor is disclosed, never silent — the RF program's radio-silence discipline carried over) |
| `voltage_low` *(only if a dongle source ever proves out, §2.3)* | Battery voltage below a stated floor | voltage in the key name, per contract units discipline | RECORD |

Deliberately **absent** from the shapes: no continuous location stream, no audio, no occupant anything. The contract's privacy fence (event metadata and evidence pointers only) binds this producer exactly as it binds the Sentry.

---

## 5. DISTANCE GRADE — FORMING, AND THE NAMED BLOCKER

**Grade: FORMING.**

**What is already real:** the cars and their tooling (§2, graded), the spare-handset sensor pattern proven in-car by the RF fleet, the `house.event/1` contract, and a correlator whose CHECK/CONFIRM/RECORD law already prices a single-sense car producer honestly.

**The named blocker:** *no house-controlled sensor has ever spent one night awake in the parked 540i.* Every candidate source is unproven at exactly the parked-overnight job — MHD and OBD are ignition-gated, the Dragy's model and any parked behaviour are unconfirmed, no dongle is inventoried, and the spare handset's overnight endurance, thermal behaviour in a Florida cabin, and false-jolt rate are all unmeasured. One fixture (§6) is the distance between this dossier and BUILDABLE-NOW for the phone-as-sensor form — and if that fixture fails, the honest grade falls, not the story.

**The fence that does not move with the grade:** the car reports on **itself** — its motion, its battery, its state. It never reports on a person: no family member's location, no driver's identity, no passenger anything, in any future form of this concept.

---

## 6. THE CHEAPEST FIRST FIXTURE — *PROPOSAL ONLY, NOT EXECUTED*

**One overnight parked test, $0, one owner-evening plus one owner-morning:**

1. **Device:** one spare RF-fleet handset (the Samsung that already runs RF Detector sessions — a fleet device, not anyone's daily phone), fully charged, running a $0 sensor-logging app the Quartermaster gate clears first, placed in the 540i's center console at home, car locked and parked as normal for the night.
2. **Two scripted touches, owner-performed and timed:** one door closed firmly and one deliberate rock of the car in the first ten minutes — the ground truth the log is graded against. Nothing else touches the car overnight, as far as a normal night allows.
3. **Morning read (the whole exam):** (a) Did the handset log continuously all night, and what battery did it end on? (b) Do the two scripted touches appear, at the right times, clearly above the night's noise floor — and did anything else cross the threshold (the false-jolt count, printed whatever it is)? (c) Handset temperature / any thermal warning on pickup — the Florida-heat question's first data point, taken on a mild night at home before any hotter test is even discussed.
4. **What it proves, and only this:** whether the phone-as-sensor form survives a parked night and can tell a touch from a quiet night — the exact blocker in §5. It proves nothing about towing detection, away-from-home use, or a second car, and the fixture report must say so.

Owner time: ~10 minutes at night, ~5 in the morning. If it passes, the next step is a *design* commission (producer + correlator zone registration), not another dossier. If it fails twice on the same defect, the Catechism's kill signal folds this item to a packet with the failure printed.

---

*Filed by Horizon Works, Q-Branch Item 8, 2026-10-31. Companions: `WHAT-TO-TRY-8.md` (the owner's read/decision sheet) · `CUTLIST-8.md` (retail cut list) · `BUILD-RECORD-8.md` (what was deliberately not done, and why). No car was touched, no device was placed, no test was run.*