Interface Forensics

Investigate one requested surface. Follow visible symptoms to their implementation causes, then prove repairs in the rendered page. Depth means accounting for meaningful regions and states, not inventing a quota of defects.

Start here

1. Read references/_shared/experience-core.md and references/_shared/experience-operating-contract.md.
2. Define the route/component/workflow, user job, primary action, current state, constraints, and mode: AUDIT or REPAIR. Read references/forensic-process.md.

Core rules in brief. These apply even before you open references/_shared/experience-core.md. Read that file (the full rules and evidence levels) before a full review, repair, or build.