Source: c62 visibility-stream thread — the sell step the demo lands on, fed by the live digest stream
The demo ends; this is the page that asks for the relationship. Four concepts for a /partner page that sells becoming a build partner — and every number, quote, and story on this page is pulled live from digests/ via /api/digests. Nothing below is hand-written pitch copy; the page practices the same rule as the program: generated, cited, honest.
The receipts
Momentum-first: the cadence promise as the hero claim, immediately backed by computed stats and the actual latest issue. The sell is velocity you can subscribe to — the page proves the promise is already being kept before anyone signs anything.
Build with us while we build it. Partners get a digest every Thursday — what shipped, what's in flight, said honestly. Even quiet weeks. You will never wonder what's happening.
The epilogue with receipts
The tracks-page coda (stack A) gains a third act: replay what the room just saw, then — before the fork — show the last three weeks as partners received them. The demo proved the product; the stream proves the pace. Then the doors.
That was one demo on one day. This is what the three weeks before it looked like — the same digest partners get in Slack every Thursday.
Said honestly
The trust lead: open with the things most vendors hide. Every quote below is a real "Said honestly" entry from the stream. The differentiation isn't the candor claim — every startup claims candor — it's the dated, citable trail of it.
The pitch is that we don't pitch. Every weekly digest carries at least one thing that slipped, stalled, or shipped rough — by rule, not by accident.
qtap (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.
The breaking cutover shipped without a migration guide. If you consume the event stream, the schema diff is in the CHANGELOG but the step-by-step migration notes are still owed — they're queued behind the schema getting its final commit stamp.
The design-site volume above overstates this single week — it's a batch commit of several weeks of work. A weekly digest generated live would have spread these stories out.
Two of this week's three layer tags exist because publishing was broken — v0.9.1 shipped missing assets and v0.9.2 republished after a tag raced a rebase. The release pipeline got exercised; it wasn't graceful.
qtap (the separate eBPF product) had zero changes this week — last commit March 13.
Fifteen honest entries about what will bite an integrator, with workarounds and status. When the first one flips to fixed in vX, it'll be in the digest before it's in any marketing.
The channel
Show the artifact partners actually live with: their Slack channel on a normal Thursday. The digest post is the real latest issue; the threaded human reply and the 🎫 capture demonstrate the playbook's rules (human-shadow, emoji-to-ledger) instead of describing them. The sell: this is what being a partner feels like on an ordinary week.
The control-center story is the one that matters for you — it's the config surface your team asked about in the eval. The connector ask is aimed at you: pick your two and I'll put them at the front of the queue.
Splunk and S3 — and honestly the event stream replay question from our SRE team is a bigger deal for us than either.
The composed /partner page
The concepts are sections of one page, in demo-day order: replay the demo, prove the pace, open the doors, then let the honesty and the channel close the skeptics. The tracks fork (c62 tracks-ideas, stack A) slots in as the doors; the contract stays one click deep. Together the surfaces chain: demo → /partner (this page, the ask) → track detail → portal (the post-signing home).
open question for review: does the honesty wall (idea 3) belong on the sell page or one click deep with the contract? it's the section most likely to be screenshotted — and the section a nervous buyer's boss reads twice.