# ElizaOS Intel — 2026-03-18

## 1) Data Pattern Recognition (last 72h signal)

### Activity & velocity indicators
- **Active Discord surfaces:** 3 channels with meaningful signal (`#discussion`, `#coders`, `#xfn-framework`).
- **New integration demand:** 1 concrete inbound integration (unbrowse) + 2 platform-level integration proposals (Effect AI human-in-loop marketplace; Z1N identity persistence) surfaced in 48h.
- **Plugin ecosystem momentum:** explicit work in-flight to add **“100+ onchain data support”** via `goldrush.dev` into `plugin-evm` (community contributor: dinesh).
- **Core architecture decision pending:** v2.0.0 skills governance (PR #6597) + question of **shipping with 0 default skills** to avoid 0.x bloat.

### Engagement & sentiment patterns
- **Token/strategy discourse dominates** `#discussion` with **repeated questions and frustration**; high risk of compounding negativity due to unanswered specifics (see below).
- **Positive engagement** clusters around:
  - Jin’s weekly roundup trailer (content performs well; lightweight community morale boost).
  - “unbrowse” (novel capability; builders asking “how do I plug this in?” indicates real adoption intent).

### Pain-point correlation across channels
- **Onboarding friction → community ops load:** Google Form role assignment failure (“Invalid Dynamic Link”) in `#coders` correlates with user requests for **ticket/admin access** in `#discussion`. This is a classic “broken onboarding → support escalation → sentiment drag” loop.
- **Registry/discovery fragmentation:** simultaneous push for (a) decentralized external skills hosting (v2 proposal) and (b) centralized Clawhub-like directory suggests users want **discoverability + curation**, not necessarily “skills in core.”

---

## 2) User Experience Intelligence

### Feedback themes (categorized by impact)

**A. Critical (blocks trust / conversion)**
1) **Tokenomics & migration transparency gaps (trust risk)**
   - Open questions from community: migration %, post-migration supply breakdown, plans for unmigrated allocation, handling collected ai16z supply.
   - Observed: repeated skepticism and “marketing/commitment” accusations amplify when specifics aren’t answered.

2) **Onboarding access failure (operational blocker)**
   - Google Form role assignment broken with “Invalid Dynamic Link” errors.
   - Downstream: users asking for an admin/ticket channel; friction harms newcomer activation.

**B. High (near-term adoption & ecosystem growth)**
3) **Chain/support ambiguity (Milady SOL vs BSC)**
   - Same question asked multiple times, unanswered.
   - Effect: creates perceived disorganization, increases rumor spread, and undermines the “flywheel” narrative.

4) **Component discovery & governance**
   - Proposal: Clawhub-style directory that unifies **skills + plugins**.
   - v2.0.0 discussion: avoid uncontrolled submissions by shipping 0 skills + external hosting via `yourdomains.com/skills.md`.
   - User intent signal: builders want a canonical “where do I find/ship capabilities?” entry point.

**C. Medium (builder experience improvements)**
5) **Integration pathways clarity**
   - unbrowse asked “where do I integrate?” and got pointed to plugin registry + docs.
   - Opportunity: turn this into a repeatable “integration fast lane” playbook.

### Usage patterns vs intended design
- Intended: plugins/registry as distribution mechanism.
- Actual: community still expects “official” answers in chat for:
  - what’s supported (chains, products)
  - where to contribute (skills vs plugins)
  - how to get access (roles/admin)
- Gap: system-of-record docs and pinned answers are not absorbing repeated questions.

### Sentiment snapshot (qualitative)
- **Negative / anxious:** token performance + unclear comms (dominant in `#discussion`).
- **Constructive / builder-positive:** unbrowse integration, directory idea, plugin-evm contributions.
- **Neutral-positive:** community content (weekly trailer).

---

## 3) Strategic Prioritization (impact vs risk, and what to do next)

### Priority matrix (initiatives surfaced)
| Initiative | User Impact | Technical Risk | Key Dependency | Recommendation |
|---|---:|---:|---|---|
| Publish **token migration transparency** (numbers + plan) | Very High | Low | Access to on-chain + treasury data | **Do immediately (24–48h)**; stops rumor loop |
| Fix **role assignment Dynamic Link** | High | Low–Med | Whoever owns Firebase/Dynamic Links + form | **Do immediately (same day)**; unblocks onboarding |
| Clarify **Milady chain support (SOL vs BSC)** | High | Low | Owner decision + single canonical post | **Do immediately**; reduce repeated churn |
| Launch **elizacloud** (promised end-of-week/early next week) | Very High | Med–High | Product readiness + onboarding + docs | **Protect critical path**; align comms and rollout |
| v2.0.0 **skills governance** (ship 0 skills + external index) | Med–High | Med | PR #6597 merge + discovery UX | Decide this week; avoid “bloat vs discoverability” stall |
| Clawhub-style **directory/registry UX** | High | Med | Data model + moderation/curation policy | Start with MVP (read-only index + tagging) |
| unbrowse plugin integration | Med | Med | Plugin scaffolding + example agent | Treat as “hero plugin” to validate registry workflow |
| Effect AI human-in-loop integration | Med–High | Med | API maturity + task security model | Collect use cases; prototype behind flag |
| Z1N identity persistence integration | Medium | Med–High | Identity model alignment (SAID, etc.) | Park until v2 architecture clearer |

### Recommended resource allocation (next 7 days)
**1) Comms/Trust (1 owner + reviewer)**
- Deliverables:
  - Token migration transparency post (FAQ + dashboard link if available).
  - Milady support clarification (single pinned message + docs update).
  - elizacloud launch status updates with dates and scope (avoid vague “soon”).

**2) DevOps/Community Ops (0.5–1 engineer)**
- Fix Dynamic Links / role form end-to-end.
- Add fallback/manual role assignment path and a visible “contact admin” workflow (even a simple ticket channel).

**3) DevEx (1 engineer + 1 tech writer part-time)**
- “Integration fast lane” kit:
  - plugin template repo link
  - checklist for registry submission
  - one reference implementation (candidate: unbrowse)

**4) Platform Architecture (core maintainer bandwidth)**
- Close the v2.0.0 skills question with a decision memo:
  - if “0 default skills,” define the official discovery surface (directory MVP) so the UX doesn’t degrade.

---

## Actionable Recommendations (concrete next steps)

### A) Stop the highest-cost churn (24–48h)
1) **Token migration transparency package**
   - Publish: migration rate estimate (with method), current supply breakdown, explicit plan for unmigrated allocation, and what happens to collected ai16z supply.
   - Format: one Discord post + docs page + pinned FAQ.

2) **Milady chain support**
   - Decide + announce: supported chain(s), official contract(s), and how this ties to elizacloud distribution.
   - Add: “single source of truth” link for future replies.

3) **Role assignment fix**
   - Validate Dynamic Links domain + URL encoding/path rules; add monitoring for link failures.
   - Provide a temporary alternate onboarding route (manual role request, or a simple bot command).

### B) Convert builder interest into shipped ecosystem value (3–7 days)
4) **unbrowse as a flagship plugin**
   - Goal: ship a minimal plugin that demonstrates registry packaging + docs.
   - Add a short demo agent flow: “API-first browsing / fast retrieval” use case.

5) **Directory MVP (Clawhub-like) aligned with v2 skills governance**
   - MVP scope: searchable index of plugins + skills pointers, tags, “verified” badge, submission guidelines.
   - This resolves the tension between “keep core clean” and “users need discoverability.”

### C) De-risk elizacloud launch (this week)
6) **Launch readiness checklist (internal)**
   - Ensure: onboarding works, docs/pins answer top repeated questions, and a minimal “what is elizacloud / how it benefits ELIZA” explainer is available.
   - Avoid launching into broken onboarding + unresolved token FAQs (amplifies negative narrative).

---

## Key Watch Items (signals to monitor tomorrow)
- Repetition rate of unanswered questions (Milady chain, token migration, admin/tickets). If repeats continue, expect sentiment deterioration.
- Whether elizacloud launch dates slip again without specifics (credibility hit).
- Builder follow-through: unbrowse PRs/submission activity and plugin-evm progress (indicates ecosystem health despite market noise).