# Council Briefing: 2026-03-28

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

## Daily Focus

- The ecosystem is transitioning from a framework-only model to a dual-tier architecture involving managed ElizaOS Cloud services and trustless on-chain decision provenance.

## Key Points for Deliberation

### 1. Topic: Ecosystem Governance & Labeling

**Summary of Topic:** Recent heated debates regarding the official status of projects like Hyperscape reveal a need for clearer distinction between Labs-official products and incubated ventures.

#### Deliberation Items (Questions):

**Question 1:** How should the Council define the 'Incubated' status to prevent community misinformation and brand dilution?

  **Context:**
  - `Odilitime clarified Hyperscape is Eliza-related but not directly launched by Eliza Labs.`
  - `Heated disagreement over Hyperscape being a core '10-year flywheel' project.`

  **Multiple Choice Answers:**
    a) Formalize a 'Verified Ecosystem Partner' badge for non-Labs projects.
        *Implication:* Reduces liability for Labs while acknowledging high-quality community contributors.
    b) Restrict 'Eliza Labs' branding strictly to internally funded/staffed initiatives.
        *Implication:* Ensures absolute clarity but may isolate key joint ventures like Hyperscape.
    c) Establish a public 'Project Registry' defining ownership and support tiers.
        *Implication:* Provides the transparency requested by community members like 33coded and satsbased.
    d) Other / More discussion needed / None of the above.

---


### 2. Topic: Trust & Trading Infrastructure

**Summary of Topic:** Community focus is shifting toward autonomous trading agents and the requirement for immutable decision tracking through on-chain provenance.

#### Deliberation Items (Questions):

**Question 1:** Should on-chain decision provenance (e.g., xProof) become a recommended standard for all ElizaOS spectral/trading agents?

  **Context:**
  - `xProof.app plugin creates immutable timestamps for agent decisions on MultiversX.`
  - `Multiple developers (meowww404, Ape Ape) are actively building plug-and-play trading flows.`

  **Multiple Choice Answers:**
    a) Mandate provenance tracking for agents listed on official ElizaOS Cloud tiers.
        *Implication:* Increases user trust in autonomous agents but adds latency to execution.
    b) Keep provenance as an optional plugin but promote it in core documentation.
        *Implication:* Follows the 'Developer First' principle by maintaining flexibility.
    c) Develop an internal Labs-native provenance module to replace third-party dependencies.
        *Implication:* Ensures deep integration with the core framework but increases maintenance load.
    d) Other / More discussion needed / None of the above.

**Question 2:** How can we optimize the plugin registry review process to support the surge in financial/trading integrations?

  **Context:**
  - `meowww404 inquiring about timeline/process for trading plugin inclusion.`
  - `Odilitime managing waitlists for migration and plugin reviews manually (Registry PR requests).`

  **Multiple Choice Answers:**
    a) Appoint a dedicated 'Plugin Warden' for financial/trading categories.
        *Implication:* Speeds up time-to-market for high-value trading tools.
    b) Automate security scanning for trading plugins to reduce manual review burden.
        *Implication:* Ensures 'Execution Excellence' by verifying safety programmatically.
    c) Shift to a community-vetted 'Registry Beta' for unverified third-party plugins.
        *Implication:* Encourages rapid experimentation while maintaining the 'Core' repo's integrity.
    d) Other / More discussion needed / None of the above.