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 from staging-green to full production for Eliza Cloud while simultaneously navigating community skepticism regarding token dilution and foundation transparency.
    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

    Cloud Production Hardening
    Recent logs indicate a successful push of Eliza Cloud apps to production, but significant scaling gaps and infrastructure vulnerabilities require immediate attention to reach the 1000-app ceiling.
    Q1
    How should we prioritize the remaining 'Product 2' infrastructure gaps given our North Star of Execution Excellence?
    • NubsCarson: The current code's realistic ceiling is ~dozens of apps, not ~1000 (#8321).
    • Logs indicate ingress not installed and Postgres connection ceilings are P0 blockers.
    1Halt all feature adds to fix P0 scaling blockers immediately.
    Ensures reliability but may delay the rollout of flagship agents.
    2Continue the 10-user launch while hotfixing scaling issues as they arise.
    Allows for real-world testing but risks 'Trust Through Shipping' if failures occur.
    3Delegate infrastructure hardening exclusively to the core dev team (standujar/NubsCarson).
    Concentrates technical risk on a small number of contributors.
    4Other / More discussion needed / None of the above.
    Q2
    Should we move to self-hosted runners to increase developer productivity as suggested by recent migrations?
    • PR #8501: Migrated to self-hosted runners to improve speed and reliability of dev processes.
    • Review dependency: 78% of runtime PRs reviewed by odilitime.
    1Standardize all CI/CD on self-hosted Hetzner runners.
    Reduces costs and build times but introduces hardware maintenance overhead.
    2Maintain a hybrid model using GitHub-hosted runners for sensitive fork PRs.
    Balances build performance with high security isolation for open-source contributors.
    3Reject further infrastructure complexity and stick to standard GitHub runners.
    Prioritizes simplicity over DX speed until cloud revenue stabilizes.
    4Other / More discussion needed / None of the above.
    Ecosystem and Token Strategic Alignment
    Community members are raising concerns about market dilution from side-projects using separate tokens and are calling for clearer branding between 'Eliza Cloud' and 'Eliza OS'.
    Q3
    How shall the Council address the perceived market dilution from platforms like waifu.fun using separate tokens?
    • Community member zadayos: Argued that separate tokens create market dilution and skepticism (#2026-06-20).
    • odilitime clarified that the foundation manages the main token independently (#2026-06-22).
    1Mandate that all official ElizaOS ecosystem tools must use $ELIZAOS natively.
    Unifies the economy but restricts the autonomy of sub-platforms.
    2Allow sub-platforms to innovate with their own tokens while maintaining a token-backfill to $ELIZAOS.
    Facilitates R&D while ensuring the main token holds long-term value.
    3Release clear documentation explaining the separation between core infrastructure and lab experiments.
    Maintains transparency but may not satisfy investors concerned about price action.
    4Other / More discussion needed / None of the above.
    Q4
    Should the project officially pivot branding to 'ElizaOS' over 'Eliza Cloud' to align with its vision as an operating system?
    • ghss44: Advocated for positioning as an operating system for agents rather than a cloud service (#2026-06-22).
    1Adopt 'ElizaOS' as the primary brand for all components.
    Clarity of vision as a foundational layer for AI agents.
    2Keep 'ElizaOS Cloud' as the commercial product name while keeping 'ElizaOS' for the open-source framework.
    Maintains marketing separation between the SaaS and the SDK.
    3Rebrand to a more neutral 'Eliza Labs' identity for 2026.
    Reflects the R2D nature of the work but loses the 'Operating System' narrative hook.
    4Other / More discussion needed / None of the above.