fix(comms): constant-per-day subjects for hive/activity/push-digest/lens-debug emails

Hive tracker, per-visit ThetaCoach activity, the activity-report cron,
and push digest all built a unique subject per send (path/IP/referrer/
TOD/human-score/commit-count), so every event opened a new Gmail
thread instead of bunching into one thread per day. Lens debug already
threaded correctly (date-only subject) but still carried an emoji in
the subject line.

Fix: every subject is now a fixed label + the day's date, no emoji, no
per-instance noise. All the per-instance detail (location leads the
hive-tracker body per the operator's ask, geo flag/human-score/TOD/page
for activity) moves inside the email body. Referrer + browser/UA were
already present in both visitor-tracking bodies; left untouched.

Guard: tests/comms/daily-thread-subjects.test.js — static-checks each
of the 5 subject lines for no-emoji, date-anchored, no-per-instance-
noise, so the threading convention can't silently regress.

Originating-Terminal: 🎤 voice
Relevant-Rooms: 🎩 operator, 🎤 voice, 🔨 builder
Story: Operator asked to normalize subjects across the repeating
automated-email systems (hive tracker, push digest, lens debug,
thetacoach activity) so same-day sends thread together in Gmail,
using lens debug's already-correct date-anchored subject as the
reference pattern.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YQxP9rRho3RXPUBTtdvWgZ

commit abd5d25c7 — 144×144 lattice triptych (on-chip)

◎ the ingest chose B,C — Tactics × Operations — acting on A1,C1 — Strategy·Law × Operations·Grid (grip 0.719) · the walk starts at the ACTOR's row · 6 file(s)

⏱ ingest 117.6ms (corpus→lattice) · definer walk 589ms (row→transpose→row, ballistic XOR per hop) · total 803ms
ingest here = commit-scoped SENSING only (this commit's message + changed files → lit anchors) — deep seed authoring lives in the reef-self-loop, off the commit path

rows = ACTOR (lens) · cols = PATIENT (object) · diagonal = self-reference; ◎ at actor-row × patient-col — every panel, same orientation. Heat above the diagonal = actors ranking ShortLex-earlier than their patients (the walk follows definers uphill in rank).
The 12 canonical lanes (rows top→bottom, cols left→right): A·Strategy · B·Tactics · C·Operations · A1·Law · A2·Goal · A3·Fund · B1·Speed · B2·Deal · B3·Signal · C1·Grid · C2·Loop · C3·Flow

PAIR LATTICE (the map we normally see)

PRE-WALK SENSE · INTENT grid — the snapshot, no point of view

the no-point-of-view snapshot — what the sensor lit before any walk; the leaf walk below is what bridges the two grids

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

PRE-WALK SENSE · REALITY grid — the snapshot, no point of view

the no-point-of-view snapshot, reality side — same sensor law

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

PRE-WALK Δ · straight comparison of the two ingested grids (green both · cyan intent-only · amber reality-only) · 6% overlap · ◎ = where the competence pixel sits in the raw overlap

good = green overlap without being a copy — near-100% is self-similarity, not alignment

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

◎ the pixel this commit belongs to

B,C — Tactics × Operations (actor) acting on A1,C1 — Strategy·Law × Operations·Grid (patient) · grip 0.719

actor seed B,C — Tactics determine the timing and beat required to run the daily operations cadence and execution loop. Tactics is the choice of which leverage to pull at which beat. Not what we want, but how the want lands on Tuesday: the sequence of irreversible commitments, each made before the next one's information is available. Speed of feedback dominates speed of execution. Tactics that converge fast beat tactics that compute long, because the loop closes around the world's response before the world has moved. The tactical map is a ranked list of moves where each move carries a cost-of-delay. Pick the move whose cost of doing it tomorrow exceeds the cost of doing it imperfectly today. Execution is a sequence of bets made under uncertainty. Tactics is the discipline of betting the right size on the bet whose information value pays for the loss-if-wrong. Operations is the loop that runs whether anyone watches. The daily commit, the hourly hook, the per-request fingerprint — the substrate of the substrate, ambient and unwatched. Process is what you forget to do; ops is what does itself. Convert manual moves into ambient state, because the tax of remembering compounds faster than the tax of automating. The daily friction is the diff between your intent and your harness. Close the diff or pay the tax twice — once in the slip, once in the apology to the next agent. Operations earns its keep by being boring. The day the routine is interesting is the day it has already failed and is being narrated rather than executed.

patient seed A1,C1 — A binding law provides the mandate for power flow through the infrastructure grid and route topology. EU AI Act Article 14 requires human-on-the-loop oversight, with the supervisor able to interrupt the system at any moment. Compliance attaches to the artifact the artifact cannot escape — provenance is a regulatory primitive, not a feature. Power flows where the grid lets it. Choose connections before topologies; the topology is what the connections compose, and a connection added later is a topology silently rewritten. Constraints precede objectives. The cap-table, the license text, the consent envelope — each draws the inviolate line the action must respect, and the line is enforced before the optimization runs. Latency is geography expressed in milliseconds. The grid IS the map of where compute meets storage meets bandwidth; the map is the territory at the scale the request actually traverses. A rule names what the system MAY NOT do. If the agent can do X, then 'forbid X' is not the constraint — it is wishful thinking dressed as policy. Constraints live in the gate, not in the prompt. Infrastructure decisions are reversible at ten-times the cost of being right the first time. Buy the irreversibility down before you provision the easy decisions, because the easy decisions ride on the irreversible ones. Regulation is not advisory. The fine is the price tag stapled to the omitted control; insurance is the option pricing on the failure-mode the regulation already named. A connection between two systems is a contract that outlasts the systems on either end. Wire-protocols outlive the processes they connect; the wire is the substrate, the endpoints are the exhaust.

INTENT · leaf-walk clouds · BLUE→VIOLET by ply (◎ = the competence pixel: actor∩patient)

good = the clouds concentrate where the commit SAYS it works

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

REALITY · leaf-walk clouds · ORANGE→RED by ply (◎ = the same pixel — the shared perspective)

good = the same clouds as intent — shipped where declared

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

DELTA · graded cloud divergence (green agree · magenta declared-not-done · amber done-not-declared) · 5% agree

good = mostly green; magenta = said-not-done (chase it in the code), amber = done-not-said (chase it in the docs)

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

TOLERANCE · cloud topology (dim green in-shape · hot amber bleed · red orthogonal concentration) · ⚠ TOO MANY

red only matters above the flip — a few amber is normal bleed

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

SHORTLEX-3 PROJECTION (ABC · A1..C3 · the 132 children — candidate, pre-ratchet)

PROJECTED INTENT · the commit’s claims, head→axis_i tail→axis_j (cyan)

the three-length view — good = claims land inside their own zone

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

PROJECTED REALITY · same projection law (amber)

same projection law — good = reality occupies the zones intent does

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

STRAIGHT COMPARISON · green both · cyan intent-only · amber reality-only · 3% overlap

good = the zones agree; cross-zone scatter is the drift to read

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

shortlex-3 zone occupancy (lit cells per diagonal square)
INTENT: 0 in the 3×3 ABC corner · 1 in the 9×9 A1..C3 square · 1134 in the 132×132 children square · 138 cross-zone
REALITY: 0 in the 3×3 ABC corner · 1 in the 9×9 A1..C3 square · 1315 in the 132×132 children square · 97 cross-zone
axes: identical 144 ShortLex names both sides (symmetric); weights asymmetric
zone 3 = candidate children, pre-ratchet (repo-derived dumps not yet past the perturbation-probe gate) · intent 8 claims @ θ 0.5938 · reality 41 claims @ θ 0.625 · projection 735ms

SHAPE-MATCH σ = 4.46 — the real intent↔reality definer walk vs random-reality (actual 0.18 vs random 0.073). >0 = the walk distinguishes real alignment from noise; aggregate over independent walks → the divergent series.
σ_drift · forming · separation is forming — the direction is real, the trust is not yet

Most out-of-lane row: B1 · Speed — that lane is drifting most (read the red band in that row).

Three-colour tolerance (out-of-lane = reality fires where intent is weak, in orthogonal blocks): green=in-lane agreement · amber=a few out-of-lane (tolerated) · red=FIRED — orthogonal out-of-lane 50% vs tolerance 25%.
435 green · 480 amber · 916 red · 473 XOR-friction cells.

Both axes = the 144 ShortLex anchors, cell=row⊕col, on the chip. INTENT=docs+rules · REALITY=code · DELTA=friction.

tile dump — what the SimHash matched on the diagonal (inspect the sensor; tap to expand)

A,A The lattice we build today is what next year's underwriter inherits.

intent 72% (no distinctive match)

reality 73% This change operates in the ui frontend domain, involving page react nav. This change operates

B,B Tactics is the choice of which leverage to pull at which beat.

intent 63% (no distinctive match)

reality 70% (no distinctive match)

C,C Operations is the loop that runs whether anyone watches.

intent 77% (no distinctive match)

reality 69% (no distinctive match)

A1,A1 EU AI Act Article 14 requires human-on-the-loop oversight, with the supervisor able to interrupt the system at

intent 70% (no distinctive match)

reality 72% // email itself") lives in the body, not the subject. (2026-07-08)

A2,A2 The target is the cell coordinate the system MUST occupy by end-of-quarter.

intent 73% (no distinctive match)

reality 75% (no distinctive match)

A3,A3 Every dollar builds either the floor (substrate that lifts future bets) or the ceiling (cap on the next round)

intent 66% (no distinctive match)

reality 66% (no distinctive match)

B1,B1 Latency is the price of a missed beat.

intent 67% (no distinctive match)

reality 72% --subject "Push digest · ${DATE}" \

B2,B2 The deal sets the exchange rate between two value substrates.

intent 69% (no distinctive match)

reality 69% (no distinctive match)

B3,B3 Signal-to-noise is the inverse cube of bandwidth — narrow the channel, the message arrives; broaden it, recipi

intent 72% (no distinctive match)

reality 70% // (operator, 2026-07-08: "emoji local inside email not in subject")

C1,C1 Power flows where the grid lets it.

intent 69% (no distinctive match)

reality 67% (no distinctive match)

C2,C2 Each iteration is a hypothesis tested against the ground truth of the world.

intent 69% Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/

reality 72% (no distinctive match)

C3,C3 Flow is the rate at which committed work crosses the finish line.

intent 72% (no distinctive match)

reality 70% (no distinctive match)

commit context — 6 file(s)

fix(comms): constant-per-day subjects for hive/activity/push-digest/lens-debug emails

Hive tracker, per-visit ThetaCoach activity, the activity-report cron,
and push digest all built a unique subject per send (path/IP/referrer/
TOD/human-score/commit-count), so every event opened a new Gmail
thread instead of bunching into one thread per day. Lens debug already
threaded correctly (date-only subject) but still carried an emoji in
the subject line.

Fix: every subject is now a fixed label + the day's date, no emoji, no
per-instance noise. All the per-instance detail (location leads the
hive-tracker body per the operator's ask, geo flag/human-score/TOD/page
for activity) moves inside the email body. Referrer + browser/UA were
already present in both visitor-tracking bodies; left untouched.

Guard: tests/comms/daily-thread-subjects.test.js — static-checks each
of the 5 subject lines for no-emoji, date-anchored, no-per-instance-
noise, so the threading convention can't silently regress.

Originating-Terminal: 🎤 voice
Relevant-Rooms: 🎩 operator, 🎤 voice, 🔨 builder
Story: Operator asked to normalize subjects across the repeating
automated-email systems (hive tracker, push digest, len

scripts/cog/prompt-lens-hook.sh
scripts/push-digest.sh
src/app/api/activity/track/route.ts
src/app/api/hive/track/route.ts
src/lib/activity-email.ts
tests/comms/daily-thread-subjects.test.js

Produced on the chip by the running pipeline (scripts/pmu/pipeline.mjs → runPipeline → walk + xor), commit-scoped · on-chip per-walk 514.13ns (this commit). Recompute: node scripts/pmu/commit-triptych.mjs --commit abd5d25c7

Commit artifacts (open on a computer — Gmail mobile won't follow file:// links; the inline images above are the phone-viewable form): reef grid · this triptych · the HDL — all three are also attached to this email.