# ElizaOS Intel — 2026-02-20

## 1) Data Pattern Recognition (Signals, trends, quantified)

### Development velocity & code health
- **Monthly (2026-02-01 → 2026-03-01, elizaos/eliza):**
  - **32 PRs opened, 18 merged** (≈56% merge rate so far)
  - **38 new issues**, **63 issues closed** (closure > intake; backlog burn-down trend)
  - **30 active contributors**
  - **127 commits**, **160 files touched**, **+18,576 / -3,807 LOC** (net +14,769)
- **Current engineering emphasis (last 72h of community + repo signals):**
  - “Foundational refactor / compatibility” work is dominating near-term focus:
    - Spartan repo: PR opened to address **core-compat layers + service/build issues** (pre-integration hardening).
    - Core: ongoing multi-language + runtime refactors, DB refactor track, bootstrap optimizations.

**Interpretation:** Velocity is healthy, but change surface area remains large (multi-language runtime + DB refactor + plugin upgrades). Risk of “DX breakage” and onboarding friction is high without parallel investment in install paths, Docker, and docs.

### Community engagement patterns
- Discussion volume is being pulled strongly toward **token identity, migration, and credibility questions** rather than product usage.
- “Positive engagement” cluster exists but is secondary:
  - Creative content sharing (artwork) generated lightweight social momentum.
  - “Golden checkmark verification” created a short-lived legitimacy boost.
  - “Babylon / hanging plaza” demo repeatedly referenced as the best live proof of agents-in-the-wild.

### Feature adoption & discovery
- **Most discoverable “product” today is the Babylon Discord demo** (the hanging plaza).
- **elizaos.news** is evolving into a community-facing media surface (mobile support improved; interview feature planned), but it has not yet become the primary support/onboarding funnel.

### Pain point correlation across channels
Recurring issues converging across days:
1. **Token confusion + migration support gaps** (repeated questions; contradictory peer answers; deadline misses)
2. **Onboarding friction for builders** (Spartan setup pain, missing plugins, Docker nonfunctional, “not polished yet”)
3. **Distribution/packaging trust** (milady `npx` installing wrong package; pre-release confusion)
4. **No clear pathway for collaboration/support** (no ticket system; redirect to “build a plugin” doesn’t satisfy non-dev collabs like AMAs)

---

## 2) User Experience Intelligence (Themes, impact, sentiment)

### Feedback themes (categorized by impact)

**High impact (blocking trust / adoption)**
- **Token identity clarity failure mode**
  - Users asked whether **$ai16z / $ai6z** and **$elizaos** are the same; initial community responses were wrong, later corrected by Odilitime (“different contracts; ai16z worth way less”).
  - Repeated requests for **contract address**, plus concerns about **mintability** and **missed migration deadline**.
  - Marketing follow-through questions: “What happened after autofun?” “Where’s ElizaCloud?”
- **Migration support experience**
  - At least two separate user cases surfaced (lost coins during migration; missed deadline) with no clear resolution path beyond “post publicly.”

**Medium impact (builder conversion / developer productivity)**
- **Spartan setup complexity**
  - Missing plugin dependencies requiring manual cloning; bun install hangs; Docker present but **non-functional**.
  - Setup perceived as “not polished,” attributed to ongoing plugin upgrades.
- **Plugin integration ambiguity**
  - “Can I use plugins with milady assistant?” → “Yes if next branch exists” (implies unstable branch dependency; unclear compatibility contract).
- **Collaboration workflow ambiguity**
  - “Where do I open a collab proposal ticket?” → “No ticket system; build a plugin.” This leaves non-plugin collabs (AMAs, partnerships) orphaned.

**Low-to-medium impact (momentum and perception)**
- Rebrand sentiment: “lost memetic value” due to ticker change; contributes to negative price narrative even if not product-related.

### Usage patterns vs intended design
- Community is using Discord as:
  1) **Primary support desk** (token + migration + install)
  2) **Primary product discovery layer** (demo pointers)
  3) **Primary comms channel for roadmap/accountability**
  
This exceeds Discord’s capacity without structured support artifacts (FAQ, ticketing, known-issues, canonical contract info).

### Sentiment tracking (directional)
- **Polarized sentiment**:
  - Negative: frustration on marketing/ElizaCloud, token utility, migration confusion.
  - Positive: technical positioning (benchmarks/connectors/reliability vs OpenClaw), verification milestone, demo pride, creative culture.
- Net sentiment risk is driven less by tech and more by **credibility + clarity gaps**.

---

## 3) Strategic Prioritization (What to do next, why, risk, dependencies)

### Priority stack (next 7–14 days)

#### P0 — Trust & Support Stabilization (highest user impact, low-to-medium technical risk)
1) **Publish a canonical Token & Migration “Single Source of Truth”**
   - Must include: verified **$elizaos contract**, explicit statement **ai16z != elizaos**, migration status (closed/open), and “what if I missed it?”
   - Add **mintability explanation** (or explicit “not mintable / capped” proof + links), since it’s a recurring trust trigger.
   - Success metric: reduce repeated token questions in #discussion by **>50%** within 1 week.

2) **Create a minimal Support Intake path**
   - Even a lightweight form + triage labels (Migration / Wallet / Install / Cloud / Partnerships) will outperform ad-hoc replies.
   - Dependency: designate 1–2 rotating community “first responders” with escalation rules to core team.

#### P1 — Builder Onboarding Reliability (high conversion impact, medium technical risk)
3) **Spartan “golden path” install**
   - Ship: working Docker or explicitly remove/flag it as unsupported; publish required vs optional plugin list; provide a one-command bootstrap script.
   - Tie-in: Spartan PR on core-compat/service-build issues indicates active stabilization—pair code fixes with **DX documentation** immediately.
   - Success metric: new builder time-to-first-run < **30 minutes** (track via a small self-report form).

4) **Packaging/distribution hygiene**
   - Resolve the `npx milady` name collision issue (already tracked as issue #324) and publish clear “pre-release install” guidance.
   - Add a “Known package name collisions / official installs” page to docs.

#### P2 — Narrative & Positioning (medium impact, low technical risk)
5) **Operational comms update: Marketing + ElizaCloud**
   - Provide a short status post: what’s paused, what’s shipping next, and what “done” looks like.
   - Leverage strong differentiators already stated publicly:
     - “Better benchmarks, more connectors, more reliable (not self-configuring) vs OpenClaw.”
   - Success metric: fewer repeated “where is X?” posts; improved sentiment in weekly recap.

### Critical path dependencies / risk flags
- **Large refactors + plugin upgrades** are actively blocking polish (Spartan, Docker, setup). If continued without parallel stabilization, community builder interest will churn.
- **Identity + trust work is emerging organically** (SAID protocol efforts, MoltBridge trust graph discussion, rugpull detection). This is an opportunity, but it must not distract from baseline UX.

---

## Actionable Recommendations (Resource allocation)

### Allocate immediately (this week)
- **1 Maintainer (DX owner, 2–3 days):** Spartan install + Docker truth + required plugins list + quickstart docs.
- **1 Community/Ops owner (0.5–1 day):** Token/migration FAQ, pinned posts, contract address canonicalization, mintability statement, migration finality policy.
- **1 Eng + 1 Comms (1 day):** ElizaCloud + marketing status note (even if minimal), plus a “demo-first onboarding” message that routes newcomers to hanging plaza + docs.

### Instrumentation to add (lightweight)
- Tag Discord questions into 4 buckets weekly: **Token/Migration**, **Install/DX**, **Roadmap/Marketing**, **Build/Integrations**.
- Track: count of unresolved questions per bucket; aim for **<20% unanswered** in P0 buckets.

---

## Key Watch Items (next intel cycle)
- Whether token/migration clarity reduces repeated confusion (watch for re-emergence of “ai16z = elizaos?” questions).
- Whether Spartan compatibility/build fixes land and are matched by a published golden path.
- Whether “trust/security” projects (rugpull detection, identity signing standards) convert into ecosystem integrations without fragmenting focus.
- Whether partnership/collab requests (AMAs, grants, events) get a non-dev intake channel to avoid missed opportunities.