# Council Briefing: 2026-04-28

## Monthly Goal

December 2025: Execution excellence—complete token migration with high success rate, launch ElizaOS Cloud, stabilize flagship agents, and build developer trust through reliability and clear documentation.

## Daily Focus

- The project is undergoing a massive dependency modernization alongside a pivot to monetization infrastructure in Eliza Cloud, while facing community pressure regarding token market cap.

## Key Points for Deliberation

### 1. Topic: Framework Modernization & Dependency Risk

**Summary of Topic:** Massive version bumps across Node.js 24 and TypeScript 6 are being initiated to keep the framework cutting-edge, despite potential breaking changes.

#### Deliberation Items (Questions):

**Question 1:** How should the Council weigh the risk of breaking current agent implementations against the necessity of technical modernization?

  **Context:**
  - `lalalune initiated Renovate updates targeting Node.js 24 and TypeScript 6 across core repositories.`
  - `Team is currently awaiting CI results to verify if major version bumps break infrastructure.`

  **Multiple Choice Answers:**
    a) Prioritize stability by delaying major bumps until after Eliza Cloud launch.
        *Implication:* Reduces short-term risk but increases technical debt and slows down developer adoption of new features.
    b) Proceed with modernization but require a long-term support (LTS) branch for v1.x builders.
        *Implication:* Maintains community trust while allowing the core team to iterate on v2/v3 frameworks.
    c) Aggressive rollout of Node 24/TS 6 to reinforce the 'Execution Excellence' principle.
        *Implication:* Forces builders to upgrade, ensuring the ecosystem stays on the most secure and performant stack.
    d) Other / More discussion needed / None of the above.

---


### 2. Topic: Token Utility vs. UX Friction

**Summary of Topic:** Recent strategy discussions favor revenue-driven buybacks over forced token utility to minimize barrier to entry for the Cloud platform.

#### Deliberation Items (Questions):

**Question 1:** Is the 'Buyback via Revenue' model sufficient to pacify community concerns regarding token market performance?

  **Context:**
  - `shawmakesmagic: Preferred approach is to accept any payment and use revenue to buy back tokens to avoid user friction.`
  - `Community members expressed concern over the token dropping below $5M market cap.`

  **Multiple Choice Answers:**
    a) Adopt a hybrid model: discount for paying in native tokens, buybacks for fiat/stable users.
        *Implication:* Increases native token demand without technically excluding non-crypto users.
    b) Stay the course with buybacks to keep developer onboarding as seamless as possible.
        *Implication:* Focuses on growth and framework adoption as the primary long-term value driver for the token.
    c) Pivot to a 'Token-Gated' advanced feature model for Cloud to create immediate utility.
        *Implication:* May increase token price in the short term but likely throttles Cloud platform growth.
    d) Other / More discussion needed / None of the above.

---


### 3. Topic: Maintenance Ownership & Contributor Concentration

**Summary of Topic:** Operational logs reveal high concentration of core system maintenance among two primary contributors, creating a potential 'bus factor' risk.

#### Deliberation Items (Questions):

**Question 1:** Should the Council implement a formal 'Eliza Army' steering group to decentralize maintenance of the core framework?

  **Context:**
  - `lalalune and odilitime maintain high ownership over framework updates and CI/CD logic.`
  - `odilitime mentioned forming an 'eliza army' steering group for community coordination.`

  **Multiple Choice Answers:**
    a) Formalize the 'Eliza Army' with specific sub-bounties for maintaining legacy modules.
        *Implication:* Frees up core devs to focus on V3 and Eliza Cloud while increasing decentralized resilience.
    b) Restrict core repo access to current leads to preserve 'Execution Excellence' and UX reliability.
        *Implication:* Ensures quality control but maintains a high 'bus factor' and potential burnout for leads.
    c) Transition to a 'Reviewer-Only' model where community members must earn maintainer status through PR audits.
        *Implication:* Slowly expands the contributor pool while ensuring high standards are met through tiered access.
    d) Other / More discussion needed / None of the above.