Pages
Compliance Frameworks — Visual Semantics

Source: /pages/policy-catalog framework grid — c65 iteration surface for framework-card visual semantics (kind label dropped, compliance-shield art replaces the kind icon)

V1 — baseline (catalog semantics: primary tint = active)

Compliance frameworks

Active frameworks require policies — an unmet requirement is a gap that degrades posture.

58% · 7 / 12 policies

8 policies mapped · 5 would need enabling

6 policies mapped · 2 would need enabling

6 policies mapped · 1 would need enabling

10 policies mapped · 4 would need enabling

2 policies mapped · 0 would need enabling

10 policies mapped · 4 would need enabling

8 policies mapped · 3 would need enabling

80% · 8 / 10 policies

7 policies mapped · 4 would need enabling

67% · 4 / 6 policies

5 policies mapped · 2 would need enabling

V2 — surface semantics (active = raised white, inactive = sunken grey)

Compliance frameworks

Same model, same toggles — activation state carried by the card surface instead of the primary tint.

58% · 7 / 12 policies

8 policies mapped · 5 would need enabling

6 policies mapped · 2 would need enabling

6 policies mapped · 1 would need enabling

10 policies mapped · 4 would need enabling

2 policies mapped · 0 would need enabling

10 policies mapped · 4 would need enabling

8 policies mapped · 3 would need enabling

80% · 8 / 10 policies

7 policies mapped · 4 would need enabling

67% · 4 / 6 policies

5 policies mapped · 2 would need enabling

ComplianceTag — reusable layer component

Compliance tag

Shield + name in a grape pill; removable adds the ✕ and emits @remove.

EU AI ActEU AI ActEU AI ActEU AI ActEU AI ActEU AI ActEU AI ActOWASP LLM Top 10SOC 2HIPAA

Qpoint Brand Style Guide