Source: c62 build-partner — Surface A, the shared portal. Painted directly from content-architecture.md + sharp-edges.md (no wireframe pass).
This band is generated from the cycle system and the sharp-edges registry — it is never hand-edited.
Now
active cyclesNext
queuedOrder shifts with partner feedback — that's the point.
Shipped
ship logSharp Edges
10 of 15 shown · reviewed every releaseThe honest list. Every edge names what it affects, a workaround (or says "none"), and where the fix stands. If you hit something that isn't here, that's a bug in this page — tell us.
Selective MITM learns exclusions by observing a cert rejection — so the first request to a pinned endpoint breaks before the exclusion exists. Later connections work.
Child processes inherit proxy env but often honor only HTTPS_PROXY and reject the MITM cert. Our own assessment: current endpoint-based exclusions are not a sufficient fix.
When process attribution fails or times out, the connection falls back to raw tunneling. Traffic flows; you see nothing — a gap, not an error.
The event socket is a bounded live stream: brief buffering while a collector is down, drops under pressure, no replay. Snapshot restores current state, not missed history.
No agent injection, no OS trust-store management, no per-process attribution, no live telemetry — and identity enforcement proceeds without the control applied.
Adapter-grade understanding exists for Claude Code, Codex, Cursor, and OpenClaw. Other agents can be tapped, but without adapter depth.
cost_usd is empty on every provider — even where the wire carries cost, the schema has nowhere to put it yet.
Because it wraps TUIs, all diagnostics — including pre-launch failures — go to log files, never the screen. A non-working tap looks like nothing happened.
If you also deploy the qtap eBPF agent
separate product — separate requirementsGo crypto/tls, Java JSSE, and Node TLS are not yet implemented — a Go or Rust AI workload will not have its TLS decrypted.
Kernel 5.10+ with BTF and an effectively-privileged container. Captured messages cap at ~120 KiB (large LLM bodies truncate), and capture is best-effort under load — loss is a first-class metric.
The Program
Founding cohort · week 4 of 12The program has rules and they're written down: five phases, a real end date, and a real ask at the end. Where the cohort stands is always visible — including to each other.
- · A real integration, not a lab — qcontrol on the machines your agents run on
- · A 30-minute structured session every two weeks
- · Honest signal, especially when it's bad
- · A yes/no conversation at week 12 — paid pilot of the next phase
- · A numbered founding seat, priced like one — locked at conversion
- · Direct line to the people building it (below)
- · Your asks visibly reordering the roadmap — with your name on the ship log
- · This portal: the same view of the project we have
Founding Partners
6 seated · 2 seats reservedWhy we're building this
Every org is quietly becoming an AI company — not by strategy, but by installation. Agents arrive on laptops, wire themselves into repos and credentials, and start acting. The org chart didn't change; the actors on it did.
Oversight tools built for humans watch the wrong layer. We think the right layer is the seam where agents touch the world — the process, the connection, the credential — and that visibility there has to be honest about its own gaps to be worth trusting. That's why this portal has a Sharp Edges page and why it will never be empty.
The long version — the one to send your leadership — lives in the thesis doc, alongside how we work: small numbered cycles, shipped weekly, in the open with this cohort.
Direct Line
Everything you raise — in Slack, in sessions, in the feedback queue — lands in the attribution ledger. When it ships, the ship log says so, by name.