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 the framework architecture toward modular 'skills' while addressing critical memory consumption bottlenecks in the build pipeline.
    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

    Modular Architecture: Plugins to Skills
    To improve composability and DX, the team is proposing a strategic pivot to convert all existing plugins into modular 'skills'.
    Q1
    How deeply should the framework decouple reasoning models from embedding and execution handlers?
    • Jin proposed a strategic shift to convert all plugins into skills for better composability.
    • aicodeflow suggested rethink plugins as 'skills' rather than just integrations.
    1Complete decoupling of all primitives.
    Maximizes flexibility but may introduce integration overhead for new developers.
    2Standardized skill wrappers for plugins.
    Preserves current ease-of-use while providing a roadmap for future modularity.
    3Model-specific skill optimizations.
    Prioritizes execution speed but risks vendor lock-in for certain agent types.
    4Other / More discussion needed / None of the above.
    Q2
    Should the Council mandate a fallback embedding model for all cross-plugin operations?
    • Stan noted Anthropic plugin needs OpenAI key for TEXT_EMBEDDING handler fallback.
    • Andrei Mitrea documented MCP integration requiring OpenAI even when only using Anthropic.
    1Mandate OpenAI/standard fallbacks.
    Ensures reliability across the framework at the cost of external dependencies.
    2Implement local-first embedding defaults.
    Aligns with the vision of local autonomy but increases user system requirements.
    3Dynamic provider negotiation.
    Agents negotiate capabilities at runtime, increasing architectural complexity.
    4Other / More discussion needed / None of the above.
    Operational Infrastructure Scarcity
    Critical performance bottlenecks, specifically excessive memory usage (21GB+) during builds, are threatening local development efficiency.
    Q3
    What is the acceptable resource ceiling for the elizaOS build environment?
    • Odilitime identifying severe memory issues with turbo builds (21GB to 27GB+).
    • Madjin reported issue #6332 regarding memory consumption impacting developer experience.
    1Aggressive optimization for 16GB RAM limits.
    Ensures the framework remains accessible to individual builders on consumer hardware.
    2Cloud-first build specialization.
    Moves heavy lifting to elizaOS Cloud, incentivizing managed deployment.
    3Modularized package builds.
    Reduces build load but complicates monorepo dependency management.
    4Other / More discussion needed / None of the above.