Resolute — programme activity

1 · Sale sites

The two sale-day field-sheet applications. Reachability was probed by HTTP GET from the Mac Studio at build time; everything else in this section was measured on 2026-08-12 and is carried forward.

The parity gap — 11 features Keeneland lacks that Saratoga has

Scope: enumerated by reading both source trees on 2026-08-12; each entry was confirmed by a grep of the Keeneland tree that returned no implementing code. Not re-measured on this build.

2 · Data warehouse

Scope: RESOLUTE_MIND.RACING_DATA. Every figure is a real SELECT COUNT(*) executed at the measurement time above — not the SHOW TABLES / INFORMATION_SCHEMA estimate. The total covers all 122 base tables in the schema, not only the rows listed here.

The gaps — base tables holding exactly zero rows

Scope: the same query as above. A table appears here only if its real count is exactly 0. An empty table is a measured fact; it is not the same thing as a table that failed to be measured, which would read ERROR.

3 · Extraction fleet

PRODUCING = wrote at least one row in the last 24 h. STALLED = wrote rows within 7 days but nothing in the last 24 h. DEAD = wrote nothing at all in 7 days, however many times it ran.

Collected and derived are reported separately on purpose: the derived lanes manufacture hundreds of thousands of rows a day out of data the warehouse already holds, and adding the two together hides a collection failure completely.

External collection lanes

Derived / internal lanes

Scope: RESOLUTE_MIND.RACING_DATA.SCRAPER_LOG, one row per run. The 24 h and 7 d columns are SUM(RECORDS_WRITTEN) and COUNT(*) over RUN_STARTED_AT within that window. “Days since last productive run” is DATEDIFF from MAX(RUN_COMPLETED_AT) WHERE RECORDS_WRITTEN > 0 over ALL TIME, so it is not capped by the window; a lane with no productive run anywhere in the log reads never. Nothing in this table reads the STATUS column.

4 · Freshness

How old the newest row is, per source, for the two data classes the sale sites and the analytics depend on.

Races — days stale by source

Scope: RESOLUTE_MIND.RACING_DATA.RACES, grouped by SOURCE_SITE. Days stale is DATEDIFF(day, MAX(RACE_DATE), CURRENT_DATE()) at the measurement time above. Note the two duplicated source spellings (sportinglife vs sportinglife.com, HRN vs horseracingnation.com): they fragment any GROUP BY, including this one, and are listed here exactly as they appear in the column rather than merged.

Sales — days stale by source

Scope: RESOLUTE_MIND.RACING_DATA.SALE_ENTRIES, grouped by SOURCE_SITE. Days stale is DATEDIFF(day, MAX(SALE_DATE), CURRENT_DATE()) at the measurement time above. This is the most degraded lane in the warehouse, and it is the table the Keeneland September comparables are built on.

5 · What remains

The work still to be executed, counted from the three companion documents that sit alongside this dashboard, plus the defects filed and not yet fixed.

Scope: these counts are parsed out of the companion documents themselves at build time, from /private/tmp/claude-501/-Users-abbiadmin/276e123c-6e99-46e3-a2c1-01644f8e81a5/scratchpad, by counting distinct item identifiers. They are not transcribed by hand and so cannot drift from the lists. If a document is unreadable the last successful count is shown with its date and marked stale; if there has never been one the cell reads ERROR.

Open defects — filed, none fixed

Scope: the four defects filed against the Resolute programme and open as of 2026-08-12. Recorded, not re-measured on this build.

6 · Keeneland site readiness

Feature-by-feature parity against the Saratoga build (section 1 above lists all 11 parity gaps in full; this checklist is the PM tracking view of the same work, plus items Saratoga does not have either). DATA-BLOCKED means no engineering unblocks it — the item needs data that will not exist until the sale itself runs.

Scope: recorded 2026-08-24, last updated 2026-08-24 via pm-state.json. This is a tracked checklist, not a live measurement — it changes when the work changes, not on every build.

7 · Open items & actions

Every open action across the programme, one owner and one due date each. Edited directly in pm-state.json alongside this generator, so ownership and status can change without a code deploy.

Scope: 6 item(s), source pm-state.json, as of 2026-08-24. Two items are Architect unlocks (a credential only he holds), not engineering tasks — they cannot be closed by building anything.

8 · Project timeline

Days remaining, counted from this build's measurement time to Keeneland September 2026 (Sept 14–26).

Preparation window 2026-08-01 → 2026-09-14 — 52.3% elapsed

Milestones

Scope: dates are fixed calendar constants in this generator (Keeneland September 2026-09-14–2026-09-26, milestone due dates matching section 7); days-remaining is computed live at each build against the measurement timestamp above. The preparation-window bar's start date (2026-08-01) is a display anchor for the bar's width, not a recorded project-kickoff date.