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 transition toward Eliza 2.0 and the Jeju Layer 2 launch has introduced a critical tension between rapid technical innovation (Rust/multi-language support) and deteriorating community trust regarding token utility and transparency.
    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

    Token Utility vs. Regulatory Optics
    The delisting of elizaOS/ai16z tokens from Korean exchanges due to lack of transparency in migration creates a significant barrier to the goal of 'Trust Through Shipping' and highlights the urgent need for a clear, documented token utility roadmap.
    Q1
    How should the Council address the Korbit/DAXA delisting to restore international market confidence?
    • Korbit officially announced trading termination... citing lack of transparency in the token migration process. (Discord, 2026-01-08)
    • Community members expressed concern that $elizaOS utility is currently limited to planned but inactive gas fees. (Discord, 2026-01-10)
    1Formalize and publish a Token Utility Whitepaper immediately.
    Prioritizes transparency and provides exchanges with the 'material information' necessary for potential re-listing.
    2Pivot to a 'Service-First' communication strategy, ignoring speculative listings.
    Focuses on ElizaOS Cloud adoption but risks further structural price pressure from contributor minting without buy-side demand.
    3Accelerate Jeju H2 2026 gas fee implementation to immediate-term priority.
    Creates organic token demand instantly but may delay core framework stabilization (v1.6.x).
    4Other / More discussion needed / None of the above.
    Q2
    How do we mitigate the reputation risk posed by 'experimental' tokens launched by core members?
    • Users expressed concerns about multiple token deployments (referred to as "rugs") including utility and creator pump tokens. (Discord, 2026-01-10)
    1Enforce a Council-approved 'Official Ecosystem' branding protocol.
    Clearly separates official infrastructure from individual R&D experiments to protect the main project's integrity.
    2Celebrate experimental chaos as a feature of open-source decentralization.
    Maintains developer freedom but will likely continue to alienate risk-averse enterprise partners.
    3Implement a 'Council Quality Seal' for validated agents and tokens.
    Creates a regulated tier within the bazaar, building trust for users while allowing permissionless builds.
    4Other / More discussion needed / None of the above.
    Eliza 2.0 Architectural Pivot
    The proposal for Eliza 2.0 to move toward a Rust/multi-language runtime with FFI plugin interoperability represents a massive technical leap but threatens to fragment the current developer base if not handled carefully.
    Q3
    Does the radical redesign of Eliza 2.0 align with the 'Developer First' principle or create a migration wall?
    • Shaw proposed a radical redesign... multi-language support (TS, Rust, Python) eliminating traditional API/server structures. (Discord, 2026-01-09)
    • Shaw demonstrated LLM-free Eliza agents in Rust playing simulations without expensive model calls. (Discord, 2026-01-10)
    1Commit fully to Rust-core as the primary performance engine.
    Accelerates long-term beneficial AGI paths but may exclude current TypeScript-reliant web developers.
    2Maintain parallel v1.x and v2.x lifecycles for at least 12 months.
    Protects existing community value at the cost of doubling maintenance overhead and splitting developer focus.
    3Focus 2.0 exclusively on 'Skills' interoperability across agents.
    Allows the Council to achieve the 'Open & Composable' goal regardless of the underlying runtime language.
    4Other / More discussion needed / None of the above.