Source: c62 visibility-stream — the partner's actual home page, show-not-tell pass
The page a partner opens on Thursday. One glance answers what moved, what to watch, what's stuck; every card expands to the digest prose it came from. All content is live from /api/digests — the board is a projection of the stream, not a second thing to maintain.
Shipped
tap a card for the storyWatch out
said honestlyqtap (the separate eBPF product) had zero changes this week — last commit March 13. If your deployment includes qtap, qcontrol is where all current velocity is.
Nothing flipped to fixed on the sharp-edges registry this week. The adapter expansion above is the closest thing to edge movement.
Moving
in flightfeat/control-center — everything in "Shipped" above, verified end-to-end in headless Chromium against a live backend; lands on main…
Migration notes for the unified monitor cutover (shipped last week, see Issue #2) — coming with the next schema stamp.
Windows binary packaging remains paused (#619) — Windows support is on the plan (docs/plan/windows-support.md) but nothing shipped this period.
The connector catalog launched with 11 integrations chosen from research, not usage. Which two would you actually wire up first? That answer reorders the queue.
Generated from the weekly digest — never hand-edited · full issue text in Slack · a quiet week shows up here as a quiet board, and says why
Design notes: the glance layer is dots, counts, chips, and bold leads — no sentence required to get the week's shape. Prose exists only behind "+ details" (the digest story bodies, verbatim). Evidence chips are auto-extracted citations (PRs, versions, cycles, SHAs) from the digest text. Week chips carry activity bars so the rhythm is visible before any reading. Open question for the next pass: should "Watch out" entries link to their sharp-edge registry entries when one is referenced?