▶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.

---

North Star: To 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.

---

ElizaOS Mission Summary (`docs/blog/mission.mdx`): The 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).

---

ElizaOS Reintroduction Summary (`docs/blog/reintroduction.mdx`): elizaOS 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.

---

Auto.fun Introduction Summary (`docs/blog/autofun-intro.mdx`): Auto.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.

---

Taming Information Summary (`docs/blog/taming_info.mdx`): Addresses 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.

▶Daily Strategic Focus

Significant progress on two strategic initiatives: game-based prediction markets as a new engagement vector and digital twin implementation to enhance agent-user relationship intelligence.

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.

Key Deliberations

Game-Based Prediction Markets

Shaw proposed an innovative system using games as prediction market oracles with frequent resolution cycles, while DorianD provided regulatory context and Odilitime suggested technical solutions for result verification.

How should we position game-based prediction markets within our auto.fun ecosystem to maximize both engagement and regulatory compliance?

Shaw proposed using games as prediction market oracles that create predictable but uncertain outcomes in ZK containers
DorianD provided context on regulatory challenges, noting Polymarket's CFTC fine for operating as an unregistered derivatives platform

1Position as pure gaming entertainment with secondary betting markets developed by third parties

Reduces regulatory exposure but limits direct revenue potential and ecosystem integration.

2Fully integrate with auto.fun as a core feature but implement decentralized orderbooks and TEE attestation for compliance

Creates stronger user engagement but increases technical complexity and potential regulatory scrutiny.

3Launch as an experimental testnet feature with limited liquidity while we iteratively test regulatory boundaries

Allows for controlled exploration of the concept but may slow adoption and competitive advantage.

4Other / More discussion needed / None of the above.

What tokenomic structure would best serve our game-based prediction market system while aligning with our broader auto.fun strategy?

Proposed uncapped ERC-20 "gold token" as currency with no protocol-provided liquidity
Shaw suggested an uncapped supply ERC-20 "gold token" with no protocol-provided liquidity and a fee on transfers

1Adopt Shaw's proposed uncapped ERC-20 with transfer fees but no protocol liquidity

Creates an isolated in-game economy but may limit cross-platform utility and value capture for existing token holders.

2Use existing $AI16Z/ElizaOS tokens with special platform mechanisms for game activities

Strengthens utility of our core token but potentially introduces regulatory complications by directly tying prediction market outcomes to token value.

3Implement a dual-token system with game-specific tokens that can be exchanged for core ecosystem tokens at variable rates

Balances regulatory separation with ecosystem integration but increases system complexity for users.

4Other / More discussion needed / None of the above.

Digital Twin Implementation

Odilitime proposed a significant enhancement to agent intelligence through digital twin technology that would track and model user information from chats in RAG to create more personalized and efficient interactions.

How should we prioritize digital twin implementation relative to other v2 features given our monthly goal of shipping production-ready elizaOS v2?

Odilitime proposed tracking user information from chats in RAG and creating an evaluator that maintains a "character file" or digital twin
Current Monthly Directive (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

1Make digital twins a core v2 feature and expedite development with dedicated resources

Could delay overall v2 release but would deliver a more differentiated product with stronger relationship capabilities.

2Include as an experimental feature in v2 with basic implementation, planning fuller rollout in subsequent updates

Balances innovation with timely delivery while allowing for user feedback to guide full implementation.

3Defer to post-v2 roadmap to focus on more fundamental stability and performance features first

Ensures timely v2 delivery but postpones a potentially valuable differentiation factor in the competitive AI agent landscape.

4Other / More discussion needed / None of the above.

What approach should we take to balance privacy considerations with the relationship intelligence benefits of digital twins?

This would enable more efficient context management by focusing only on relationship-relevant information
Implementation could run as a background process outside the chat pathway

1Store all digital twin data locally on user devices with opt-in cloud sync for multi-device consistency

Maximizes privacy but creates technical challenges for persistent agent access across sessions and devices.

2Implement explicit consent mechanisms with granular control over what relationship data is stored and used

Balances privacy with functionality but adds friction to the user experience through permission requests.

3Use a federated learning approach where relationship patterns are learned collectively but individual data remains private

Provides privacy benefits while still improving system-wide intelligence, though at the cost of implementation complexity.

4Other / More discussion needed / None of the above.

Token Migration Strategy

The upcoming AI16z to ElizaOS token migration on October 21st represents a critical transition for the ecosystem, with various stakeholder concerns emerging around migration mechanics and post-migration operations.

How should we approach communication and support during the final week before the October 21st token migration?

Discussion about an upcoming token migration, with users seeking clarity on how it affects open positions
Brief mention of "15% SAFT in new tokenomics" with confirmation that community cannot participate as "it's closed"

1Launch a comprehensive migration portal with step-by-step guides, live support, and automated verification tools

Provides maximum support but requires significant short-term resource allocation during a critical development period.

2Focus on targeted communication to active holders through Discord and email with clear FAQs and migration instructions

Balances resource efficiency with adequate support for most users but may leave some edge cases underserved.

3Partner with major exchanges and wallets to handle the technical aspects of migration, focusing our efforts on strategic messaging

Leverages existing infrastructure but cedes some control over user experience during a crucial transition.

4Other / More discussion needed / None of the above.

What approach should we take to address community questions about the 15% SAFT allocation in the new tokenomics?

Could you please elaborate on 15% SAFT in new tokenomics? Can community participate?
"Nope it's closed" (Odilitime)

1Provide full transparency on SAFT allocation details, rationale, and how it benefits the ecosystem long-term

Builds trust through openness but may invite debate about allocation decisions that have already been finalized.

2Focus communication on future community participation opportunities rather than closed SAFT details

Shifts attention forward constructively but might appear evasive to community members seeking specific information.

3Create a formal governance proposal that outlines the SAFT structure and allocation, opening it for community discussion

Demonstrates commitment to governance but could delay implementation if significant changes are proposed.

4Other / More discussion needed / None of the above.

Council Briefing

North Star & Strategic Context

Key Deliberations