waggle-os/docs/addictiveness-audit-2026-05-28/PLAN.md

Waggle OS · Addictiveness + 10-Persona Audit

Started: 2026-05-28 · Goal: 10/10 across 10 personas on addictiveness, become "the one AI tool" they need.

Constraint from saved rule (workflow-reality-check)

Each persona's workflow must be grounded in where their traces ACTUALLY live, not invented friction. Cross-platform claims need a concrete user-trigger; generic "this segment matters" doesn't clear the epistemic gate.

Order (per user instruction)

1. Benchmark research — OpenClaw, Hermes, Claude Cowork, Claude Code-for-non-coding
2. Addictiveness rubric — Hook model adapted to AI assistant
3. 10 personas — across tech-knowledge spectrum, epistemically grounded
4. Baseline audit — score current build per persona
5. Triage + surgical fixes — minimal diffs, per CLAUDE.md §3.3
6. Re-audit + iterate until 10/10 each
7. Feature requests — synthesize what each persona wishes existed

Distinct from prior UX audit

The 2026-05-27 audit (1dc7df3 / 57f6f04) covered USABILITY (can users complete tasks). This one covers ADDICTIVENESS (do users come back / make Waggle the one tool). Different rubric, different fixes.

Files

• BENCHMARK-{openclaw,hermes,cowork,claude-code-nc}.md — competitor cards
• RUBRIC.md — addictiveness scoring dimensions
• PERSONAS.md — 10 personas
• BASELINE.md — per-persona baseline score
• FIX-LIST.md — triage
• ITER-N.md — iteration results
• FEATURE-REQUESTS.md — synthesis
• screens/ — visual evidence