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 must address a critical friction point between strict execution parameters (migration deadlines) and community trust while simultaneously shipping the high-impact v2 cross-language core architecture.
    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 Migration & Community Governance
    Recent logs reveal significant community distress and scam vulnerability surrounding the closed February 4th migration deadline, threatening the 'Trust Through Shipping' core principle.
    Q1
    How should the Council handle verified long-term holders who missed the 90-day migration window?
    • Long-term holders (Andi CEGY, fibsonly) expressed frustration and advocated for a manual process for verified on-chain proof.
    • Omid Sa confirmed no further migration support is available, citing the official deadline.
    1Maintain strict deadline enforcement (No exceptions).
    Protects the integrity of operational timelines but risks alienating loyal ecosystem participants.
    2Implement a one-time manual verification window for significant holders.
    Restores community trust but increases administrative overhead and security risks.
    3Transition remaining migration utility to automated on-chain governance (DAO).
    Decentralizes the decision-making process at the cost of immediate execution speed.
    4Other / More discussion needed / None of the above.
    V2 Architectural Expansion & Developer Reach
    The shift toward a multi-language (Rust, Python, TS) core and the introduction of the ActionFilterService represent a major leap in framework scalability and performance.
    Q2
    Given the 'Developer First' principle, how should we prioritize the rollout of multi-language support?
    • lalalune: 52% of runtime PRs, driving next-gen support for Rust and Python (#6485).
    • DorianD: Recommendation to include 'ElizaCloud awareness' in base installs to improve discoverability.
    1Aggressive rollout: Deprecate v1.6.x infrastructure to force V2 adoption.
    Accelerates ecosystem evolution but risks breaking existing stable agent deployments.
    2Parallel maintenance: Support v1.x while slowly onboarding enterprise builders to Rust/Python cores.
    Ensures stability but splits developer resources across multiple frameworks.
    3Developer-led: Release V2 as an opt-in 'Labs' experiment until core plugins are parity-complete.
    Minimizes risk and aligns with 'Execution Excellence' by prioritizing reliability over features.
    4Other / More discussion needed / None of the above.
    Q3
    Should the framework include native 'Cloud-Aware' system prompts by default?
    • DorianD: suggested base install should include prompts making agents aware of ElizaCloud capabilities.
    1Yes—Implement native service discovery for all agents.
    Significantly increases ElizaCloud adoption and creates a seamless node-to-cloud UX.
    2No—Keep the open-source framework completely cloud-agnostic.
    Preserves decentralization purity but may hinder the project's revenue-driven buyback strategy.
    3Optional—Add a setup flag for users to enable cloud-awareness.
    Offers a middle ground but risks lower discoverability for non-technical users.
    4Other / More discussion needed / None of the above.
    Tokenomics & Market Value Alignment
    Community sentiment indicates a disconnect between the technical power of the OS and the utility of the native token, with market caps trailing behind meme-driven competitors.
    Q4
    What is the most viable path to strengthen the tie between the Framework and the Token?
    • DannyNOR NoFapArc: 'ELIZA framework has no direct tie to the token, creating zero inherent reason to buy it.'
    • Alexei: mentioned potential buyback mechanisms using revenue from Eliza Cloud.
    1Revenue-based buybacks: Direct ElizaCloud fees to buy/burn or redistribute tokens.
    Provides clear economic utility linked to platform growth.
    2Staking for Compute: Require tokens to unlock high-performance plugins or cloud features.
    Creates high demand for builders but might increase friction for new developers.
    3Governance Weight: Tie architecture decisions and plugin whitelisting to token holdings.
    Empowers the community but risks 'whaling' where top holders dictate R&D.
    4Other / More discussion needed / None of the above.