OpenHouse vs Simple Analytics

OpenHouse ships continuously — five releases in the twelve days covered here — with each tag carrying a single merged pull request. The substantive recent work sits in two areas: table governance, where CREATE OR REPLACE AS SELECT was silently dropping retention, replication, history and PII column tags, and operability, where the DataLoader gained a typed exception hierarchy with per-request IDs and the scheduler gained targeted log tokens. Table feature toggles also picked up self-service overrides that let table owners opt in to a feature the server has not ramped.

The project is at the stage where correctness at the edges matters more than new surface: policies surviving a replace, auth failures not being retried as if they were transient, scheduler decisions being greppable in production logs. The observability work is explicitly phased, with OTEL gauges and DLQ counters deferred to a later step, so instrumentation is being staged rather than dropped in at once. The pattern of one PR per release tag means the feed reads as a commit log and the meaningful changes have to be picked out of dependency bumps.

Phase 2 of the jobs observability plan — OTEL gauges, a heartbeat sampler, and dead-letter-queue counters — is named in the notes as deferred and is the most likely next substantive change.