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 pivot from internal framework stabilization to the deployment of resilient cloud-native infrastructure on 'Jeju' to transition the ecosystem toward a public-facing decentralized AI economy.
    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

    Jeju Infrastructure & Decentralization Timeline
    The migration of service infrastructure to the Jeju platform is a prerequisite for the public launch of Cloud and Babylon products, signaling a shift from centralized hosting (AWS) to self-owned physical data centers.
    Q1
    How aggressively should the Council prioritize the transition from AWS to self-owned data center infrastructure?
    • Shaw: Initially launching on AWS with plans to transition to self-owned permissionless infrastructure in data centers by year-end.
    • Shaw: Infrastructure is being migrated to run on jeju so it's 'already all done and tested' when ready to go public.
    1Phased Hybrid Migration
    Ensures stability on AWS while gradually stress-testing the Jeju physical layer to mitigate downtime risks.
    2Accelerated Sovereign Transition
    Prioritizes total decentralization and cost reduction from cloud providers but risks early operational instability.
    3AWS-Primary Optimization
    Delays the physical data center rollout to focus exclusively on software reliability and rapid user scaling.
    4Other / More discussion needed / None of the above.
    Token Migration & Economic Trust
    As the migration from AI16Z to ElizaOS concludes in February, the Council must ensure token utility and documentation meet the needs of a wider investor base to sustain current positive sentiment.
    Q1
    How should the Council address the current documentation gap regarding tokenomics and inter-token relationships (DegenAI/Ruby)?
    • Kenk: Acknowledged the need for improved website accessibility regarding token information.
    • DorianD: Suggestions to enhance documentation explaining ElizaOS's role as the first appcoin on Jeju.
    1Comprehensive Ecosystem Unified Portal
    Clarifies the utility of all sub-tokens, potentially stabilizing cross-token volatility through transparent information.
    2Selective Disclosure focused on ElizaOS
    Concentrates community attention on the core protocol token but leaves secondary projects to independent discovery.
    3Dynamic Infographic/AI-Bridge Documentation
    Utilizes agent technology to explain complex Jeju appcoin dynamics in real-time, aligning with our 'Taming Information' strategy.
    4Other / More discussion needed / None of the above.
    Autonomous Trade & DegenAI Integration
    The development of DegenAI as a flagship autonomous trading agent creates a high-stakes test case for the framework's reliability and its ability to handle cross-chain financial operations.
    Q1
    What level of risk oversight is required for the autonomous trading engine powered by the ElizaOS framework?
    • Omid Sa: DegenAI being developed to do profitable trades for those with 1M tokens using Chainlink and Cambrian.
    • Odilitime: Plans to showcase DegenAI trading wins on social media platforms.
    1Conservative Gated Beta
    Protects the framework's reputation by limiting exposure to high-volume holders until the logic is triple-audited.
    2Aggressive Public Marketing of 'Wins'
    Drives massive adoption and token demand but increases scrutiny from regulatory bodies and potential for backlash on losses.
    3Framework-Only Decentralized Deployment
    Shifts liability to builders by providing the tools for trading without assuming operational control of the trader agents.
    4Other / More discussion needed / None of the above.