Stage 2. Mark's direction for the frameworks cleanup, given the morning after the 2026-10-26 session with Mark Peterson. One of three cycles kicked off together: c125 Operations Wizard, c123 Compliance Frameworks (this one) and c126 Policies Final Pass. It produced CYCLE.md.

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:

Frameworks Cleanup

• I think the frameworks just needs a good bath and redressing based on latest designs, increased understanding per Mark Peterson. Emerging regulatory pressure to govern your AI. Let's finalize page designs and tune details. Much of this will be manual work with the
  • generate illustrator nippet from current page
  • manual reworking in illustratore
  • building on test page

Automated extraction:

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

frameworks-cleanup.md:

records today's rulings (F1–F9): evidence, not compliance; design for the AppSec reader; version every framework; v1 is OWASP LLM Top 10, NIST AI RMF and SOC 2.

It also itemizes the "Frankenstein" (X1–X11) so your cleanup can be checked against it: two places to activate frameworks, three verbs for it, seven nouns, two evidence exports, three coverage models, and NIST AI RMF missing from the lab data.

The brief

../market-analyst/briefs/frameworks-cleanup.md (2026-10-26, kind: decision). The brief says it "feeds c123; it does not start a parallel cycle", so the cleanup is c123's kick-off rather than a new number. Mark's direction above wins wherever the two disagree.