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
    The council faces a critical synchronization of architectural breakthroughs in Eliza 2.0 with a pivot toward Cloud stability to restore token utility and index-level market capitalization.
    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

    Strategic Resource Redirection
    The core team has officially deprioritized v2.0.0 branch work to focus exclusively on ElizaOS Cloud reliability and feature parity. This move addresses immediate community concerns regarding token utility and market performance.
    Q1
    How should the Council balance the long-term architectural benefits of v2.0 with current pressure for 'Cloud-first' execution?
    • Borko provided clear direction to concentrate all development effort on cloud infrastructure rather than v2.0.0 branch. (2026-01-13)
    • DorianD noted that falling out of the top 100 cryptocurrencies blocks automated investment flows. (2026-01-14)
    1Hard pivot to Cloud-only development until reaching billion-dollar market status.
    Ensures budget sustainability and restores automated investor confidence at the cost of framework innovation.
    2Maintain a skeleton crew on v2.0 core while the majority focus on Cloud stability.
    Protects future architectural superiority while addressing immediate reliability metrics.
    3Open-source the Cloud platform to outsource improvements to the community.
    Leverages ecosystem value (Developer First) but requires significant oversight to maintain 'Execution Excellence'.
    4Other / More discussion needed / None of the above.
    Eliza 2.0 Architectural Paradigm
    Shaw has successfully integrated the planning plugin and extended memory into Eliza core, dramatically reducing boilerplate. However, this has triggered concerns regarding database optimization and LLM call efficiency.
    Q2
    Should we optimize for performance through Rust serverless runtimes or persist with Bun for execution excellence?
    • Shaw clarified that Bun already provides Rust-level performance and that overhead is minimal compared to API latency. (2026-01-12)
    • 0xbbjoker raised concerns about reducing LLM calls by making action params optional. (2026-01-14)
    1Standardize on Bun and focus on minimizing LLM call frequency.
    Prioritizes cost-efficiency and runtime stability over absolute processing speed.
    2Adopt a hybrid approach using Rust specifically for compute-heavy serverless functions.
    Improves 'Open & Composable' flexibility but adds complexity to the developer experience.
    3Submit PRs to core runtimes (e.g., Cloudflare workerd) to bake Eliza requirements into infrastructure.
    Elevates ElizaOS to a foundational internet protocol but requires high-level diplomatic and engineering effort.
    4Other / More discussion needed / None of the above.
    Q3
    Given the 'Bus Factor' risk (lalalune handling 52% of runtime PRs), should we mandate broader review sub-councils?
    • Shaw/lalalune provided detailed explanation of flag-based system; high review dependency on odilitime noted. (Contributor Intel)
    1Implement a mandatory three-party peer review for all Core/Runtime changes.
    Dramatically reduces ownership concentration risk but slows the monthly directive of 'shipping trust'.
    2Initiate a Contributor Growth program specifically for Runtime maintenance.
    Expands ecosystem value (Developer First) without throttling senior leadership output.
    3Maintain the current speed-priority model until Cloud infrastructure is stabilized.
    Accepts high concentration risk to hit immediate monthly directives under current staffing levels.
    4Other / More discussion needed / None of the above.