Skip to content

Distinguish ADHD frames from personas (A5) and from domain specialists (Han-style) #17

@UditAkhourii

Description

@UditAkhourii

External research review by u/mxriverlynn correctly noted that the paper's positioning of ADHD frames conflates three structurally distinct mechanisms:

  1. Personas (A5: Examining and Addressing Barriers to Diversity in LLM-Generated Ideas) — simulated identities with user attributes ("you are John, 34, from Ohio"). A5 finds ordinary personas outperform curated expert personas. The mechanism is specificity in user-attributes.

  2. Domain specialists (Han plugin's adversarial-security-analyst, devops-engineer, user-experience-designer, etc.) — role-grounded reviewers with domain-scoped briefs. They read the artifact under review.

  3. ADHD frames (this project) — vantage operators that force structural re-framing of the problem itself ("you think in latency, memory layout, and physical constraints"). Off-domain by design. Not identities.

The paper currently allows readers (and reviewers) to map ADHD frames onto the persona literature, inviting the A5 contradiction as Han's review did.

Action:

  • Add a subsection in §2 (Related Work) titled something like "Frames are not personas."
  • Explicitly distinguish frames from personas and from domain specialists.
  • Note that A5's "ordinary beats expert" finding is about specificity in user-attribute personas, which is orthogonal to vantage reframing.
  • Cite Han's domain-specialist parallel review architecture as a related-but-distinct prior pattern.

Raised by u/mxriverlynn in adhd-application-to-han.md. The Han plugin already implements parallel fan-out with domain specialists, which is a legitimate prior pattern that the paper does not adequately differentiate from.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationmethodologyMethodology critique or clarificationpaperPreprint paper updates

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions