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 focus shifted toward long-term survivability: architecting the 'Eliza 2.0' radical redesign while managing a critical regulatory delisting crisis on Korean exchanges.
    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

    Architecture Evolution: Eliza 2.0 Redesign
    Shaw has proposed and already begun porting a radical overhaul that replaces traditional APIs and servers with a multi-language, Claude-friendly runtime. This aims to maximize framework reliability and composability through unified abstractions in TypeScript, Rust, and Python.
    Q1
    Does eliminating traditional API, Server, and CLI structures improve the 'Developer First' core principle or create excessive friction for existing builders?
    • Shaw: 'The vision eliminates traditional API, server, CLI, and project structures in favor of an extremely Claude-friendly documented runtime.'
    • Shaw confirmed having already ported the implementation with a branch available for review.
    1Full commitment to the 2.0 redesign.
    Prioritizes future-proofing and AI-native DX at the cost of potential breaking changes for v1.x legacy users.
    2Hybrid approach maintaining legacy endpoints.
    Reduces migration friction but risks technical debt and bloat within the new unified runtime architecture.
    3Staged rollout focusing on Rust/Python FFI first.
    Verifies performance gains from multi-language support before dismantling the existing CLI/API infrastructure.
    4Other / More discussion needed / None of the above.
    Token Utility and Regional Regulatory Pressure
    The coordinated delisting from Korean exchanges (Bithumb, Korbit, Coinone) due to 'transparency concerns' highlights a critical need for clearly defined token utility and public communication strategies. Community members are increasingly questioning framework integration for the native token.
    Q2
    How should the Council address the 'transparency' critique from DAXA while simultaneously integrating utility into the framework?
    • Korbit announced delisting citing lack of transparency in the token migration process and failure to disclose material information.
    • stoikol raised questions about the lack of defined utility specifically questioning why it's not used for gas or payments.
    1Immediate publication of a Comprehensive Token Utility Whitepaper.
    Restores trust with exchanges and clear utility paths but limits flexibility for future lab R&D.
    2Integrate x402 micropayments as a core utility requirement.
    Directly links token usage to agent actions, addressing 'utility' concerns via technical implementation.
    3Decentralized governance focus for Korean market recovery.
    Uses the DAO structure to prove transparency to regulatory bodies, though this may slow down rapid execution.
    4Other / More discussion needed / None of the above.