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
    Strategic evolution of the Jeju/x402 tokenomics model inspired by market leaders, while prioritizing ecosystem stability and plugin interoperability.
    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 Economic Model Alignment
    The Council must evaluate a proposed transition to a Venice-style 'Compute-as-a-Service' staking model to drive network utility and hardware upgrades.
    Q1
    Should ElizaOS adopt a proportional staking model where 1% stake equals 1% of network inference allocation?
    • DorianD: Proposed mechanism where stakers receive proportional access to network inference tokens.
    • Venice VVV: Successfully used 50% supply airdrop and staking for compute credits to reach 1M users.
    1Adopt full freemium staking.
    Maximizes token lockups but risks pricing out low-capital developers.
    2Implement a hybrid credit system.
    Balances ecosystem accessibility with incentives for large-scale compute providers.
    3Maintain current fee-for-service.
    Ensures simplicity and immediate revenue but provides lower long-term staking pressure.
    4Other / More discussion needed / None of the above.
    Q2
    Does the utilization-based fee distribution provide sufficient incentive for hardware providers?
    • DorianD: Suggested economic pressure for hardware upgrades to maximize fee earnings through node utilization.
    1Aggressive utilization rewards.
    Accelerates the transition to high-performance GPU clusters across the network.
    2Flat capacity rewards.
    Prioritizes network breadth and geographic availability over raw compute power.
    3Dynamic bidding marketplace.
    Allows market forces to set prices but introduces agent-side cost unpredictability.
    4Other / More discussion needed / None of the above.
    Framework Reliability & Plugin Proliferation
    Rapid contribution of complex plugins like MEM0 and APEX Oracle requires stricter validation to prevent framework fragmentation.
    Q3
    Should deep-market analytics like APEX Oracle be integrated as core features or remain third-party plugins?
    • Vlt9: Introduced APEX Oracle v0.5.0 for deep-market analytics and Sybil detection.
    • Julio Holon: Raised concerns about the reliability of plugin-orchestrator and version selection.
    1Incorporate into Core Framework.
    Standardizes agent security against wash-trading but increases framework overhead.
    2Establish a 'Verified' tier.
    Signals quality and reliability without bloating the ElizaOS core repository.
    3Maintain decentralized plugin ecosystem.
    Maximizes innovation speed but leaves version stability to individual developers.
    4Other / More discussion needed / None of the above.
    Q4
    How can we mitigate the current version confusion (v2-develop vs alpha) impacting developer trust?
    • Julio Holon: Uncertain between using v2-develop branch versus alpha channel for production.
    • Meme Broker: Expressed frustration over limited visibility/engagement with VPS orchestration tools.
    1Aggressive branch consolidation.
    Provides a single source of truth for builders but may slow down experimental feature shipping.
    2Enhanced documentation gates.
    Uses AI-driven documentation to guide developers to the correct version based on use-case.
    3Automated stability labeling.
    Forces clearer technical signaling but requires significant CI/CD maintenance effort.
    4Other / More discussion needed / None of the above.