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 is shifting toward a high-performance Rust core (v2.0.0) while grappling with immediate security spoofing threats and the complexities of multi-chain infrastructure on ICP and Polymarket.
    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

    V2 Architectural Transition & Performance
    Development suggests TypeScript is hitting performance ceilings for real-time high-load agents, necessitating the pivot to Rust (v2.0.0) and NATS Jetstream for scalability.
    Q1
    How should we manage the transition for developers currently using TypeScript as the core runtime moves to Rust?
    • Chucknorris: TypeScript proved inadequate for real-time multi-DEX handling due to systematic crashes.
    • lalalune: PR #6351 (v2.0.0) focuses on runtime in Rust/Typescript, removing non-essentials.
    1Maintain full TypeScript parity indefinitely.
    Ensures no developer fallout but slows the performance gains of the Rust pivot.
    2Enforce a 'Rust-for-Internal, TS-for-Plugins' hierarchy.
    Provides a clear performance path while keeping the ecosystem accessible to TypeScript builders.
    3Hard pivot to Rust v2 as the only supported runtime.
    Maximizes performance and security but risks alienating current contributors (lalalune is authoring 52% of runtime PRs).
    4Other / More discussion needed / None of the above.
    Security and Verification Gaps
    Recent GitHub spoofing incidents and confusion over bot wallet requirements (Sparta) highlight a need for robust authentication protocols and clear team communication.
    Q2
    Should ElizaOS mandate PGP-signed commits and official 'Council-Verified' badges for third-party plugins?
    • Odilitime: Suspicious GitHub repo (hash-llm) used manipulated Git commits to appear as legitimate team members.
    • Casino/Odilitime: Confusion over Sparta bot requiring seed phrases vs. private keys.
    1Implement PGP-only commit policies project-wide.
    Eliminates impersonation risks but raises the barrier for casual contributors.
    2Launch an on-chain verification registry for plugins.
    Builds 'Trust Through Shipping' by allowing users to verify safe agent containers.
    3Increase focus on documentation as the primary security layer.
    Relies on education but may not stop sophisticated social engineering attacks.
    4Other / More discussion needed / None of the above.
    Multi-Chain & Oracle Strategy
    Expansion to ICP and complexity in Polymarket Safe multisigs indicate elizaOS is becoming a cross-chain orchestration layer rather than just an LLM wrapper.
    Q3
    Should we pivot development resources from 'General Purpose Agents' to 'Autonomous Infrastructure Agents' on platforms like Jeju and ICP?
    • Shaw: Successfully implemented Eliza to run on ICP.
    • DorianD: Vision includes agents running independently as oracles posting results to the network.
    1Focus on the 'Agent as Oracle' use case.
    Positions elizaOS as a critical infrastructure provider for decentralized markets.
    2Prioritize consumer-facing flagship agents (Eli5/Otaku).
    Stronger brand visibility but may lag in technical decentralization milestones.
    3Develop the 'Jeju' decentralized compute network first.
    High risk/high reward; solves long-term autonomy but requires 'gargantuan' effort (DorianD).
    4Other / More discussion needed / None of the above.