▶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

Community concern over token migration and platform stability rising as technical teams prioritize codebase quality and next-generation features over immediate user-facing functionality.

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

Community Trust & Token Economics

The AI16Z to ElizaOS token migration has sparked significant community frustration due to the sudden snapshot, supply increase, and declining token price, undermining confidence in the project's economic model at a crucial development juncture.

How should we address the growing community frustration regarding the token migration and price decline?

The migration from AI16Z to ElizaOS token has caused significant community frustration. Users expressed concerns about the sudden snapshot that caught many holders off-guard.
Token price has been declining despite broader crypto market strength. Supply increased from 6.6B to 11B tokens (~40% increase), with 13% immediately entering circulation and 27% on a 3-year unlock schedule.

1Increase utility by accelerating the launch of auto.fun and Babylon, creating immediate token demand.

Prioritizing product launches may strain technical resources but would provide tangible utility to justify the increased token supply.

2Implement a token buyback program using treasury funds to support price and demonstrate confidence in the ecosystem.

A buyback would provide immediate price support but depletes treasury resources that could otherwise fund development.

3Improve communication with comprehensive tokenomics education and regular treasury/development updates to restore trust.

Enhanced transparency may slow immediate price decline through improved sentiment but doesn't address fundamental utility concerns.

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

What tokenomics adjustments should be considered to align with our decentralization principles while supporting token value?

Q: How is it "decentralized"? A: Probably by ELIZAOS holding. (Omid Sa)
DorianD expressed skepticism about a 2026 bull run, suggesting 2028 as more likely, citing broader geopolitical trends affecting decentralized networks.

1Implement on-chain governance allowing token holders to vote on treasury allocations and feature prioritization.

True decentralization through governance would differentiate ElizaOS but may slow decision-making during this critical development phase.

2Establish protocol fee distribution where a percentage of auto.fun and platform usage fees flows directly to token stakers.

Creating a direct value accrual mechanism would strengthen token fundamentals but requires operational products.

3Develop a progressive decentralization roadmap with clear milestones tied to technical achievements and community growth.

A structured approach balances short-term development needs with long-term decentralization goals but requires ongoing management attention.

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

Product Delivery & Timeline Management

Multiple core products (ElizaOS Cloud, Babylon, Jeju) are behind communicated schedules, with the development team focused on infrastructure and technical debt rather than user-facing features, creating a potential misalignment with immediate community expectations.

How should we prioritize between technical infrastructure improvements and shipping user-visible products?

ElizaOS Cloud: Originally promised for November, still in development with no specific launch date
Large PR (#6213) submitted to clean up code quality issues, including type fixes, test additions, and removing unnecessary try/catch blocks

1Maintain focus on code quality and infrastructure, as this creates a sustainable foundation for future products.

Long-term technical health will be improved, but continued delays may further damage community confidence.

2Shift to a dual-track approach with separate teams for infrastructure and product delivery to ensure parallel progress.

This balances technical debt reduction with visible outputs but increases coordination overhead.

3Temporarily prioritize shipping minimum viable versions of promised products before returning to infrastructure work.

Quick wins boost community sentiment but may create technical debt that becomes harder to address later.

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

What should our communication strategy be regarding product timelines given the current development reality?

Q: What about ElizaOS cloud launch - it was supposed to launch by EOD November - we are in December? A: "We're busy working on it, I think devs will really like it" (Odilitime)
Q: When is Babylon launching? Already 275K registered and still no signs. A: "It's going really well - you saw it introduced about two weeks ago. If we had announced when it will be launching, you'd know about it" (Kenk)

1Adopt a "no public timelines" policy until features are nearly complete to prevent disappointment from missed deadlines.

Reduces short-term pressure but may create perception of slow development and lack of roadmap clarity.

2Implement transparent milestone tracking with regular public updates on progress and honest acknowledgment of delays.

Builds trust through transparency but requires admitting shortfalls and may temporarily impact sentiment.

3Shift to smaller, incremental releases with more achievable timelines rather than major product launches.

Creates steady progress perception but may dilute excitement around major feature completions.

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

Agent Architecture & Capability Limitations

Current agent infrastructure faces critical limitations in composability, uptime guarantees, and long-term accessibility that conflict with our mission of creating reliable 24/7 autonomous agents for auto.fun and other applications.

How should we address the architectural limitations of our current agent system compared to smart contract reliability?

Current agent system lacks composability
No guaranteed 24/7 uptime (unlike smart contracts)
Uncertain long-term accessibility of agents

1Develop an on-chain persistence layer for agent state with smart contract integration for critical functions.

Blockchain integration provides reliability guarantees but increases complexity and gas costs.

2Implement a distributed hosting model with redundancy and automatic failover across multiple cloud providers.

Improves uptime without blockchain costs but requires significant infrastructure investment.

3Create standardized agent interfaces and protocols that enable cross-deployment interoperability and state persistence.

Focuses on interoperability rather than specific hosting solutions, enabling diverse implementations.

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

What innovative agent capabilities should we prioritize to distinguish elizaOS in the competitive AI framework landscape?

Concept of an AI agent that monitors food consumption through fridge cameras and smart scales
Home automation technology for elizaOS has been developed by Neo
Discussion about alternative data formats (TOON and POML) vs. traditional formats like JSON/XML

1Prioritize multi-modal agent capabilities across text, vision, audio, and IoT device integration.

Broadens potential use cases but spreads development resources across multiple complex technologies.

2Focus on agent-to-agent collaboration protocols that enable emergent collective intelligence.

Creates a unique differentiator aligned with AGI vision but requires solving complex coordination problems.

3Develop specialized vertical solutions in financial trading, content creation, and home automation.

Targets proven market demand areas with immediate utility but may limit broader platform adoption.

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

Council Briefing

North Star & Strategic Context

Key Deliberations