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-studio-mechanism_lead. Scroll down for Before / After examples and Evidence and remediation steps.

Purpose

Studio operators are not maintainers reading an ingestion README. The first paragraph after H1 should answer what they can do here (find, compare, track, review, watch, monitor)—not which harvest job or API endpoint powers the screen.

DET.STUDIO.MECHANISM_LEAD flags leads that open with mechanism vocabulary (harvest, API, pipeline, EDGAR, XBRL, multi-select) without outcome verbs in the same snippet.

Plan: Read the lead aloud as an analyst. Do: Rewrite one sentence for outcome; move mechanism to a disclosure link or footer meta. Check: page.json.lead_text passes heuristic. Adjust: Keep technical labels on controls, not in the hero lead.

Passing signals

• Lead: Review and compare the issuers you are tracking.
• Mechanism detail in Show details disclosure, tooltips, or handbook links.
• Primary CTA label is outcome-shaped (Open watchlist, Compare selected).

Failing signals

• Lead: Harvest EDGAR filings into the pipeline API for XBRL facts.
• Lead opens with internal codenames before scope or outcome.
• Empty lead while dense mechanism copy fills the first card title.

Before example

After example

Evidence and remediation

• Scorer: lead_text in page.json from capture-page.mjs.
• Axis: human_outcome in GPT assessment.
• Copy pattern: forge-enterprise-app-ux-standard.md.

Related rules

• DET.STUDIO.TITLE_NAV_MATCH — identity before copy polish.
• AI.DASHBOARD.ACTIONABILITY_PRIORITY — next step visible after outcome lead.
• AI.CREDIBILITY.NO_OVERCLAIM — bounded capability statements.