## Intel — 2026-02-16

### 1) Data Pattern Recognition (Velocity, Engagement, Adoption, Pain Correlation)

**Engineering throughput (GitHub, month-to-date window 2026-02-01 → 2026-03-01)**
- PRs: **25 opened / 18 merged** (merge rate **72%**)
- Issues: **33 opened / 37 closed** (net issue backlog slightly improving)
- Contributors: **28 active**
- Code churn: **+18,576 / -3,807** across **160 files**, **93 commits**  
**Trend:** high output with heavy architectural change (multi-language core, auth, filtering). Elevated review/QA risk due to large-scope PRs and cross-cutting refactors.

**Development focus signals (last week context)**
- Core security + multi-user safety landed (JWT auth system, data isolation path).
- Performance/cost work is emerging as a first-class theme (ActionFilterService; scenario cost evaluator issue recently closed; media caching in plugin-openai).
- Ecosystem/plugin economy expanding quickly (new registry additions; chain/rpc resilience work).  
**Risk:** platform stability and “golden path” onboarding lag behind breadth of integrations.

**Community engagement patterns (Discord 2026-02-13 → 2026-02-15)**
- Discussion volume dominated by **token migration closure** + “no recourse” outcomes; repeated questions indicate ongoing discovery of missed deadline.
- **Security/scam events spiked** in “coders” threads (fake support workflows).
- Product positioning repeatedly challenged: “framework not tied to token,” “non-technical users can’t realize value,” and “roadmap lacks concrete milestones.”
- Adoption friction shows up as deployment questions (Spartan agent) and operational issues (thread permissions, support channel closure).

**Pain point correlation across channels**
- “Cost & duplication” theme appears in both product and platform:
  - GitHub: URL-triggered **duplicate LLM calls** (#6486), **image content stripped** in cloud chat (#6494).
  - Discord: token utility skepticism + need for clearer value proposition; both map to users questioning ROI and operational reliability.
- “Trust & safety” theme appears in both:
  - Discord scams + need for permission tightening.
  - GitHub security improvements underway, but community-facing security controls lag (Discord ops).

---

### 2) User Experience Intelligence (Themes, Impact, Sentiment, Opportunities)

#### A) High-impact UX failures / trust breakers
1) **Token migration dead-end (Critical, trust damage)**
- Users missed a **hard deadline** and were told there’s **no remediation** even with on-chain proof of long-term holdings.
- Observed behavior: repeated requests to reopen tickets / manual processing; distress and “punished loyal holders” framing.
- Sentiment: acute frustration; values mismatch (“decentralization/community”) narrative risk.

**Implementation opportunity**
- Even if policy stays closed, users need a **clear, immutable source of truth** + a **single authoritative FAQ** and visible “closed” messaging *where users search* (Discord channels, pinned posts, website, X).

2) **Discord scam surface area (Critical, user-loss risk)**
- At least **one identified scammer ID** and **multiple scam attempts** leveraging threads + fake support tickets.
- Users are primed to be exploited specifically because migration support is closed and they are desperate for help.

**Implementation opportunity**
- Reduce attack vectors: restrict thread creation, add automated warnings, enforce a verified-support pattern.

#### B) Product clarity gaps (medium-high impact; growth limiter)
1) **Token utility disconnect (High impact on investor/user conviction)**
- Community explicitly states: “framework has no direct tie to token → zero reason to buy.”
- Requests surfaced: buybacks via cloud revenue; stronger utility tie; staking after JEJU (timeline unknown).

2) **Non-technical onboarding mismatch (High impact on adoption)**
- Discord feedback indicates non-tech users can register and prompt an agent, but “real use cases require plugins/technical work.”
- Roadmap not accessible to non-coders; missing concrete milestones (e.g., token payments, governance).

3) **Discoverability of ElizaCloud capabilities (Medium impact; quick win)**
- Proposal: base install should system-prompt agents to be aware of ElizaCloud as a solution set (also for Milaidy fork).
- This is a direct UX lever: reduces “I installed it, now what?” and increases cloud feature adoption.

#### C) Operational/product bugs hurting perceived quality (medium impact, but compounding)
- **Duplicate LLM calls when message contains URL** (#6486) → cost blowups + duplicated output (immediate quality/cost hit).
- **Image content stripped in cloud chat** (#6494) → breaks multimodal expectations (high frustration for cloud users).
- **Custom OpenAI endpoint request** (#6490) → blocks OpenAI-compatible providers; hurts developer flexibility.
- Discord user report: agent posting issue (roomId) still unresolved in chat context.

---

### 3) Strategic Prioritization (Impact vs. Risk, Dependencies, Resourcing)

#### Priority 0 — Trust & Safety Containment (execute in 24–48h)
**Why:** Active scams + migration distress is a perfect social-engineering storm.

**Actions**
- **Lock down thread creation** in high-risk channels (coders/support-adjacent); move to mod-approved threads only.
- **Ban reported scammer ID 364718078946312192**; audit recent threads for similar patterns.
- Add a **bot auto-reply** to any message containing “migration / swap / ticket / support”:
  - “Support will never ask you to join another server/Zoom”
  - Link to verified support policy + official URLs
- Create a **single “Verified Support” role + channel-only ticketing** (no DMs, no threads) and pin it everywhere.

**Resource ask:** 1 admin + 1 mod for permissions/audit; 0.5 eng-day if bot changes needed.

---

#### Priority 1 — Migration Fallout Management (7-day plan; comms-heavy, low eng risk)
**Why:** This is the largest sentiment driver and directly impacts retention and reputation.

**Recommended approach (pick one explicitly, then communicate clearly)**
- **Option A (Policy fixed):** “No further migrations” + publish post-mortem + anti-scam guidance + where to verify status.
- **Option B (Limited remediation):** one-time **appeals window** for provable long-term holders (strict rules, on-chain proof, cap, deadlines).  
  *Risk:* operational load + fairness debates; *Benefit:* reputation recovery.

**Non-negotiables**
- Publish a **Migration Closure FAQ** with:
  - deadline, ratio, process recap, why closed, how to avoid scams
  - explicit: “No tickets accepted after Feb 4” (if Option A)
- Add “migration closed” banner in Discord + website docs (where newcomers land).

**Resource ask:** 1 comms owner + 1 legal/ops reviewer.

---

#### Priority 2 — Fix “Cost/Quality” Bugs that Create Visible Failure (next sprint)
**Why:** These create immediate “Eliza feels broken/expensive” moments.

**Top fixes (ranked)**
1) **#6486 URL duplicate LLM calls** — *High user impact, likely moderate complexity*  
   - Expected ROI: reduces token spend + fixes duplicated output (direct quality + cost win).
2) **#6494 image content stripped in cloud chat** — *High impact for cloud UX, moderate complexity*  
   - Protects multimodal credibility; prevents “cloud is worse than local” perception.

**Resource ask:** 1–2 engineers for 2–4 days including tests and release notes.

---

#### Priority 3 — “Golden Path” Onboarding + Cloud Discoverability (high leverage, low-medium risk)
**Why:** Converts interest into retention; aligns with ecosystem growth strategy.

**Implement**
- Base install **system prompt augmentation**:
  - Agents should know: “ElizaCloud can provide storage/DB/deploy/monetize” and suggest it when relevant.
  - Include a lightweight “capabilities discovery” step (only once per session or when user asks “how do I…”).
- Cloud dashboard: add “Recommended safe plugins” set for non-technical users (curated, minimal configuration).
- Publish a **non-coder roadmap view** (milestones + dates/quarters; JEJU/staking dependency stated plainly).

**Dependency mapping**
- **Staking availability depends on JEJU launch**; current lack of timeline fuels repeated questions.  
  -> Provide a *confidence-bounded* estimate (even if ranges) and status updates cadence.

**Resource ask:** 1 product + 1 eng (prompt/template + dashboard copy) + 1 design for roadmap format.

---

#### Priority 4 — Token Utility Narrative → Concrete Utility Surface Area (strategy + sequencing)
**Why:** Community identifies token/framework disconnect as the “biggest hurdle.”

**Near-term (credible, implementable)**
- Tie token to **cloud credits / fees / discounts / paymaster flow** (even if limited pilot).
- If buybacks are planned: publish a **transparent policy spec** (source of revenue, cadence, reporting).

**Medium-term**
- Governance and utility milestones published with explicit deliverables (not aspirational statements).

**Risk:** regulatory/market sensitivity; ensure tight language and compliance review.

---

### Key Recommendations (Actionable Summary)
- **Immediately**: lock down Discord threads + implement anti-scam automation + ban known scammer.
- **This week**: publish migration closure FAQ + choose and announce remediation stance (A or B).
- **Next sprint**: ship fixes for URL double-processing (#6486) and cloud image stripping (#6494).
- **Within 2–3 weeks**: implement base-install “ElizaCloud awareness” prompting + a non-coder onboarding path + roadmap visibility (including JEJU→staking dependency).
- **Quarter planning**: formalize token utility integration points (cloud credits/fees) and publish measurable milestones.