qcontrol Visibility Storytelling

qcontrol is moving quickly on MCP observation, runtime/session reduction, surface collection, and scanner foundations. The engineering direction is getting clearer, but the visual and narrative layer is still mostly implicit. We need a focused design cycle that translates the most promising opportunities into concrete briefs the team can build, review, and discuss.

This cycle sits on top of c36.qcontrol-integration, c37.qcontrol-file-debug, qmap/c22.runtime-session-map, and the likely future qflow live-session work. Its job is not to settle the engineering architecture. Its job is to define where visualization, UI, communication, and storytelling can make the engineering effort easier to understand, easier to trust, and easier to explain.

Produce a compact brief set for the highest-leverage clarity opportunities around qcontrol, qmap, and qflow, with enough structure that the next design or implementation cycle can pick one up immediately.

The initial brief set should cover:

• layered visibility and handoff across the security stack
• telemetry boundaries
• provenance inspection
• a synchronized abstraction ladder from raw events to story
• session-to-session diffing
• a paired live-view strategy for qflow and qmap

• cycles/c38.qcontrol-visibility-storytelling/ — cycle record and brief set
• cycles/c38.qcontrol-visibility-storytelling/briefs/*.md — goal-oriented design briefs
• shared visual-language guidance for confidence, provenance, reduction, and live state
• framing for standalone value versus hybrid-stack value
• references from ../bob-wire/.claude/agents/brief-writer.md and cycle-manager.md

Out of scope for this cycle:

• building the mocks themselves
• changing qcontrol runtime behavior
• committing to a production information architecture

• Created a new active design cycle focused on the communication layer around qcontrol work
• Added a brief set overview with shared visual-language principles and recommended sequencing
• Expanded the brief set using the updated QControl as Signal framing from QPT.2026.qcontrol-as-signal.2.pdf
• Added observation-handoff-map-v1.md as the first concrete one-page wireframe spec, explicitly paired with telemetry-boundary-layer
• Wrote six goal-oriented briefs, following the bob-wire brief-writing pattern:
  • observation-handoff-map.md
  • telemetry-boundary-layer.md
  • provenance-inspector.md
  • session-abstraction-ladder.md
  • session-diff-view.md
  • paired-live-session-surfaces.md

Initial brief set now covers both session-level trust surfaces and the larger layered-visibility story around where qcontrol sees, where other layers see, and how signal is handed off between them. It is ready for design selection, mockup work, or downstream qmap/qflow experiment cycles.