Handbook

Quality lane

Forge quality tooling spans deterministic auditors, accessibility products, and Fleet-hosted UX workers. Each has a distinct job; platform docs name boundaries — not full runbooks.

Updated

Tool map

Tool Repo Job Typical output
KS website UX auditor forgesdlc-kitchensink Deterministic UX metrics + optional AI judgment analyze-website-ux.mjs report
KS website a11y auditor forgesdlc-kitchensink axe + deterministic a11y rules a11y audit JSON
forge-a11y-checker forge-a11y-checker Wrapper scripts invoking KS a11y auditor run-a11y-audit.sh
A11y Studio forge-accessibility CDP + axe in Electron; sealed remediation loops combined CDP+axe score
fleet_ux_worker Fleet job container In-container audit/remediation under ForgeRun worker_progress, worker_result

How they relate

  1. Local / CI — KS auditors and a11y-checker run against static sites or fixtures without Fleet.
  2. Interactive studio — A11y Studio uses KS tools/ui-app-audit/ patterns for app-level CDP audits.
  3. Governed campaigns — fleet_ux_worker runs inside Fleet workspace under a Lenses ForgeRun; results return via WorkcellResult.

See intersection map — Quality-lane intersections.

Design system source of truth

Visual hash catalog, design contracts, and UX remediation plans live in Kitchen Sink — not in platform or a11y-checker repos.

Does not own

Quality tools do not approve releases, own ForgeRun state, or replace human review in Lenses.