⌚ WATCH TAP SIGNAL

Theme: “Signal Brass” — a silent wrist language on the house.event/1 spine · Q-Branch Item 5 · PROTOTYPE
Prototype — emits nothing; shows what it WOULD emit

Send a signal

Press a button: on a phone it plays the buzz pattern via navigator.vibrate (guarded — if your device/browser doesn't support vibration, you'll see a note instead of feeling it), and below it prints the exact house.event/1 event that pattern WOULD emit. Nothing is sent anywhere.

CHECK-IN

● ●  (2 short taps)

“I'm here / I'm okay.” Routine — logs as RECORD.

COME-HERE

● ● ● ▬  (3 short + 1 long)

“Come to me.” Non-urgent — surfaces as CHECK.

ALL-CLEAR

▬  (1 long)

“Resolved / stand down.” Closes the thread — RECORD.

DISTRESS

●●● ▬▬▬ ●●●  (SOS-style 3-3-3, repeating)

“I need help now.” Routes as CHECK — never automated action.

Event it WOULD emit

// Press a signal above — the exact house.event/1 JSON appears here.

Receive demo — feel an incoming pattern

Pick an incoming signal: the panel flashes in time with the pattern and your device buzzes it (where supported), so you can learn to read taps by feel.

— idle —

The rules baked in

Defense Ruling 1: outputs are CHECK / RECORD only. A tap is one sense, so no tap can ever emit CONFIRM (CONFIRM needs two physics-independent senses). DISTRESS routes as CHECK, never automated action — the system proposes, the owner actuates. Full table: TAP-CODEBOOK.md in this folder.