Council Briefing

Strategic Deliberation
▶North Star & Strategic Context

North Star & Strategic Context



This file combines the overall project mission (North Star) and summaries of key strategic documents for use in AI prompts, particularly for the AI Agent Council context generation.

Last Updated: December 2025

---

North Star: To build the most reliable, developer-friendly open-source AI agent framework and cloud platform—enabling builders worldwide to deploy autonomous agents that work seamlessly across chains and platforms. We create infrastructure where agents and humans collaborate, forming the foundation for a decentralized AI economy that accelerates the path toward beneficial AGI.

---

Core Principles: 1. **Execution Excellence** - Reliability and seamless UX over feature quantity 2. **Developer First** - Great DX attracts builders; builders create ecosystem value 3. **Open & Composable** - Multi-agent systems that interoperate across platforms 4. **Trust Through Shipping** - Build community confidence through consistent delivery

---

Current Product Focus (Dec 2025):
  • **ElizaOS Framework** (v1.6.x) - The core TypeScript toolkit for building persistent, interoperable agents
  • **ElizaOS Cloud** - Managed deployment platform with integrated storage and cross-chain capabilities
  • **Flagship Agents** - Reference implementations (Eli5, Otaku) demonstrating platform capabilities
  • **Cross-Chain Infrastructure** - Native support for multi-chain agent operations via Jeju/x402


    • ---

    ElizaOS Mission Summary: ElizaOS is an open-source "operating system for AI agents" aimed at decentralizing AI development. Built on three pillars: 1) The Eliza Framework (TypeScript toolkit for persistent agents), 2) AI-Enhanced Governance (building toward autonomous DAOs), and 3) Eliza Labs (R&D driving cloud, cross-chain, and multi-agent capabilities). The native token coordinates the ecosystem. The vision is an intelligent internet built on open protocols and collaboration.

    ---

    Taming Information Summary: Addresses the challenge of information scattered across platforms (Discord, GitHub, X). Uses AI agents as "bridges" to collect, wrangle (summarize/tag), and distribute information in various formats (JSON, MD, RSS, dashboards, council episodes). Treats documentation as a first-class citizen to empower AI assistants and streamline community operations.
    ▶Daily Strategic Focus
    Transitioning from recovery to rebirth through the definitive architecture of ElizaOS v3 as a full application runtime, despite significant financial and community turbulence.
    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.

    Key Deliberations

    v3 Runtime Evolution & Resource Scarcity
    Development has shifted to a 'full application runtime' architecture supported by personal funding from leadership due to token value collapse and equity loss.
    Q1
    How shall we secure the continuity of v3 development given the current reliance on personal savings and lack of traditional equity?
    • 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.
    1Accelerate Eliza Cloud monetization to create a sustainable revenue loop.
    Provides non-dilutive funding at the cost of potential friction for early adopters.
    2Seek external R&D grants or strategic venture partners for Eliza Labs.
    Stabilizes the 'bus factor' but may introduce external governance pressures.
    3Pivot to a purely decentralized 'contributor-bounty' model for all non-core features.
    Reduces burn rate but risks slowing down the 'Execution Excellence' mandate.
    4Other / More discussion needed / None of the above.
    Q2
    Does the 'full application runtime' model align with our 'Developer First' principle or risk over-centralizing the ecosystem?
    • Shaw: v3 supports all platforms including iMessage and allows runtime application creation and monetization.
    • Example: 'botdick' agent created its own video game autonomously.
    1Prioritize seamless UX by bundling the runtime as the primary way to deploy agents.
    Ensures 'Execution Excellence' but may alienate developers preferring modular toolkits.
    2Maintain v3 as an optional 'Pro' layer while keeping the framework modular.
    Upholds 'Open & Composable' values while providing a premium execution environment.
    3Open-source the runtime specs immediately to encourage multi-platform parity.
    Drives ecosystem value through 'Developer First' openness but risks fragmentation during v3 launch.
    4Other / More discussion needed / None of the above.
    Token Philosophy & Infrastructure Utility
    The project is pivoting away from artificial token utility towards culture-building and concrete infrastructure usage via x402.
    Q3
    Should $ELIZA's implementation as the default payment method in x402 be the primary model for all future framework services?
    • Shaw: '$ELIZA (elizaOS token) has been implemented as the default payment method in x402.'
    • Rejected traditional forced utility in favor of culture-building.
    1Mandate $ELIZA for all core infrastructure services (Cloud/Jeju).
    Strongly ties framework success to token health but creates a barrier to entry for non-crypto users.
    2Keep $ELIZA as a 'preferred' currency with discounts, allowing fiat/stablecoin alternatives.
    Balances 'Execution Excellence' (low friction) with token coordination.
    3Focus exclusively on 'Culture-Building' and let the market determine utility without mandates.
    Purely organic growth but risks missing out on capturing infrastructure value.
    4Other / More discussion needed / None of the above.