← Cycles
bob-wire · c3activestarted Mar 23Auto draft — not yet reviewed

Dataflows

Looks done — ready to closeAll four status boxes are ticked and the Outcome is written; it was only never moved to HISTORY.md.

To close: Move it from CYCLES.md to HISTORY.md with a Completed date.

last activity Mar 23

Why we did this

Qpoint needed a way to show the paths data takes between systems, and how sensitive the data on each path is.

What happened

Three linked wireframes: a health overview, a sortable list whose rows open into cards, and a detail page with settings. Finished, but never moved to the history file.

New in this cycleAn overview counts all dataflows, the ones carrying sensitive data, and the sensitive ones with no rule covering them.

Start here

At a glance
3
changes
0
conversations
0
decisions
0
outside helpers

What changed

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

  1. 1

    An overview counts all dataflows, the ones carrying sensitive data, and the sensitive ones with no rule covering them.

    How healthy are our dataflows? · came from Mark Parsonopen →

  2. 2

    Each row in the dataflow list expands into a card with the flow's full profile.

    A list whose rows open in place · came from Mark Parson

Also in this cycle
  • A detail page shows what a flow carries and lets you attach rules, alert thresholds and labels. 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

No ruling needed: the work itself is the change.

So now

An overview counts all dataflows, the ones carrying sensitive data, and the sensitive ones with no rule covering them.

Someone said

From the record: no recorded conversation behind this one.

We decided

No ruling needed: the work itself is the change.

So now

Each row in the dataflow list expands into a card with the flow's full profile.

Thanks to

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

MP
Mark Parson
Qpoint team

Asked for the dataflow entity

Wrote the original request (carried over from c2). The record names no one; every commit in this cycle is authored by Mark Parson (git), so the credit is matched from authorship.

All images

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

The pairs

How healthy are our dataflows?New in this cycle

Everything captured · 4

The full record 0 decisions · 0 key-change entries · 262 words · 3 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 c3 →

Qpoint Brand Style Guide