Mark's prompts, verbatim and in order. Written after the fact, at "update histories". No plan preceded the work. What it produced: CYCLE.md § Key Changes, "phase4-simple"; commits d9dac5fd95 and c400dd2afe; q-nuxt-layer 0d1ea8c (v0.9.37).

phase 4, simple items:

compliance page,

• let's use similar in-page-headers to what we're using elsewhere for active / inactive.

Frameworks details page

• table should be full width
• Let's split out the "mapped policies, capablities, configurations, etc" into their own columns
  • mapped policies -> policies, let's use the inline policy view component
  • remove capability
  • to that component, let's add an optional status (inactive, observed, enforced)
  • make findings it's own column and use any existing views for showing findings we are using elsewhere–see big number in findings page
  • let's lose gap column

I've noticed that when the page is more narrow than the table, the table overflows, what can we do to make descriptions, or text collapse more elegantly (overflow elipsis if possible)?

only collapse when table is more narrow than the page

I still see the table wider than the page

Fold a column

let's remove : Forensic why-trail & evidence export — preview. you might want to let the reporst page planning agent know about

ignore that last one. What I was hoping is that somehow as the page shrunk, the various contents of the various columns received ... overflow. Before proceeding, is that feasible, or does that present problems?

yes, go ahead

hmm, I'm on the policies page, ist aht where you're working?

oh , sorry! I've been checking that page

yes please

on the compliance details page:

• Let's lose the language of "risk" what can we replace it with?

Items

this whole section feels old. We have better existing visualizations. Let's to a couple quick revisions on a separate design page to explore

(with a screenshot of framework detail's summary band)

also, let's add a framework detail page into the composed mocks view

do you have a link for previes?

answer to summary band, let's use:

1. coverage : A
2. Mapped policies : B, donut
3. Open findings : C

let's move this to the bottom, or clean up some how:

(with a screenshot of the OWASP description and the guidance disclaimer under the title)

I don't understand the tracked toggle

State + stop link

let's add more gap between the sedtion

*sections

more gap after the description

rename policies column to "policies governing this item"

let's use green, orange grey for mapped policies

let's use black, grey, white for coverage

and just make the filter buttons standard bilter buttons found elsewhere in the site

(with a screenshot of the coloured Fully addressable / Partially / Not addressable chips)

these descriptions aren't that helpful, let's either simplify, or remove :

make more clear

(with a screenshot of the band's three sub-lines)

excellent, I don't think we need the search filter here, remove

(filter items)

much better, small note, any way to make the letf nav item stay highlighted when viewing a sub page? if not, no big deal since this is just a mock

let's build / deploy / push to design.internal.qpoint..

update histories