## Intel — 2026-05-04

### Executive Signals (last 72h)
- **Product narrative vs market narrative misalignment** is the dominant community risk: token-price drawdown + “promises” (e.g., Babylon airdrop) are pulling attention away from near-term shippables (V3, Cloud, Milady app).
- **Engineering throughput is high and skewed toward stabilization + platform hardening**, with major UX-facing automation improvements landing (n8n clarification loop), but a few **P1-quality gaps** remain that could surface as “it doesn’t work” during V3/Milady ramp.
- **Comms + usability friction** is now a measurable productivity tax (spam filter blocking URLs; repeated clarifications on buybacks/revenue).

---

## 1) Data Pattern Recognition

### Development velocity & trend
- **Monthly (May-to-date, elizaos/eliza)**: **111 PRs opened / 59 merged**, **9 new issues / 12 closed**, **12 active contributors**.
- **Change shape**: high-volume consolidation and infra work is increasing (e.g., PR #7235: cloud+plugins added; rust/python removed; very large diff). This signals **platform convergence** but also raises **regression risk** and review load.
- **Focus mix (observed May 3 engineering narrative)**:
  - Runtime/infrastructure stability fixes (headless Linux segfault, Telegram polling race/message loss, CI/workflows cleanup)
  - Auth/client consolidation (MiladyClient → canonical ElizaClient; SIWE domain fix; Codex CLI token recognition)

### Community engagement patterns
- Discussion intensity clustered around:
  - **Token economics + expectations** (buybacks, price decline, “investor vs holder” framing)
  - **Roadmap clarity** (visual roadmap pushed; GitHub roadmap text update planned)
  - **“Builder” energy**: external dev building a spot trading agent targeting **SOL, SUI + 5 tokens**, aiming for **1–2 signals/week** (early adoption signal for trading agent tooling)

### Feature adoption / pull signals (proxy)
- Automation UX investment is landing in core:
  - n8n: clarification roundtrip routes + Discord context catalog surfaced (indicates intent to drive **NL→workflow** adoption)
- Trading stack surfaced repeatedly:
  - Repos highlighted: **plugin-auto-trader**, **plugin-social-alpha**, **spartan**
  - “Social alpha” explicitly oriented to **trenches channel profitability evaluation → copy trading**

### Pain point correlation across channels
- **Communication clarity deficits** (roadmap, Babylon airdrop status, buyback logic) correlate with **negative sentiment and churn threats**.
- **Operational friction (spam filter URL blocks)** correlates with reduced technical support bandwidth (helpers forced into workaround explanations; slows coordination).

---

## 2) User Experience Intelligence

### Feedback themes (categorized by impact)

**P0 / High impact (blocks usage or trust)**
- **Roadmap ambiguity → trust degradation**: repeated questions on buybacks, revenue timeline, unfulfilled “Babylon airdrop”.
- **Spam filter blocking URLs**: prevents users/helpers from sharing references; workaround (“wrap in backticks”) is non-obvious and brittle.

**P1 / Medium-high impact (likely to surface during onboarding/launch)**
- **Automation clarification loop quality risks** (per merge notes / review signals): any mismatch between generated `paramPath` formats and real n8n draft shapes can cause 400s or “needs clarification” loops—this is a launch-day paper cut with outsized UX cost.

**P2 / Strategic UX opportunity**
- **Long-lived agent reliability (memory rot)**: clear evidence that retrieval-only memory systems drift after ~3 months; reconciliation passes (freshness gates + diffs + re-embedding) are a differentiator if turned into a first-class product capability.

### Usage patterns vs intended design
- Intended: “community of builders”; Actual: a large segment behaves like **short-horizon token speculators**, demanding immediate token-mechanism actions.
- Intended: rapid technical collaboration in Discord; Actual: **platform moderation tooling (spam filter)** is degrading collaboration efficiency.

### Sentiment snapshot
- **Polarized**: frustration and accusation cycles in public channels; improved sentiment when:
  - roadmap artifacts are shared,
  - near-term product readiness is mentioned (Milady “nearly ready”),
  - concrete repos and shipping plans are provided.

---

## 3) Strategic Prioritization (Impact × Risk × Dependencies)

### Critical path (next 1–2 weeks, aligned to V3/Milady/Cloud push)

1) **Roadmap + launch comms systemization (High impact, Low tech risk)**
   - Dependency: finalized sequencing for **V3**, **Eliza Cloud**, **Milady app**.
   - Deliverables:
     - Announcements-channel doc set (single canonical source)
     - GitHub roadmap text parity with the visual roadmap
     - Public FAQ: buybacks=revenue gating; what “token holder” means; explicit status of Babylon airdrop (even if “not happening”)

2) **Automation UX hardening for n8n clarification roundtrip (High impact, Medium tech risk)**
   - Why: this is a “wow” feature when it works; a “broken product” signal when it loops/errors.
   - Required:
     - End-to-end contract test: **/generate output → /resolve input** using identical `draft + paramPath` formats
     - Guardrails: reject/repair empty `paramPath`; normalize bracket-string vs array-index paths

3) **Collaboration friction removal: URL sharing + safe allowlisting (Medium impact, Low tech risk)**
   - Implement one of:
     - channel-scoped relaxed filters for trusted roles
     - auto-unfurl disabled but allowlist common domains (github, docs, fixupx, elizaos.news)
     - bot response when blocked: “wrap in backticks” + reason + appeal path

### “Next” priorities (2–6 weeks)

4) **Package the “memory rot reconciliation” into a productizable module (High strategic impact, Medium tech risk)**
   - Convert research/production pattern into:
     - a documented memory lifecycle policy,
     - scheduled reconciliation job,
     - freshness-scored claims middleware
   - This can become an ElizaOS differentiator for enterprise/long-lived agents.

5) **Trading ecosystem enablement (Medium impact, Medium risk)**
   - Support the community’s trading-agent build by:
     - minimal “blessed” reference agent template
     - data contracts for social-alpha signals
     - safety + backtesting scaffolding to reduce support burden and reputational risk

### Resource allocation recommendation (pragmatic)
- **40% Launch Readiness & Comms**: roadmap docs, V3 PR/marketing plan, FAQ, announcements hygiene.
- **40% UX Reliability**: n8n clarification hardening + onboarding “first successful workflow” path; spam-filter fixes.
- **20% Strategic R&D**: memory reconciliation module spec + prototype integration plan.

---

## Quantitative KPI Targets (next report cycle)
- **Roadmap clarity**: reduce repeated buyback/airdrop questions in discussion by **50%** (proxy: count of repeated Qs/day).
- **Automation success rate**: achieve **>90%** “generate → deploy” completion without manual debugging (measured via route outcomes: `needs_clarification` loops ≤1 iteration median).
- **Support friction**: reduce “URL blocked” incidents to **near-zero** via allowlisting or role-based relaxation.

---

## Actionable Recommendations (owner-ready)

1) **Publish a canonical “Token Economics & Expectations” page** (Owner: Community Ops)
   - Includes: revenue-first rationale, buyback prerequisites, explicit airdrop status, what gets announced where, and expected cadence.

2) **Ship a “V3 Launch Packet”** (Owner: Shaw + Community PR lead)
   - 1-pager: What is V3, what changes for builders, migration notes, Cloud/Milady tie-in, partner/whitelabel narrative.

3) **n8n clarification reliability sprint** (Owner: App-core engineering)
   - Add one integration test that replays real payloads.
   - Normalize `paramPath` formats and add pruning rules for legacy empty paths.
   - Add UI fallback: allow free-text resolution even when target catalog is missing.

4) **Discord spam filter product fix** (Owner: Moderation tooling)
   - Implement allowlist + structured bot hinting.
   - Document the workaround temporarily in a pinned “How to share links” message.

5) **Convert memory-rot reconciliation into an RFC + plugin** (Owner: Runtime/memory)
   - RFC with acceptance criteria: drift detection, freshness gates, periodic diffs, re-embedding triggers, observability metrics (staleness rate, contradiction rate).