Rule handbook metadata

Rule: DET.THEME.FONT_STACK · lane deterministic
Page status: current
page_version: c1e1ed0bc84d27c4a0d298f0237d5e132a29c3039df3f7c0b6083e24a63cb0c3
generated_at: 2026-05-25T13:41:26Z
registry_fingerprint: 2ce40848effce579d3e4879f6ca85535183a14db201870a6c007da424624550c

How this rule is fixed

Not in the deterministic fixer pilot registry (stub or not yet wired). Use the After example below as the target state and remediate manually or extend pilot-registry.json.

Detection module: docs/design/ux-audit/deterministic-design-rules.md#det-theme-font_stack. Scroll down for Before / After examples and Evidence and remediation steps.

Purpose

Bootstrap page for the DET ruleset harness. Examples are minimal Kitchen Sink markup aligned with design-rules/deterministic/generated/det-theme-font-stack.check.js.

Passing signals

After example satisfies the rule on audit.

Failing signals

Before example triggers DET.THEME.FONT_STACK on the defect fixture.

Before example

Before (failing example)

Font stack drift

Wrong display stack

Body uses non-token font-family.

After example

After (passing example)

Approved font stacks

Display uses Forge stack

Body and labels use theme token stacks only.

Evidence and remediation

Run generator/build_rule_defect_fixtures.py and auditor-tests/invoke-det-ruleset-harness.sh --only-rule DET.THEME.FONT_STACK.