activecreated 2026-08-15· last activity 2026-08-15
Why
Design's c62 cycle is building a portal for Qpoint's founding build partners — tech teams
integrating qcontrol for AI oversight. Phase-0/1 work (ideation, program-structure survey,
content architecture, sharp-edges content spike) is done in ../design/cycles/c62.build-partner/.
The content is validated; what's untested is the page structure: how the sections order,
how the honesty registry reads at page scale, and how one per-partner page serves two
altitudes (the embedding engineer and their boss).
Objective
Wireframe both c62 surfaces with real content — real cycle names, real sharp-edge entries —
so the structural decisions can be judged before any hi-fi work:
Surface A — Shared portal (one page, all partners): Now/Next/Shipped, Sharp Edges
(qcontrol vs qtap-eBPF split), The Program (cohort + phases + rings), Partner Wall,
Mission & Thesis, Direct Line. Order: momentum first, honesty second, relationship after.
Surface B — Per-partner view (one exemplar partner, synthetic data): Integration
Tracker, Your Stack on the Map (qmap placeholder), Attribution Ledger, Your Sharp Edges
(filtered), For Your Leadership. Explores the two-altitude tension with an explicit
Engineering / Leadership view toggle.