Stage 1, captured 2026-10-27. One of three cycles kicked off together from the Qpoint Product session of 2026-10-26: c125 Operations Wizard, c123 Compliance Frameworks (the frameworks cleanup) and c126 Policies Final Pass.

Mark's prompt (verbatim)

Based on yesterday's "Qpoint Product" I want to kick off 3 cycles of design development. The three initial briefs were written by ../market-analyst (See below). I will provide additional context and direction for each cycle:

Operations wizard:

we are going to build a tour-guide/self documentiong tool for easing onboarding, setting config, understanding the guides, etc. We need a way to step through tasks, mnavigate through pages, highlight sections of the ui, show expanatory text. The UI becomes the documentation.

Prior Art - Ableton live has a help window, when active, hovering over any aspect of the UI will show explanatory text about what the thing is, and how to use it.

• We are designing a tool / component that can be attached cleanly to sections of the UI
• We want a mode where hovering over aspects of the UI will help you to understand
• I've also imagined having a mode where we would overlay brighly colored circles–white outline, subtle drop shadow. This allows us to explain aspects of the UI
• I want to include an AI tour guide from the beginning. MCP Server. Fire up our dashboard and your favorite harness, and let it give you the tour.

Automated extraction:

The three automated extraction briefs, favor the above when these disagree. Favor the above for the spirity of what the cycle is.

operations-wizard.md:

the journey the session settled on is people and endpoints → deploy → visibility → recommended baseline at Observe → frameworks → enforce for a pilot team through an exception → expand. It lists the existing prior art Parson mentioned. The closest is the old qdash "Get started" checklist, which shipped and was then removed. Others are c121's adoption stage and the app.qpoint.io wizard kit. Your "starting from HIPAA" idea is recorded as rejected: Peterson said start from a secure-environment baseline, then layer frameworks.

The brief

../market-analyst/briefs/operations-wizard.md (2026-10-26, kind: problem). Mark's direction above wins wherever the two disagree, and sets the spirit of the cycle: the brief describes a journey; Mark's cycle is the tool that makes any journey, and the UI itself, explain itself.

Create a plan, ask any clarifying questions, suggest patterns I may not be considering.