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 ecosystem is transitioning from a framework-only model to a dual-tier architecture involving managed ElizaOS Cloud services and trustless on-chain decision provenance.
    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

    Ecosystem Governance & Labeling
    Recent heated debates regarding the official status of projects like Hyperscape reveal a need for clearer distinction between Labs-official products and incubated ventures.
    Q1
    How should the Council define the 'Incubated' status to prevent community misinformation and brand dilution?
    • Odilitime clarified Hyperscape is Eliza-related but not directly launched by Eliza Labs.
    • Heated disagreement over Hyperscape being a core '10-year flywheel' project.
    1Formalize a 'Verified Ecosystem Partner' badge for non-Labs projects.
    Reduces liability for Labs while acknowledging high-quality community contributors.
    2Restrict 'Eliza Labs' branding strictly to internally funded/staffed initiatives.
    Ensures absolute clarity but may isolate key joint ventures like Hyperscape.
    3Establish a public 'Project Registry' defining ownership and support tiers.
    Provides the transparency requested by community members like 33coded and satsbased.
    4Other / More discussion needed / None of the above.
    Trust & Trading Infrastructure
    Community focus is shifting toward autonomous trading agents and the requirement for immutable decision tracking through on-chain provenance.
    Q2
    Should on-chain decision provenance (e.g., xProof) become a recommended standard for all ElizaOS spectral/trading agents?
    • xProof.app plugin creates immutable timestamps for agent decisions on MultiversX.
    • Multiple developers (meowww404, Ape Ape) are actively building plug-and-play trading flows.
    1Mandate provenance tracking for agents listed on official ElizaOS Cloud tiers.
    Increases user trust in autonomous agents but adds latency to execution.
    2Keep provenance as an optional plugin but promote it in core documentation.
    Follows the 'Developer First' principle by maintaining flexibility.
    3Develop an internal Labs-native provenance module to replace third-party dependencies.
    Ensures deep integration with the core framework but increases maintenance load.
    4Other / More discussion needed / None of the above.
    Q3
    How can we optimize the plugin registry review process to support the surge in financial/trading integrations?
    • meowww404 inquiring about timeline/process for trading plugin inclusion.
    • Odilitime managing waitlists for migration and plugin reviews manually (Registry PR requests).
    1Appoint a dedicated 'Plugin Warden' for financial/trading categories.
    Speeds up time-to-market for high-value trading tools.
    2Automate security scanning for trading plugins to reduce manual review burden.
    Ensures 'Execution Excellence' by verifying safety programmatically.
    3Shift to a community-vetted 'Registry Beta' for unverified third-party plugins.
    Encourages rapid experimentation while maintaining the 'Core' repo's integrity.
    4Other / More discussion needed / None of the above.