← Design · c123

intents-pr5-prompt.md

Thread `intents-pr5`: prompt (2026-11-05)

Mark's messages, verbatim. What it produced: intents-pr5-evaluation.md → intents-pr5-plan.md → intents-pr5-review.md.

I'd like to integrate the updates to the ../intents repo–in particular the changes encapsulated in PR 5 (https://github.com/qpoint-io/intents/pull/5/). Let's start by analyzing the changes, evaluating against our composed mock-ups (primarily : reports, compliance, and policies) and create a plan for integrating the latest into our composed mock-ups. This can be part of the most appropriate existing cycle

let's create evaluation and plan.

(one item to note, I just merged that PR into main)

A couple of thoughts, then let me know if there is still ambiguity.

  • In general, we are only going to report percentages on things that we can know. This is less about how much of a framework we are compliant to in the abstract–we recognize there is much in a particular framework that is beyond surface area we can illuminate and govern. We don't need to pollute our percentages with things we have no relevance to.
  • merging the PR wasn't meant to settle anything over the Nov 4 metric I speak of percentages, but really all of our posture is included here

let's review everything at the end

Framework Details :

  • Data Machine, let's show a pie chart breaking down the exceptions
  • Can we add a framework that is 100% to see what that looks like?
  • let's move the over time to the top

Reports:

  • Compliance, is there any way we can add the posture over time to this report

Let's review decisions after these changes

  1. a
  2. a
  3. b
  4. a
  5. a

before the next decisions, let's make the enforecement over time very short

hmm, that may be a bit too short, let's revert it and move it to the bottom of the page

let's remove these sections : (a screenshot of Not mapped by Qpoint and Supporting evidence)

  1. a
  2. a
  3. a
  4. a

5 a

let's change the red to orange for loosen everywhere

when there is nothing left to tighten with the enforcement policy, let's use light green for items that can't be enforced–so that bar in the DataMachine would be light green

we lost our quick framework tracker at the top of the policies page, probly for a reason, why? ie add framework

a

Qpoint Brand Style Guide