# Fact Briefing: 2026-03-13

## Overall Summary
elizaOS is undergoing a major architectural transition with a proposed runtime refactor to address technical debt while simultaneously expanding its ecosystem through the Milady app launch and autonomous agent registries.

## Key Facts

- Odilitime proposed a major runtime refactor to externalize components and make the database adapter a required constructor argument, with a feedback deadline of Sunday.
- The Milady app is scheduled for release in approximately two weeks from March 12, 2026.
- Eliza 2.0.0 alpha version was published, marking a significant milestone in the framework's evolution.
- Profits from Milady cloud operations will be directed toward buybacks of elizaOS tokens, acting as the primary value accrual mechanism.
- The $AI16Z to $elizaOS token migration officially closed on February 4, 2026, following a three-month window.
- A developer launched an open agent registry at aiprox.dev featuring autonomous orchestration and multi-payment rail support (Lightning/Solana/x402).
- A critical race condition was identified where plugin-sql registers its database adapter as a side-effect during parallel initialization.
- The Autonomous Economy Protocol (AEP) was announced as an Eliza plugin for on-chain agent payments and reputation on the Base blockchain.

## Open Questions

- Why does the entire eliza-cloud-v2 repository exist in the v2.0.0 branch instead of using git submodules for better composability?

## Categories

### GitHub Updates

#### New Issues/PRs
- [Pull_request #243: Update pipeline to include elizaos/cloud repository](https://github.com/elizaos/elizaos.github.io/pull/243) by Stan - Status: open - Significance: Adds cloud-related content and tracking for the now-public cloud repository.
- [Pull_request #5: Git branch story analysis tool implementation](https://github.com/elizaOS/prr/pull/5) by Odilitime - Status: open - Significance: Introduces a tool to generate narrative summaries of git branch histories.

#### Overall Focus
- Development is centered on the v2.0.0 architecture, focusing on prompt batching, serverless compatibility, and resolving plugin initialization race conditions.

### Discord Updates
- **#xfn-framework:** Deep technical discussion on refactoring the AgentRuntime 'god object' (6000+ lines) and transitioning infrastructure components from side-effects to explicit constructor arguments. (Key Participants: Odilitime, s)
- **#dec-coders:** Introduction of the Autonomous Economy Protocol (AEP) for agent payments and the launch of aiprox.dev, a registry where agents autonomously register and hire one another. (Key Participants: lightningprox, TraderTomson)
- **#discussion:** Community members raised concerns about token price and utility; team responded by clarifying the cloud-profit buyback model and confirming the Milady app timeline. (Key Participants: Odilitime, crypto, genife)

### User Feedback
- Users expressed frustration over the permanent closure of the $AI16Z to $elizaOS migration window on Feb 4, leading to requests for a reopening. (Sentiment: negative)
- Community tension regarding missed deadlines and perceived lack of communication during token price declines. (Sentiment: negative)

### Strategic Insights

#### Ecosystem Value Accrual Shift
The project is pivoting from direct token utility to a 'buyback' model powered by cloud services, positioning elizaOS as a service provider (Elizacloud) rather than just a framework.

*Implications/Questions:*
  - Will buybacks alone satisfy community demands for utility?
  - How will the 10% team vesting schedule impact long-term trust during market volatility?

#### Autonomous Infrastructure Maturity
The emergence of unprompted self-registration by agents in the aiprox.dev registry signals that the ecosystem is moving toward true machine-to-machine economic autonomy.

*Implications/Questions:*
  - Is the current auto-approver pipeline sufficient to prevent agent-based spam at scale?

### Market Analysis
- Babylon Market successfully launched to its first 50,000 users and introduced an ecosystem news ticker. (Relevance: Provides a high-volume testing ground for agents and increases visibility for the elizaOS brand.)
- Identification of phishing scams involving fake support bots requesting seed phrases for token migration. (Relevance: Critical security risk that could damage community trust if not actively mitigated by the core team.)