archivedcreated 2026-09-11· last activity 2026-09-11
Why
The security dashboard vision (c11) shows policies with adjacent violations tables. The PolicyCard was props-only with no way to compose detail content alongside it. The data-flow visual (source → data-type tags → destination) is a core Qpoint concept that belongs in the shared layer.
Objective
Add a default slot to SecurityPolicyCard for adjacent content (e.g. violations table), and create a SecurityDataFlow component for rendering data-type tag flows.
Scope
Layer: Default slot on security/PolicyCard.vue, new security/DataFlow.vue
Design site: Demo files for both components, component registry entries
PolicyCard stays backward-compatible — no slot content = same render as before
Key Changes
SecurityPolicyCard now accepts a default slot; when present, renders card + slot content side-by-side
SecurityDataFlow renders ●--{PII}--> visual pattern with configurable types and color palette
Demo shows PolicyCard with a UxTableList violations table in the slot, matching the c11 wireframe
Outcome
Two new reusable primitives in the layer. The violations-beside-policy composition is documented and demoed on the design site.
Visual record
3 captures — heroes, page slices, and full-page renders. Click to view.
