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 divergence between rapid technical architectural shifts (V2/n8n) and deteriorating community trust regarding token migration and technical stability.
    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 Pivot: N8N Workflow Integration
    The shift from native plugins to an n8n-based three-layer architecture represents a major pivot in how agents execute automated tasks and handle credentials.
    Q1
    How should we balance the immediate DX benefits of n8n against the long-term risk of reliance on external workflow engines?
    • s: '95% want AI workflow builder... focus on connecting services like Gmail, Notion, Calendar.'
    • Architecture Proposal: Layer 1 OAuth Gateway, Layer 2 Workflow Engine, Layer 3 AI Generator.
    1Aggressive Integration
    Rapidly ships a consumer-ready platform but may create vendor lock-in with n8n.
    2Parallel Native Dev
    Maintains framework independence at the cost of significantly slower feature delivery.
    3Abstracted Interface
    Builds a generic 'Workflow' layer that supports n8n initially but allows interchangeable engines later.
    4Other / More discussion needed / None of the above.
    Q2
    Should the 'ElizaRouter' be prioritized as core infrastructure to maintain execution excellence across multiple models?
    • DorianD: 'Request for ElizaRouter... distributed mechanism where receiving nodes select optimal nodes.'
    1Native Core Feature
    Ensures framework-level reliability and cost optimization for all developers.
    2External Plugin Only
    Reduces core repository bloat but risks uneven QoS across the ecosystem.
    3Delay until V2 Stable
    Focuses limited dev resources on core architecture before adding complex routing layers.
    4Other / More discussion needed / None of the above.
    Ecosystem Trust & Migration Resolution
    Serious community friction is emerging regarding the 1:10 token migration, team allocation, and migration site technical failures.
    Q3
    How will we address the perceived '40% team allocation' and transparency concerns to restore 'Trust Through Shipping'?
    • Community: 'Questioned 40% team allocation... community received 6 tokens while team received 40%.'
    • Jayzen: 'Are the wallets holding 40% known and do they have a vesting schedule?'
    1On-chain Vesting Reveal
    Provides maximum transparency and potentially silences 'scam' narratives.
    2Framework Utility Airdrops
    Distributes supply toward active builders/holders to dilute initial team allocation concerns.
    3Revenue-Driven Buybacks
    Focuses on the 'Buy-back' mechanism from credit card rails mentioned by Odilitime to provide floor support.
    4Other / More discussion needed / None of the above.
    Q4
    What emergency measures are required for users stuck in zero-liquidity migration loops on the ETH chain?
    • Sarthak: '98% losses when attempting to swap ElizaOS tokens on ETH... due to zero liquidity.'
    1Manual Whitelist Migration
    Saves individual holders but creates significant operational overhead for the team.
    2Incentivized LP Provisioning
    Restores market health but requires diverting capital from R&D (Eliza Labs).
    3Cross-Chain Bridge Subsidy
    Directly facilitates multichain accessibility at project expense.
    4Other / More discussion needed / None of the above.