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 framework transitions toward an economic layer with v3 development and the AIGEN protocol, while facing friction in developer documentation for Socket.IO integrations.
    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

    Economic Layer & Agent Identity Transition
    Recent shifts prioritize 'AgentID' and the AIGEN Protocol, moving from simple messaging to a secure, cryptographic identity framework for autonomous agent economies.
    Q1
    How should we balance the pivot toward the 'AgentID' framework with existing messaging protocol support?
    • Formal deprioritization of standalone messaging (XMTP) in favor of AgentID.
    • AIGEN Protocol (#6708) introduced to formalize economic incentives.
    1Full pivot to Identity.
    Maximizes security but may alienate developers using agents purely for communication.
    2Dual-track development.
    Retains legacy users while building the future, but splits R&D bandwidth.
    3Identity as a messaging wrapper.
    Seamlessly upgrades the current user base to the new standard without breaking workflows.
    4Other / More discussion needed / None of the above.
    Q2
    Should the AIGEN token rewards strictly target tool contributions or expand to community-led documentation?
    • AIGEN Protocol offers 1,000-10,000 tokens for plugin builds.
    • Community frustration over lack of Socket.IO and token utility documentation.
    1Code-only rewards.
    Ensures high technical value but leaves the project with a high barrier to entry.
    2Holistic contribution rewards.
    Accelerates 'Execution Excellence' by incentivizing clear documentation alongside code.
    3Core-team controlled allocation.
    Maintains strict quality control but limits decentralized growth potential.
    4Other / More discussion needed / None of the above.
    Developer Trust and V2/V3 Technical Debt
    Core developers are focused on v3, leaving v2 integrators struggling with undocumented Socket.IO patterns and installation failures.
    Q3
    How do we maintain developer trust during the transition from v2 to v3 given the documentation gap?
    • User shah0406 found Socket.IO patterns via debugging rather than docs.
    • Core dev odilitime noted focus is currently on v3 development.
    1Assign a dedicated V2 maintenance lead.
    Provides a safety net for current builders at the cost of slight v3 delay.
    2Automated codebase extraction (Cursor/AI).
    Low effort solution that encourages developers to 'self-serve' via AI tools.
    3Freeze v2 support to accelerate v3.
    Achieves the 'Monthly Goal' faster but risks temporary reputational damage.
    4Other / More discussion needed / None of the above.
    Q4
    Should we address ownership concentration in runtime maintenance to improve shipping velocity?
    • odilitime: 70% of recent bugfix work (17 commits, 895 files).
    • Review dependency: Greptile apps flagging 'Medium Risk' on core runtime changes.
    1Mandatory peer-review for runtime PRs.
    Increases security grade but slows down shipping speed.
    2Decentralize the 'Core Dev' role.
    Reduces the bus factor risk by onboarding high-output contributors like NubsCarson.
    3Maintain current high-trust hierarchy.
    Ensures consistency in vision during the critical v3 migration phase.
    4Other / More discussion needed / None of the above.