// SLIDE 05 — SUBSEQUENT RUNS — COMPARE AGAI

SUBSEQUENT RUNS — COMPARE AGAINST BASELINE

node monitor-brand.mjs --rules=brand-rules.json --out=compliance-run-2 \ --baseline=compliance-run-1/compliance-report.j

NARRATION

node monitor-brand.mjs --rules=brand-rules.json --out=compliance-run-2 \ --baseline=compliance-run-1/compliance-report.json

// SLIDE 09 — WHAT COMES NEXT

WHAT COMES NEXT.

Chapter 12 handles the consumer that is not a human at all — structuring the Figma file's data as a machine-readable spe

NARRATION

Chapter 12 handles the consumer that is not a human at all , structuring the Figma file's data as a machine-readable specification that a CLI or code generator can build from. The compliance report is input to that process: a file with known-passing compliance is a file the code generator can trust.

// SLIDE 12 — CLOSE

ASK THE QUESTION. APPLY THE FRAMEWORK.

DEFINING THE RULES//THE CONTRAST CALCULATION//MONITOR-BRAND.MJS

Brutalist Figma + Claude · Ch.11 · Chapter 11 — Brand Compliance Monitoring

NARRATION

That is the framework. Brutalist Figma + Claude, chapter 11: Chapter 11 , Brand Compliance Monitoring. The patterns are now in place. Apply them.