{ "date": "2025-09-12", "meeting_context": "# North Star & Strategic Context\n\nThis 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.\n\n---\n\n**North Star:**\nTo build a truly autonomous, sustainable DAO that develops open-source software accelerating the path toward AGI, blending AI researchers, open-source hackers, and crypto degens to create AI agents streaming, shitposting, and trading 24/7 on auto.fun to attract users and bootstrap an autonomous organization.\n\n---\n\n**ElizaOS Mission Summary (`docs/blog/mission.mdx`):**\nThe elizaOS mission is to build an extensible, modular, open-source AI agent framework for Web2/Web3, seeing agents as steps toward AGI. Core values are Autonomy, Modularity, and Decentralization. Key products include the framework itself, DegenSpartanAI (trading agent), Autonomous Investor/Trust Marketplace (social trading intelligence), and the Agent Marketplace/auto.fun (launchpad).\n\n---\n\n**ElizaOS Reintroduction Summary (`docs/blog/reintroduction.mdx`):**\nelizaOS is an open-source \"operating system for AI agents\" aimed at decentralizing AI development away from corporate control. It's built on three pillars: 1) The Eliza Framework (TypeScript toolkit for persistent, interoperable agents), 2) AI-Enhanced Governance (building autonomous DAOs), and 3) Eliza Labs (R&D for future capabilities like v2, Trust Marketplace, auto.fun, DegenSpartanAI, Eliza Studios). The native Solana token coordinates the ecosystem and captures value. The vision is an intelligent internet built on open protocols and collaboration.\n\n---\n\n**Auto.fun Introduction Summary (`docs/blog/autofun-intro.mdx`):**\nAuto.fun is an AI-native, creator-first token launchpad designed for sustainable AI/crypto projects. It aims to balance fair community access with project funding needs through mechanisms like bonding curves and liquidity NFTs. Key features include a no-code agent builder, AI-generated marketing tools, and integration with the elizaOS ecosystem. It serves as a core product driving value back to the native token ($ai16z) through buybacks and liquidity pairing.\n\n---\n\n**Taming Information Summary (`docs/blog/taming_info.mdx`):**\nAddresses the challenge of information scattered across platforms (Discord, GitHub, X). Proposes using AI agents as \"bridges\" to collect, wrangle (summarize/tag), and distribute information in various formats (JSON, MD, RSS, dashboards, 3D shows). Showcases an AI News system and AI Assistants for tech support as examples. Emphasizes treating documentation as a first-class citizen to empower AI assistants and streamline community operations. ", "monthly_goal": "Current focus: Stabilize and attract new users to auto.fun by showcasing 24/7 agent activity (streaming, trading, shitposting), ship production ready elizaOS v2.", "daily_focus": "The elizaOS ecosystem is evolving with parallel development of core infrastructure, Web3 integration, and significant architectural improvements to enhance both developer and user experience.", "key_points": [ { "topic": "Architectural Evolution Strategy", "summary": "The team is undertaking a major architectural refactoring to simplify the codebase, reduce redundancy, and improve the developer experience, with critical discussions about merging AgentManager into AgentServer and implementing new features like browser DB integration.", "deliberation_items": [ { "question_id": "q1", "text": "How should we prioritize technical debt reduction vs. shipping new features for elizaOS v2?", "context": [ "Stan submitted PR #5864 for review, with discussions about merging AgentManager into AgentServer to reduce redundancy", "cjft reported progress on browser integration, noting they were close to loading with a browser DB" ], "multiple_choice_answers": { "answer_1": { "text": "Focus on technical debt reduction first to ensure a stable foundation for v2.", "implication": "This approach may delay new feature delivery but would create a more maintainable and extensible system long-term." }, "answer_2": { "text": "Balance technical debt reduction and new features in parallel development streams.", "implication": "This balanced approach maintains progress on both fronts but may strain development resources and slow overall delivery." }, "answer_3": { "text": "Prioritize shipping core v2 features first, then address technical debt in subsequent releases.", "implication": "This feature-first approach accelerates time-to-market for v2 but risks compounding technical debt and increasing refactoring costs later." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } }, { "question_id": "q2", "text": "How deeply should we integrate browser capabilities into the core framework?", "context": [ "cjft reported progress on browser integration, noting they were close to loading with a browser DB", "Business development priorities were shared in a Google Doc, highlighting needs for analytics, SaaS for credits, and feedback systems" ], "multiple_choice_answers": { "answer_1": { "text": "Make browser integration a first-class feature in the core framework.", "implication": "This deep integration would create a seamless cross-platform experience but increases core complexity and maintenance burden." }, "answer_2": { "text": "Create a modular browser extension system that's optional but well-supported.", "implication": "This modular approach maintains core simplicity while still providing browser capabilities for those who need them." }, "answer_3": { "text": "Focus on server-side capabilities and provide minimal browser integration patterns.", "implication": "This server-focused approach keeps the core lean but may limit adoption in browser-centric use cases and applications." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } }, { "question_id": "q3", "text": "Should we establish a formal Eliza Improvement Proposal system similar to Ethereum's EIPs/ERCs?", "context": [ "Discussion about implementing a structured proposal system similar to Ethereum's EIPs/ERCs to standardize development efforts and involve the community in a more organized way." ], "multiple_choice_answers": { "answer_1": { "text": "Implement a full EIP-style system with formalized processes and governance.", "implication": "This comprehensive approach would create strong community governance but requires significant process overhead and maintenance." }, "answer_2": { "text": "Create a lightweight proposal system focused on technical specifications only.", "implication": "This technical focus balances structure with flexibility but may not fully address governance needs." }, "answer_3": { "text": "Continue with the current GitHub-based issue and PR system with improved templates and tagging.", "implication": "This incremental approach minimizes process changes but may not provide sufficient structure for complex community governance." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } } ] }, { "topic": "Web3 Integration Strategy", "summary": "New Web3 initiatives are emerging in the ecosystem, including CoopaASI (a data sovereignty-focused AI assistant) and USDC tipping on Solana, raising strategic questions about how deeply to integrate blockchain capabilities into the core platform.", "deliberation_items": [ { "question_id": "q4", "text": "How should we balance Web2 and Web3 capabilities in the core elizaOS framework?", "context": [ "NativeSatoshi introduced CoopaASI, a Web3 AI Assistant focused on data sovereignty that combines blockchain with AI to create a \"digital vault\" where users maintain ownership of their data", "R0am implemented USDC tipping via x402 on Solana, extending existing Base functionality to support any SPL token" ], "multiple_choice_answers": { "answer_1": { "text": "Make Web3 a core pillar with first-class blockchain integration throughout.", "implication": "This Web3-first approach would differentiate us strongly but could alienate Web2 users and increase implementation complexity." }, "answer_2": { "text": "Maintain Web2 as the core with optional, modular Web3 plugins and extensions.", "implication": "This Web2-with-Web3-options approach maximizes user base but may dilute our blockchain differentiation." }, "answer_3": { "text": "Create separate Web2 and Web3 framework editions with shared core components.", "implication": "This dual-edition strategy provides clear options for different user segments but increases maintenance burden with two parallel stacks." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } }, { "question_id": "q5", "text": "Which blockchain data sovereignty model should we prioritize for agent memory and knowledge?", "context": [ "NativeSatoshi introduced CoopaASI, a Web3 AI Assistant focused on data sovereignty that combines blockchain with AI to create a \"digital vault\" where users maintain ownership of their data", "The CoopaASI tech stack includes Arweave permaweb for storage, Polygon network for transactions, MetaMask for Web3 identity, and Google's Gemini models for vector embeddings" ], "multiple_choice_answers": { "answer_1": { "text": "Prioritize Arweave-based immutable storage for permanent agent memory.", "implication": "This immutability-focused approach ensures permanent knowledge preservation but may have higher costs and slower access times." }, "answer_2": { "text": "Develop a hybrid model with local storage and selective blockchain persistence.", "implication": "This hybrid approach balances performance with permanence but requires complex synchronization logic." }, "answer_3": { "text": "Focus on Solana-native storage for speed and ecosystem alignment.", "implication": "This Solana-aligned approach maximizes integration with our token but ties us more closely to a single blockchain ecosystem." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } } ] }, { "topic": "AI Capability Expansion", "summary": "The ecosystem is expanding its AI capabilities both through internal developments like VSCode server integration with Claude code support and external opportunities like a new 200B+ parameter MOE model project, raising questions about which AI enhancements to prioritize.", "deliberation_items": [ { "question_id": "q6", "text": "Which AI model integration strategy should we prioritize for auto.fun's 24/7 agents?", "context": [ "A request was posted for ML/AI engineers with experience in training and fine-tuning 200B+ parameter MOE models for a new project", "Agent Joshua made progress on launching a VSCode server in CVM with flox and Claude code integration, eliminating the need for TEE Simulator" ], "multiple_choice_answers": { "answer_1": { "text": "Integrate with frontier models (200B+ parameters) for maximum capability.", "implication": "This cutting-edge approach maximizes agent capabilities but increases costs and infrastructure requirements significantly." }, "answer_2": { "text": "Focus on model efficiency and fine-tuning smaller models for specific tasks.", "implication": "This efficiency-focused approach optimizes for cost and performance but may limit the complexity of tasks agents can handle." }, "answer_3": { "text": "Implement a dynamic model selection system that chooses appropriate models by task.", "implication": "This adaptive approach provides flexibility but increases system complexity and integration requirements." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } }, { "question_id": "q7", "text": "How should we approach confidential computing and TEEs in the elizaOS framework?", "context": [ "Agent Joshua made progress on launching a VSCode server in CVM with flox and Claude code integration, eliminating the need for TEE Simulator", "Agent Joshua developed a solution for managing accounts without storing keys, potentially useful for subscription services with x402" ], "multiple_choice_answers": { "answer_1": { "text": "Make TEEs a central security feature available throughout the framework.", "implication": "This security-first approach creates strong differentiation but increases complexity and may limit deployment options." }, "answer_2": { "text": "Offer TEE capabilities as an optional premium feature for sensitive use cases.", "implication": "This tiered approach balances security with simplicity but creates a two-tier security model in the ecosystem." }, "answer_3": { "text": "Focus on alternative security approaches while maintaining minimal TEE compatibility.", "implication": "This pragmatic approach reduces implementation complexity but may not satisfy the highest security requirements." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } } ] } ] }