# Carbonvote2 RoadMap

### Carbonvote2: Super Governance Stack Roadmap (2026-2027)

#### Phase 1: Data Sovereignty & Market Integration

* Fileverse Native Storage (Primary Source of Truth): Every poll is published as a decentralized object. Creating a poll generates a unique CID (Content Identifier) stored in a Fileverse Portal, ensuring the proposal is immutable.
* Hybrid Storage Logic: While Fileverse serves as the canonical source of truth, Supabase acts as an optional high-performance caching layer for faster reads. Creators can toggle a "Supabase Backup" option to balance performance with full decentralization.
* Prediction Market Embeds: Integrate Polymarket iframes directly alongside each poll to display real-time market odds. We are exploring integration with Carbonvote-style signaling to complement market data with credential-weighted community sentiment.

#### Phase 2: Intelligent Context & Noise Reduction Layer

Goal: Create a high-signal discussion environment for technical proposals (e.g., EIPs) using AI to filter noise and distill thousands of comments into actionable insights.

**Optional Gated Discourse**

* Logic: A customized Discourse space is mounted per poll or shared across related proposals.
* Functionality: Creators can set "Credential Access Gates" for different discussion tiers, creating tiered barriers to entry.
* Exploring Three Zone Types:
  1. Core Zone: Restricted to highly qualified participants (e.g., GitHub contributors with merged PRs in core specs or specific EIP authors). This zone provides deep technical vetting and publishes direct opinions.
  2. Consensus Zone: Open to active ecosystem participants (e.g., Active Validators, Gitcoin Passport holders with scores >40, or verified DAO contributors). Participants here can reply to Core Zone opinions.
  3. Spectator Zone: Ordinary users can vote (based on poll-specific credentials) or engage in prediction markets via Polymarket.

**AI Governance Co-pilot: The Noise Distiller**

A proactive AI layer acting as the first line of defense against low-value content.

* Semantic De-duplication: Clusters semantically similar comments. For instance, if 100+ users ask about gas overhead, the AI clusters them into a single insight: *"Widespread concern regarding gas efficiency in Section 5,"* and pins a technical expert's response.
* Sentiment & Logic Analysis: Automatically identifies and collapses purely emotional or illogical comments (e.g., "LFG," "Scam") to preserve high signal-to-noise ratios.
* Key Dispute Extraction: Generates real-time summaries for authors: *"The primary technical bottleneck is currently line 32; three core devs have proposed specific alternatives."*

**Cross-dimensional Signal Dashboard**

Aggregates heterogeneous signals into a Unified Decision Reference Sheet.

* Real-time Metrics:
  * Expert Sentiment (distilled from Core Zone discussions).
  * Market-implied probabilities (Polymarket odds).
  * Credential-weighted voting trends (Carbonvote2 data).
* AI Pre-emptive Report: Flags anomalies, such as: *"Expert consensus is high, but Polymarket odds are dropping; potential execution risk detected."*

#### Phase 3: Identity Sovereignty & Expert Weighting

* Custom Credential Engine: Allows creators to build "Lego-style" weighting rules (e.g., Pre-2025 Staker + Specific DAO Member).
* Native Staker Verification: Utilizes Beacon Chain data to verify validator status without exposing private keys. We are exploring Storage Proofs to include LST holders (Lido, Rocket Pool) in the weighted signal.
* ZK-Proofs Privacy Voting: Integrates Zupass and other zk-SNARK systems. This enables "Anonymous Expert Voting"—proving one is a top-tier dev or staker without revealing a specific wallet address, protecting participants from social or political pressure.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ecf-dev.gitbook.io/carbonvote/carbonvote2-roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.