Dataflows

Define the information architecture for Dataflow — a new entity representing a pathway between two endpoints. Validate the IA through lo-fi wireframes before investing in visual polish.

• Dataflow overview (health dashboard)
• Dataflow listing (sortable table with expand-to-card)
• Dataflow detail (informational + configuration)

1. Goal-oriented brief covering all dataflow pages
2. Lo-fi wireframes (Wire* components) for overview, listing, and detail pages
3. Connected flow between all pages

Three wireframe pages define the Dataflow entity IA:

• Overview — landscape health dashboard with 6 aggregate metrics, sensitivity distribution (Critical/High/Medium/Low), governance gaps table, and recent discoveries
• Listing — sortable table with 6 filters (source/dest, sensitivity, coverage, protocol, encryption, data type), inline expand-to-card showing full flow profile with data type badges and connection preview
• Detail — full entity page split into informational (flow identity, 8/26 data types with instance counts, traffic profile with trend chart placeholder, connection inventory, policy coverage with violation cross-link) and configuration (policy assignment, alert thresholds, labels/tags)

Cross-feature link to c1 policy-compliance violation page established.

• initial-prompt.md — original requirements (copied from c2)
• datatypes.json — 26 data classification types (copied from c2)

• Brief written — cycles/c3.dataflows/briefs/dataflows.md
• Wireframes generated — app/pages/c3/wireframes/dataflows-v1/ (overview, listing, detail)
• Review complete — minor fixes applied (governance gap links, timestamps, view-all button, cross-feature violation link)
• Flow connected — all pages linked via WireNav + contextual links, flow overview page added