standup
Standup — 2026-07-16
Busy 24 hours.
▶ Watch the 51s summary — Daily standup — Standup 2026-07-16
Daily standup for 2026-07-16. What shipped:
Busy 24 hours. The Brain Content Editor shipped end-to-end: backend (#442) and admin frontend (#444) are both merged. The frontend covers four surfaces — candidate edit-before-approve with taxonomy pickers, DB-native metadata/retire controls, a read-only PR deep-link for git-backed rows, and an underperformer filter on the entry-performance scorecard. Five draft playbooks from the Blending for Good interview landed in #443.
The offline eval harness is done. The build-vs-buy review (#441) chose custom over DeepEval/Langfuse, the fixture-fetch job (#440) produced 319 usable connected-site profiles, and the harness itself (#447) is merged with a compare-runs CLI for regression detection. A first real baseline run against the full dataset locked pass-rate thresholds (#453): denylist ≥ 99.0%, term_overlap ≥ 98.0%, independent gates.
That run also caught one false positive: "cutting-edge" as a bare modifier was too broad and fired on a legitimate Boston Children’s Hospital summary. Narrowed to "cutting-edge solutions" in #451; stale plan docs updated in #452.
The bracket-citation leak fix (#454) closes a customer-visible bug where the advisor emitted raw tokens like [heartbeat] and [site data] inline in answers. Two-layer fix: the SYSTEM_PROMPT citation instruction now scopes brackets to numbered retrieval sources only, and a label-allowlist backstop in the render layer strips any that slip through. The [n] mechanism is preserved — it’s load-bearing for the ADR-0032 retrieval rollup.
Sandbox infrastructure is underway. The plan and Terraform variable widening merged (#439, #445); CI deploy target for sandbox (#457) is live. The actual GCP apply is deferred pending a live session.
Notable. #457 fixed a real footgun: the “resolve target environment” step in deploy.yml previously fell through to the staging (= production) DB for any unrecognized environment value. A sandbox dispatch, before this fix, would have silently run Alembic migrations against the live production database.
Window: 2026-07-15T13:00
→ 2026-07-16T13:37.515Z · Sources: memberintel @ 65c2cf3, memberpress-intel @ f78fd3e