The tape is the header now

The timeline is no longer a view you switch to. It is a strip across the top of the earnings room that never leaves the screen, and the view underneath — MONTH, WEEK or DAY — follows whatever you tap on it. One bar can be a day, a week or a month, so the whole season fits on one screen or a single day can fill it. Nothing is deployed: branch hub/earnings-4-20260923, built from Hub production b6913cb.

“I do like this timeline view, but it's very thin. So how about just having it on top of the other views, more like a header.” · “There's a blue line. I'm trying to click on it and it doesn't say… nothing. On the 23rd. October. I don't get it.” · “It's requiring a lot of scrolling… don't you think it should be a little more dynamic to zoom? I feel like it's empty. I'm going to the week view… no report.” · “What happened to the daily view? … The daily view just has a scrolling downwards.”

1 · What the page shows

The earnings room has three parts now, top to bottom:

• The span bar — the day, week or month you are looking at, one pair of arrows to step it, TODAY to come home, and the three views.
• The tape — about 110 pixels of season. Each bar is how many of the names the Hub tracks report in that bucket. Its colour is that same number, on the load law the MONTH view already used: cyan under 12, orange from 12, red from 25. Under it, one line says what the room is showing and how many reports are on the tape.
• The view — MONTH, WEEK or DAY, of whatever the tape points at.

The one thing that moves and the one thing that never does. Bar height is scaled to the busiest bar actually on screen and re-scaled as you drag, so a quiet fortnight still has a shape. Colour is never re-scaled: red always means 25 or more reports, in season and out of it.

As it opens — today, out of season

Zoomed out — two years in one screen

In season — a heavy November day

2 · The blue line, and everything else that said nothing

The blue line was today. It was drawn as decoration, so it had nothing to say and nothing happened when you clicked it. Now it is a real mark with words on it: “the cyan line is TODAY, WED SEP 23 — everything left of it has happened, everything right of it is still to come”. And every other mark answers too:

The bar you are looking at is highlighted on the tape, so you can always see where the view below is standing. Zoom is the three buttons, a pinch, or ⌘/ctrl and the wheel; a plain wheel or a drag still walks the season sideways.

3 · “I feel like it's empty” — it wasn't empty, it was narrowed

It was your FAV strip: three names rarely report in the same week. Nothing on the screen said so. Two changes:

• The earnings room now opens on ALL names and says so on the tape. Tapping a cohort while the room is open still narrows it; leaving and coming back starts wide again. Your saved strip, and every other room, is untouched.
• When a narrowed strip finds nothing, the room says what is missing — on the tape and inside the view — and offers the one tap back.

4 · The daily view, without the fall

DAY keeps everything it had, but the day is read across now: before the open · at a set time · after the close · time not announced. Each heading takes width in proportion to how many names sit under it, and a busy heading wraps its names instead of running off the bottom. The older UPCOMING | PAST · REPORTED list is still there, one click below, under “everything upcoming and everything reported”.

5 · Where each number comes from

The tape writes nothing, anywhere. Neither does the room.

6 · Report times keep themselves current now

The earnings catcher does exist, and it works. It is the Supabase function fmp-events (v2), run by the schedule fmp-events-2h every two hours: it sweeps FMP's earnings calendar from a week back to three weeks ahead, walks the universe 30 names at a time, and upserts into earnings_events on ticker + date.

Why it carries no times. Its row builder writes exactly seven fields — ticker, date, EPS actual, EPS estimate, revenue actual, revenue estimate, surprise — and report_time is not one of them. It never has been. That is the whole reason Costco, Micron and ASML said “time unknown”: nothing was ever writing that column.

What is added here. A second, small function, earnings-report-time, scheduled by pg_cron for 09:23 New York on weekdays. It is the same fill that was run by hand on 23 September, with the same four rules:

• It never guesses: when Nasdaq's calendar says “time not supplied”, nothing is written and the card goes on saying the time was not announced.
• It never overwrites: the write itself carries report_time=is.null, so the database — not just the code — refuses a row that already has a time.
• It matches on ticker and date. Where our date and the source's disagree it writes nothing and reports the disagreement.
• It touches three columns: the time, where it came from, and when it was written. Never a price, an estimate or a result.

It runs one at a time (a flag in app_config), leaves its last run's counts where anyone can read them, and reads its key from the Supabase environment. No key is on any Mac, and neither file contains one. Rolling it back is one line, written at the top of the migration.

Honest gap: this estate's other schedules live only inside Supabase, so there is no example in git of how they pass their bearer. The migration reads it from Vault by name and says, in its own comment, to use whatever pattern the existing crons use if that differs. The coordinator applies it; nothing was deployed or scheduled from here.

7 · What could be wrong

• The tape only knows what the calendar knows. Zoomed to months, next spring shows 2 and 1 — not because the season is quiet, but because those dates have not been published yet. The shape of the far right of the tape is a picture of coverage, not of the future.
• Nearly every upcoming report still has no time. On 4 November, 37 of 38 sit under “time not announced”. The new job fills the next 45 days each morning where Nasdaq states a time; beyond that window, and for names Nasdaq does not carry, they will stay unannounced.
• Two years of tape is 1,658 rows, read in six requests. Each request is capped at 1,000 rows, and if one ever came back full the line under the tape says so. It has not, at this universe size.
• A weekend-dated report gets its own bar rather than being dropped, but it will look odd sitting between a Friday and a Monday.
• The room opens wide on purpose. If you want FAV, it is one tap — but it is a tap every time you come back. That is the trade for never opening on an empty screen, and it is a decision below.
• Nothing here was tested in a live session. The market was closed; everything above is the stored calendar, which does not change during the day.

8 · What was not done

• Nothing was deployed, pushed, scheduled or written to the database. The branch is local; the migration and the function are files for the coordinator to apply.
• The report-time job has never run. It is a port of a script that ran and filled 44 rows; the function itself has not been invoked, here or anywhere.
• No pinch gesture was tested on a real trackpad — the zoom is wired to ctrl/⌘ + wheel, which is what a trackpad pinch sends, but I only exercised it in code.
• The older UPCOMING | PAST list was not rebuilt, only folded away. It is the same list, with the same contents.
• Two test failures already on production are still failing — the age-function check and xfeed-publish — and are not touched by this work. Everything else passes: 461 tests, 457 passing, the 2 known failures, and 14 new tests for what is above.

9 · Three decisions for you