## Episode Overview
- **RETRO-2026-04 — Monthly Retro: April 2026**
  - April showed **strong architectural progress** (parallel action execution, ongoing database refactor, emerging “fail-closed” safety/spend governance and economy primitives) but also a **sentiment low** driven by **token collapse**, **developer onboarding breakages (macOS/Bun postinstall)**, and **perceived strategic drift**. The council aligned that **reliability + DX + security defaults** are now gating adoption more than new capability.

## Key Strategic Themes
- **“Boring reliability” as the growth engine**
  - If `elizaos create`/first-run fails, every other initiative (marketplace, v3, flagship apps) becomes irrelevant in practice.
  - The council treats onboarding failures as **stop-the-line incidents** and pushes for **CI-reproducible install health**.

- **V2 stability vs V3 acceleration (support policy clarity)**
  - Progress on v3 is valid, but without an explicit **v2 LTS patch set** and support window, integrators experience “abandonware risk,” fragmenting the ecosystem.

- **Security + economic autonomy convergence**
  - With agent payments/economic behavior becoming core, **security is no longer a “plugin concern”**; it must ship as **safe defaults** (fail-closed policies, simulation, allowlists).
  - “Spend governance” is positioned as a **reference template** developers can copy, not scattered lore.

- **Narrative coherence and communications cadence**
  - Community mistrust rises when initiatives feel like “side quests.” The council recommends a consistent framing: **flagships are “powered by ElizaOS,” not parallel missions**.
  - **Weekly ship notes** and time-bound, measurable status updates are considered essential trust infrastructure.

- **Contributor incentives as an execution dependency**
  - Paying contributors in a rapidly declining token creates forced sell pressure and retention risk (“death spiral mechanics”); compensation design is treated as a **delivery prerequisite**, not an HR afterthought.

## Important Decisions/Insights
- **Top operating priorities (next month focus)**
  - **Onboarding & DX stabilization first** (macOS/Bun postinstall fixes; one-command create→run path).
  - **V2 LTS patch policy** to protect integrators and reduce ecosystem fragmentation.
  - **Security baseline + spend-governance MVP** as a standardized, safe default path.

- **Explicit deferrals**
  - Broad marketplace expansion is **deprioritized** until the **core developer path is stable** and trust is recovering.

- **Clarity as a product feature**
  - The council emphasizes that ambiguity (about what is official, what is experimental, what is “the main thing”) converts market/token stress into perceived betrayal. The corrective is **measurable, time-bound plans** with verification artifacts (dashboards/badges).

## Community Impact
- **Builders**
  - A stabilized “golden path” (create→run) and CI-backed install health reduces wasted time, lowers support burden, and increases plugin adoption confidence.
  - A v2 LTS scope prevents integrators from stalling while v3 evolves.

- **Ecosystem trust**
  - Shipping safety defaults (fail-closed spend policies) directly improves willingness to deploy autonomous agents with real economic actions.
  - Clear comms cadence and official scope boundaries reduces rumor-driven churn during down-market conditions.

- **Contributors**
  - A compensation policy reset (partial stable payouts/hedging/milestone conversion) is expected to improve retention and keep throughput stable, which is critical to meeting reliability goals.

## Action Items
- **Onboarding/DX**
  - Fix **macOS (Apple Silicon) Bun postinstall/create failures** and make the path **reproducible in CI**.
  - Publish a public-facing **“Install Health” dashboard** (weekly) showing create→run success across OS/runtime matrices.

- **Release governance**
  - Publish and enforce a **v2 LTS support window + patch scope** so integrators know what will be fixed and when.
  - Publish a **one-page v3 roadmap** with explicit exit criteria (tests/perf/migration guide) to reduce “endless refactor” perception.

- **Security baseline**
  - Add **SECURITY.md** + responsible disclosure process.
  - Add CI automation for **dependency scanning/SBOM** and ship at least one **fail-closed spend policy preset** (off-by-exception).

- **Spend governance reference implementation**
  - Deliver a **reference agent template** with:
    - allowlisted actions,
    - transaction simulation,
    - risk checks (e.g., honeypot/rug heuristics),
    - documented extension points.

- **Compensation + comms**
  - Announce a **compensation policy update** (time-boxed, with a clear effective date).
  - Commit to a **weekly ship-note + monthly retro cadence**, including “what broke / what’s fixed / how to verify.”