# Council Briefing: 2026-05-01

## 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

- Transitioning from recovery to rebirth through the definitive architecture of ElizaOS v3 as a full application runtime, despite significant financial and community turbulence.

## Key Points for Deliberation

### 1. Topic: v3 Runtime Evolution & Resource Scarcity

**Summary of Topic:** Development has shifted to a 'full application runtime' architecture supported by personal funding from leadership due to token value collapse and equity loss.

#### Deliberation Items (Questions):

**Question 1:** How shall we secure the continuity of v3 development given the current reliance on personal savings and lack of traditional equity?

  **Context:**
  - `Shaw: 'v3 is being funded through personal savings' and 'team received no equity when token values collapsed.'`
  - `Continuous development for 6 months with 'cozy devs' despite financial constraints.`

  **Multiple Choice Answers:**
    a) Accelerate Eliza Cloud monetization to create a sustainable revenue loop.
        *Implication:* Provides non-dilutive funding at the cost of potential friction for early adopters.
    b) Seek external R&D grants or strategic venture partners for Eliza Labs.
        *Implication:* Stabilizes the 'bus factor' but may introduce external governance pressures.
    c) Pivot to a purely decentralized 'contributor-bounty' model for all non-core features.
        *Implication:* Reduces burn rate but risks slowing down the 'Execution Excellence' mandate.
    d) Other / More discussion needed / None of the above.

**Question 2:** Does the 'full application runtime' model align with our 'Developer First' principle or risk over-centralizing the ecosystem?

  **Context:**
  - `Shaw: v3 supports all platforms including iMessage and allows runtime application creation and monetization.`
  - `Example: 'botdick' agent created its own video game autonomously.`

  **Multiple Choice Answers:**
    a) Prioritize seamless UX by bundling the runtime as the primary way to deploy agents.
        *Implication:* Ensures 'Execution Excellence' but may alienate developers preferring modular toolkits.
    b) Maintain v3 as an optional 'Pro' layer while keeping the framework modular.
        *Implication:* Upholds 'Open & Composable' values while providing a premium execution environment.
    c) Open-source the runtime specs immediately to encourage multi-platform parity.
        *Implication:* Drives ecosystem value through 'Developer First' openness but risks fragmentation during v3 launch.
    d) Other / More discussion needed / None of the above.

---


### 2. Topic: Token Philosophy & Infrastructure Utility

**Summary of Topic:** The project is pivoting away from artificial token utility towards culture-building and concrete infrastructure usage via x402.

#### Deliberation Items (Questions):

**Question 1:** Should $ELIZA's implementation as the default payment method in x402 be the primary model for all future framework services?

  **Context:**
  - `Shaw: '$ELIZA (elizaOS token) has been implemented as the default payment method in x402.'`
  - `Rejected traditional forced utility in favor of culture-building.`

  **Multiple Choice Answers:**
    a) Mandate $ELIZA for all core infrastructure services (Cloud/Jeju).
        *Implication:* Strongly ties framework success to token health but creates a barrier to entry for non-crypto users.
    b) Keep $ELIZA as a 'preferred' currency with discounts, allowing fiat/stablecoin alternatives.
        *Implication:* Balances 'Execution Excellence' (low friction) with token coordination.
    c) Focus exclusively on 'Culture-Building' and let the market determine utility without mandates.
        *Implication:* Purely organic growth but risks missing out on capturing infrastructure value.
    d) Other / More discussion needed / None of the above.