← Cycles
design · c19archivedstarted Mar 13Auto draft — not yet reviewed

Security Policy Slot

Why we did this

The security design shows each policy card with its violations table beside it. The card had no room for that, and the little data-flow picture had no shared part.

What happened

The card gained a space beside it for the violations table, and a new part draws the data-flow picture: a dot, a tag like PII, and an arrow.

Early → finalA policy card can now show a table of its violations right beside it; cards without one look the same as before.
At a glance
3
changes
0
conversations
1
decisions
0
outside helpers

What changed

The two changes that matter most, in plain words. Open any one to see it.

  1. 1

    A policy card can now show a table of its violations right beside it; cards without one look the same as before.

    Violations beside the policy card · came from Mark Parsonopen →

  2. 2

    A new shared part draws where data went: a dot, one or more data tags, and an arrow.

    A picture of data on the move · came from Mark Parsonopen →

Also in this cycle
  • When the page got narrow, the violations table spilled out; now it scrolls sideways inside its panel. In words

How we got here

Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.

Someone said

From the record: no recorded conversation behind this one.

We decided

c19-D1 Use a slot beside the card rather than new props, so pages compose whatever sits next to it. — Mark Parson

So now

A policy card can now show a table of its violations right beside it; cards without one look the same as before.

Someone said

From the record: no recorded conversation behind this one.

We decided

No ruling needed: the work itself is the change.

So now

A new shared part draws where data went: a dot, one or more data tags, and an arrow.

Thanks to

People outside Qpoint first. Every thank-you points at something they said or made.

MP
Mark Parson
Qpoint team

Built the card-plus-violations composition

Gave the policy card room for a violations table beside it, as the security design shows, and made the data-flow picture a shared part.

All images

Every picture from this cycle. Click any one to step through them all.

The pairs

Violations beside the policy cardEarly → final
→
A picture of data on the moveNew in this cycle

Everything captured · 3

The full record 0 decisions · 3 key-change entries · 175 words · 1 captures

The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.

Open the record for c19 →

Qpoint Brand Style Guide