# Intel — 2026-03-01 (ElizaOS)

## 1) Data Pattern Recognition

### Development velocity & stability signals (proxy via community reports)
- **Breaking-change pressure remains high**: multiple users report “almost every release contains a breaking change” (v2.0.0 described as “very much alpha”).
- **Plugin reliability regression indicators**:
  - Reported **broken OOTB on 1.7.2**: `plugin-linear`, `plugin-rolodex`, `plugin-memory` (requires manual patching).
  - Reported **known blocker in v2.0.0**: **bcrypt issue** requiring patches.
- **Autonomy surface area is fragmented** (3 separate implementations discussed):
  1) `plugin-autonomous` (periodic thinking)
  2) v2.0.0 built-in autonomy (Shaw)
  3) `milaidy` (OpenClaw-like autonomy)

**Trend implication:** feature velocity is creating a widening “operational gap” where users can’t confidently choose versions/plugins for production, increasing support load and slowing adoption.

### Community engagement patterns
- **High-value project shared, low discovery/attention**: ZeitGaist VPS orchestration + Conway plugin shared publicly; author explicitly cites **limited visibility**.
- **Support bottleneck pattern**: multiple questions remain unanswered due to missing “minimum repro context” (e.g., Twitter input issue requires version/product clarification).
- **External PRs increasing again** (positive health indicator), but concerns about **scope creep** (plugins reintroduced to core referenced via PR #6531).

### Quantitative snapshot (from aggregated Discord digests, 2026-02-26 → 2026-02-28)
- **Channels analyzed:** 3 (on 02-26 snapshot)
- **Active technical discussion threads (reported):** 5 (02-26)
- **Help interactions:** 3 (02-26) + additional guided Q&A on 02-27/02-28
- **Unanswered question clusters observed:**  
  - 02-26: 3 unanswered  
  - 02-28: 3 unanswered (versioning, cron-like autonomy, plugin viability)  
  - Plus unresolved compliance question (FCRA safeguards) on 02-27

## 2) User Experience Intelligence

### Feedback themes (categorized by impact)

#### A. “Production readiness” confusion (High impact, High frequency)
**Signals**
- Users unsure whether to use **`v2-develop` vs `alpha`** for production.
- Users experiencing **OOTB plugin breakage** on stable-ish versions (1.7.2).
- Users asking whether certain plugins are actually **tested/viable** (`plugin-orchestrator`, `plugin-code`).

**UX gap**
- Missing a **single source of truth** for: “If you want X use-case, use Y branch + Z plugin versions.”

**Opportunity**
- Publish a **supported matrix**: (runtime version) × (plugin versions) × (capabilities) with “known good” combos.

#### B. Autonomy expectations vs intended design (High impact, Medium frequency)
**Signals**
- Users want **cron-like autonomous behavior** and don’t know whether to implement via plugin, built-in, tasks system, or custom code.
- 1.x tasks system exists but **not chat-accessible**, creating a mismatch between “agent” mental model and actual configuration surfaces.

**Opportunity**
- Provide an **official autonomy cookbook** with 3 canonical patterns:
  1) polling cron (safe + predictable)
  2) event-driven triggers (webhooks)
  3) periodic reflection (agent “thinking” loops) with guardrails

#### C. Compliance & “real-world automation” risk (High impact, Low/Medium frequency)
**Signals**
- Credit-building plugin includes **certified mail** automation; community raised **FCRA compliance safeguards** questions (unanswered).
- Interest in expanding into other regulated dispute domains (tickets/citations).

**Opportunity**
- Establish “regulated automation” guidelines + optional compliance scaffolding (human-in-the-loop, audit logs, templates, disclaimers).

#### D. Onboarding & troubleshooting friction (Medium impact, Medium frequency)
**Signals**
- Beginner asks “how to build an agent”; response is “install + read docs + ask in help channel” (works, but indicates onboarding still doc-heavy).
- Twitter input issue stalled due to missing “version/product” intake.

**Opportunity**
- Add **support intake template** + “first agent in 15 minutes” path that culminates in a reproducible minimal agent project.

### Sentiment
- Mixed but constructive:
  - Positive: excitement about novel infra (ZeitGaist), compliance/real-world use cases, external PRs increasing.
  - Negative: frustration about project visibility and plugins breaking “out of the box,” plus confusion around alpha vs develop.

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

### Priority 0: Reduce ecosystem breakage via “Known-Good” release lanes (Very high impact, Medium risk)
**Why now**
- Reported plugin breakage on 1.7.2 and patch-requiring issues on v2.0.0 are direct adoption blockers.

**Deliverables**
1) **Version/Plugin Compatibility Matrix** (docs + CI-generated table)
2) **Two lanes**:
   - **Stable lane**: pinned runtime + pinned plugin set, only critical fixes
   - **Edge lane**: v2.0.0 alpha + fast iteration
3) **“OOTB smoke tests”** for top plugins (Linear, Memory, GitHub, Google*) against stable lane.

**Dependencies**
- CI investment + plugin maintainers aligning on pinned versions.

### Priority 1: Autonomy unification via a single “Scheduling & Autonomy” interface (High impact, Higher technical risk)
**Problem**
- Three autonomy implementations + hidden 1.x tasks system = confusion and duplicated effort.

**Recommendation**
- Define an **Autonomy API contract** (schedulers, triggers, task registry, guardrails) that multiple backends can satisfy:
  - cron/polling backend
  - event/webhook backend
  - “periodic thinking” backend

**Minimum viable path (2-step)**
1) Documented “official” approach for cron-like behavior *today* (choose one blessed method per lane).
2) Build a thin abstraction later, once adoption patterns are clear.

### Priority 2: Plugin viability labeling + deprecation policy (High impact, Low/Medium risk)
**Problem**
- Users asking if `plugin-orchestrator` and `plugin-code` are tested indicates missing trust signals.

**Recommendation**
- Add a **plugin registry badge system**:
  - Maintained / Experimental / Unmaintained
  - Tested on Stable lane (yes/no) + last CI pass date
  - Security-sensitive flags (e.g., code execution, financial actions)

### Priority 3: Project discovery & community showcase pipeline (Medium impact, Low risk)
**Problem**
- High-value community projects (ZeitGaist, Conway plugin) struggle for visibility, reducing contributor retention.

**Recommendation**
- Create a weekly “**Builds of the Week**” spotlight:
  - short template submission
  - pinned Discord thread + website/news mirror
  - “integration opportunities” tag (e.g., infra, compliance, autonomy)

### Priority 4: Regulated automation safety framework (Medium/High impact, Medium risk)
**Problem**
- Compliance questions are currently unanswered, creating reputational/real-world risk.

**Recommendation**
- Publish baseline guidance:
  - mandatory audit logging recommendations
  - human confirmation checkpoints
  - data handling & dispute safety checklist
  - disclaimers + jurisdiction notes
- Encourage plugins in regulated areas to include a **“compliance mode”** toggle (more confirmations, more logging, restricted claims).

---

## Actionable Recommendations (Next 7–14 days)

1) **Ship a one-page “Which version should I use?” decision tree**
   - Explicitly state: when to pick `v2-develop` vs v2.0.0 alpha
   - Include known issues: bcrypt patch status, plugin breakage notes

2) **Stand up OOTB smoke tests for top 5 workflow plugins**
   - Target: `plugin-linear`, `plugin-memory`, `plugin-github`, `plugin-google-meet-cute`, `plugin-google-chat`
   - Output: pass/fail badge on the compatibility matrix

3) **Answer and close the open autonomy question with a blessed pattern**
   - Provide a canonical “cron-like monitoring” example (e.g., blocked Linear issue polling + escalation)
   - Clarify when to use `plugin-autonomous` vs built-in autonomy vs tasks system

4) **Implement a “support intake minimums” bot/template**
   - Require: runtime version, channel/branch, plugin list + versions, logs snippet
   - Goal: reduce stalled issues like Twitter input debugging

5) **Launch project spotlight process for ZeitGaist/Conway**
   - Convert into: (a) short demo clip + (b) “how to try in 10 minutes” + (c) integration asks
   - Outcome: improve contributor retention and perceived ecosystem momentum

---

## Key Risks to Track
- **Adoption stall** if “alpha vs develop” ambiguity persists and plugins continue to break OOTB.
- **Autonomy fragmentation** leading to incompatible patterns and increased maintainer burden.
- **Compliance/reputation risk** if regulated automation plugins scale without safety guidance.
- **Core scope creep** (plugins re-entering core) increasing maintenance complexity; needs governance clarity (referenced via PR #6531 concern).