Inside Operation Meteor: The Research Mandate for Global Market Discovery

1. First Team Action: Elect a Research Team Speaker

Before commencing research sprints and market clustering, the first official action of the nominated Research Team is to elect a Speaker from within the group.

Elected Speaker Responsibilities

Immediate Action · Day 1

1

Represent the Research Team

Serve as the unified point of contact with the Meteor Facilitator (Tyler Adams), the Neo Council, and ecosystem community channels.

2

Facilitate Internal Decision-Making

Coordinate internal alignment, run weekly research check-ins, resolve topic overlaps, and ensure decisions across the 7-member group are made smoothly and decisively.

3

Package & Submit Deliverables

Oversee the final quality review, validation, and formal submission of the 5–10 Market Opportunity Dossiers at the conclusion of the research sprint.

2. Introduction: What is Meteor?

Meteor is an open, structured Neo ecosystem initiative designed to assign market priority, align ecosystem capabilities, and establish unified strategic focus for Neo's next chapter of growth (2026–2031).

Key Process Stance

Not a "Winner-Take-All" Contest

Meteor assigns market priority and unified focus. Depending on council scoring, there may be one or multiple target opportunities selected for execution.

Iterative & Living Process

Designed to be continuous and repeatable—supporting new opportunity injection, periodic reweighting, and strategic focus shifts as markets evolve.

Structured Execution Phases

Phase 0 (Current) Global Opportunity Identification & Priority Scoring: Research Team packages 5–10 dossiers. Neo Council weights criteria and scores candidates.

Phase 1 Product Definition & Alignment Workshop: Turning prioritized opportunities into concrete product hypotheses and commercial models.

Phase 2 Roadmap, Prototype & Ecosystem Mobilization: Building, testing, and rallying developer teams around the execution roadmap.

3. Research Team Mission & Deliverable Mandate

As the Research Team, your mandate is straightforward: Deliver 5 to 10 rigorous, standardized, plain-language Market Opportunity Dossiers representing the most compelling 5-year blockchain market opportunities for Neo.

Nominated Research Group (7 Members + Facilitator)

Phase 0 Research Sprint

Tyler Adams (COZ Facilitator) Dylan (NNT) Lunar Strategy Malcolm Lerider (Ecosystem) John Wang (NGD) Jimmy Liao (R3E Network) Vitor Coelho (Neo Research) Ivan Poon (Switcheo Labs)

4. Operating Directives & Boundaries

To ensure fairness, rigor, and accessibility across human researchers and AI-assisted workflows, production must adhere strictly to these 6 core directives:

D1 No Cold-Start Assumptions

Standalone and plainly written so council and community members understand the core thesis in under 5 minutes without specialized background.

D2 Community as an Active Signal

Solicit and integrate community submissions alongside global market research, crediting builder contributions directly in dossiers.

D3 Comprehensive 16-Category Coverage

Every dossier must provide explicit, factual assessments across all 16 standardized council voting categories for transparent scoring.

D4 No Subjective Viability Gates

Do not pre-screen or eliminate candidate markets based on personal bias. All candidate markets meeting evidentiary rigor must be presented for Council voting.

D5 Strict Deduplication

Merge overlapping proposal areas (e.g., "AI Data Verification" and "Oracle Attestation") into a single cohesive, high-conviction thesis.

D6 Bound to 5–10 Final Deliverables

Target a crisp, diverse menu of 5 to 10 distinct opportunities to ensure Council evaluation remains thorough and unburdened by bloat.

5. Agentic & Human Production Workflow

Research and drafting follow a structured 3-stage pipeline:

Stage 1 Ingestion & Clustering

Ingestion, Clustering & Competitive Analysis

Scan community forums, GitHub discussions, Discord pitches, and industry reports across global trends (e.g. DePIN, Institutional Tokenization, On-Chain Identity/Compliance, AI Agent Tooling). Map candidate spaces against competing L1s/L2s and evaluate synergies across Neo N3, Neo X, SpoonOS, NeoFS, and native oracles.

Stage 2 Drafting & Structuring

Standardized Dossier Drafting

For each candidate market, produce a Markdown document adhering strictly to the Canonical Market Opportunity Dossier Schema, ensuring uniform sectioning, clear data points, and objective assessment.

Stage 3 QA & Peer Review

Plain-Language Validation & Quality Review

Ensure jargon is explained clearly, verify neutral tone and objective assessment across all 16 voting categories, and facilitate peer cross-review before final package submission.

6. Standard Market Opportunity Dossier Schema & Template

Each of the 5–10 market deliverables must be authored using standardized sections:

Canonical Dossier Schema Components

1. Executive Summary

30-second elevator pitch, core thesis, and primary value proposition.

2. Market Analysis & Overview

5-year industry outlook, buyer profiles, and primary unmet market needs.

3. Concrete Opportunity & Product Archetype

Wedge strategy, architectural fit (Neo N3, Neo X, NeoFS, SpoonOS), and competitive analysis.

4. Marketability & Token Dynamics

Structural token demand catalysts, revenue paths, and narrative clarity.

5. Ecosystem & Partner Landscape

Adjacent builder momentum, ecosystem multipliers, and strategic partner targets.

6. Key Risks & Dependencies

Legal, regulatory, trust, reputational, and technical execution vulnerabilities.

7. Category Assessment Matrix

Explicit, evidence-backed evaluation across all 16 standardized Council voting categories.

Canonical Market Opportunity Dossier Template (Markdown Specification):

MARKET____v0.1.md

Dossier Template

# Market Opportunity Dossier: [Market Title / Thesis Name]

**Dossier ID:** METEOR-MKT-[01..10]  
**Lead Researcher / Submitter:** [Name / Organization / Community Source]  
**Date:** [YYYY-MM-DD]  
**Status:** Candidate for Council Scoring (Phase 0)  

---

## 1. Executive Summary (The 30-Second Pitch)
* **What is this market?** [Plain-language 2-sentence explanation]
* **Why now (2026–2031)?** [Market timing & tailwinds]
* **The Neo Hook:** [Why Neo is uniquely positioned or advantaged]

---

## 2. Market Analysis & Overview
* **Market Landscape & 5-Year Outlook:** [Broad market structure, growth trends, and macro tailwinds]
* **Target Users, Buyers & Stakeholders:** [Who pays, who uses, who integrates?]
* **Core Problem & Unmet Needs:** [What is broken or missing today?]

---

## 3. Concrete Opportunity & Product Archetype for Neo
* **Opportunity Definition:** [The specific wedge and high-conviction opportunity for Neo]
* **Plausible Product Archetype:** [What would Neo actually build, host, or launch as an MVP?]
* **Architectural & Technical Fit:** [How does this leverage Neo L1 (N3), Neo X (MEV-resistant EVM sidechain), SpoonOS, native dBFT finality, native oracles, NeoFS, smart contracts, or toolchains?]
* **Competitive Market Analysis & Positioning:** [Detailed competitive mapping against competing L1s/L2s, specialized execution layers, and off-chain alternatives; where is the defensible wedge?]
* **Production MVP Asset Intensity:** [What capital, regulatory, partnership, or liquidity assets are needed before a truthful MVP exists?]

---

## 4. Marketability, Attention & Token Dynamics
* **Narrative & Hype Factor:** [Why will developers, users, and media care?]
* **Token Utility & Demand Plausibility:** [How does activity in this market create demand or utility for NEO/GAS without speculative promises?]

---

## 5. Ecosystem & Partner Landscape
* **Key Competitors / Precedents:** [Who else is doing this across L1s/L2s?]
* **Potential Anchor Partners / Projects:** [Who could Neo collaborate with or recruit?]
* **Community Input & Builder Adjacencies:** [Relevant ideas, feedback, or contribution points from ecosystem builders and community]

---

## 6. Key Risks, Unknowns & Dependencies
* **Top 3 Execution / Technical Risks:**
* **Regulatory / Compliance Considerations:**
* **Dependencies / External Prerequisites:**

---

## 7. Category Assessment Matrix (Council Scoring Reference)
*Detailed analytical context and evidence assessment across all 16 voting categories to inform Council scoring:*
1. **Market timing:** [Assessment of market readiness and 5-year growth trajectory]
2. **Real customer pain:** [Assessment of problem urgency and validation]
3. **Clear buyer:** [Assessment of buyer clarity, budget availability, and willingness to pay]
4. **Neo strategic fit:** [Assessment of alignment with Neo's brand, mission, and ecosystem identity]
5. **Technical leverage and architecture fit:** [Assessment of fit with dBFT, NeoFS, native oracles, smart contracts]
6. **Defensibility:** [Assessment of sustainable moat and resistance to commoditization]
7. **Plausible revenue and economic model:** [Assessment of economic sustainability and fee/revenue plausibility]
8. **Ecosystem catalyst:** [Assessment of multiplier effect on adjacent Neo liquidity and projects]
9. **Feasible execution:** [Assessment of implementation complexity against available capabilities]
10. **Manageable legal, trust, and reputation risk:** [Assessment of regulatory exposures and reputation risk]
11. **Learning velocity:** [Assessment of speed to test hypotheses and obtain customer feedback]
12. **Practical path to a real first product (MVP):** [Assessment of capital/licensing/asset hurdles before a live MVP]
13. **Strategic flexibility:** [Assessment of platform option value and pivot flexibility]
14. **Coherent narrative:** [Assessment of storytelling clarity for developers, investors, and media]
15. **Ecosystem builder momentum:** [Assessment of developer and creator appeal]
16. **Market attention, hype, and token demand:** [Assessment of narrative buzz and organic NEO/GAS demand mechanisms]

7. The 16 Evaluation Categories (Scoring Matrix Guide)

Every candidate dossier must provide explicit, factual context across all 16 standardized evaluation criteria weighted by the Council. Use this reference guide when authoring Section 7 of each dossier:

#	Category	Description (What It Tests)	Scoring Examples (Weak vs. Strong)
1	Right market timing (next 5 years)	Is this a good opportunity for Neo to pursue now, with a realistic chance to matter during the next five years (2026–2031)?	Weak (1) Market is fading, too early to support, or Neo arrives after the window has closed. Strong (10) Clear market opening now, with high relevance and growth sustained over the next 5 years.
2	Long-term staying power (10 years)	If the first version works, is the underlying need likely to stay useful, relevant, and adaptable for a decade?	Weak (1) Depends mainly on a short-lived trend, temporary incentive, or fleeting market cycle. Strong (10) Addresses a durable, foundational need that can evolve and expand for many years.
3	Strength of the problem	Does this solve a real problem that users or organizations care enough about to change behavior or spend budget?	Weak (1) Vague, minor, or mostly an internal ecosystem hope rather than a felt customer pain. Strong (10) Clear, painful, frequent, and important enough that customers actively seek an alternative.
4	Clear customer, buyer, and route to reach them	Do we know who uses it, who approves/pays for it, why they act now, and how Neo can practically reach them?	Weak (1) Users, buyers, and GTM routes are vague; relies on passive hope that someone will adopt it. Strong (10) Target user group, decision maker/payer, trigger to act, and distribution path are crisp.
5	Why Neo should do this	Does this direction leverage Neo's distinctive strengths (dBFT, NeoFS, Oracles, Neo X, SpoonOS) and reinforce Neo's position?	Weak (1) Any generic chain could do it identically; gives Neo no distinctive advantage or brand lift. Strong (10) Directly harnesses Neo's technical, governance, and brand strengths to create a clear home.
6	Ability to stand out and stay ahead	Can this become meaningfully differentiated and defensible rather than easy to commoditize or copy by L1s/L2s?	Weak (1) Looks like existing crowded offers with no moat; easily replicated or outspent. Strong (10) Clear structural reason to choose Neo; built-in stickiness and sustainable differentiation.
7	Believable way to make money	Is there an early, credible path to revenue, sustainable fee capture, or direct economic value creation?	Weak (1) No identifiable payer; relies on wishful future monetization or indefinite subsidies. Strong (10) Clear paying customer, high-value outcome, and believable ongoing value capture.
8	Ability to bring useful activity to Neo	Will this bring real recurring builders, users, partners, applications, and liquidity into the Neo ecosystem?	Weak (1) Isolated one-off project or announcement with little lasting ecosystem spillover. Strong (10) Creates repeatable incentives for outside developers, capital, and users to engage with Neo.
9	Speed to a useful first proof	Can a focused, lean team deliver something credible to test, show, or sell quickly without a multi-year program?	Weak (1) First proof takes years, requires a massive team, or depends on heavy unresolved dependencies. Strong (10) Small team can deliver a functional prototype, pilot, or initial validation within months.
10	Practical path to a real first product (MVP)	How realistic is it to obtain required non-code assets, licenses, capital, counterparties, liquidity, or audits for a real MVP?	Weak (1) Needs heavy external licenses, massive liquidity, or complex regulatory assets before a real MVP can exist. Strong (10) Required assets and conditions are accessible; normal product execution delivers a truthful MVP.
11	Can Neo build and operate it well?	Can the ecosystem realistically build, secure, operate, and maintain this with available or obtainable technical talent?	Weak (1) Relies on unproven tech, fragile architecture, unmanageable security, or implausible operations. Strong (10) Practical architecture, manageable security/ops, and credible engineering capability in place.
12	Manageable legal, trust, and reputation risk	Can Neo pursue this direction safely without severe compliance hazards or unmanageable reputational exposure?	Weak (1) Severe regulatory/legal hazards or forces promises the ecosystem cannot safely keep. Strong (10) Risks are well-understood, proportionate, and safely manageable through clean operating design.
13	Ability to learn quickly	Can Phase 1/2 rapidly test critical assumptions through user conversations, sales feedback, or small staged pilots?	Weak (1) Critical assumptions cannot be validated until after massive capital expenditure or long delays. Strong (10) Key hypotheses can be pressure-tested rapidly with real users, partners, and lightweight tests.
14	Useful future options	Does this direction open valuable strategic options and adjacent expansion paths even if the initial wedge pivots?	Weak (1) Narrow dead-end bet; if the initial concept misses, little reusable capability or learning remains. Strong (10) Builds reusable infrastructure, relationships, and market footholds that support multiple future paths.
15	A clear Neo story	Can the direction be explained simply, crisply, and convincingly as a logical Neo foothold to builders, investors, and users?	Weak (1) Feels random, confusing, or disconnected from what Neo stands for and is building toward. Strong (10) Inspiring, cohesive narrative that clearly articulates Neo's strategic rationale and role.
16	Market attention, hype, and token demand	Can this credibly generate organic attention, narrative pull, and structural demand for NEO and GAS?	Weak (1) Low narrative pull; depends on artificial promotion with no real connection to token utility. Strong (10) High-interest narrative with clear mechanics driving genuine ecosystem excitement and token demand.

8. Concrete Benchmark Dossier: Verifiable AI Agent Settlement

The working packet includes a production-grade benchmark dossier (METEOR-MKT-01: Verifiable Autonomous AI Agent Settlement & Storage) illustrating how to leverage Neo X for MEV-resistant execution, NeoFS for persistent agent memory/weights, and native oracles for off-chain state attestation.

Benchmark Reference Dossier METEOR-MKT-01

Verifiable Autonomous AI Agent Settlement & Memory Layer

Demonstrates the standard depth and structure expected across all candidate submissions—spanning 5-year TAM projections, buyer persona analysis, Neo platform technical leverage (Neo X + NeoFS + Oracles), and full 16-category scoring rationale.

Neo X (MEV Protection) NeoFS (Persistent Weights) dBFT Finality

Full Benchmark Dossier Implementation Example (METEOR-MKT-01):

METEOR-MKT-01__ai_agent_settlement.md

Benchmark Dossier

# Market Opportunity Dossier: Verifiable Autonomous AI Agent Settlement & Storage

**Dossier ID:** METEOR-MKT-01  
**Lead Researcher / Submitter:** Research Team (Synthesized from Community Submissions & Global Market Scan)  
**Date:** 2026-09-10  
**Status:** Candidate for Council Scoring (Phase 0)  

---

## 1. Executive Summary (The 30-Second Pitch)
* **What is this market?** An infrastructure and coordination layer where autonomous AI agents can trustlessly hire each other, exchange API services, verify intermediate computational artifacts, and settle micro-transactions with instant finality.
* **Why now (2026–2031)?** Generative AI has transitioned from prompt-response interfaces to multi-agent autonomous swarms; these off-chain agents lack native financial rails, identity primitives, and tamper-proof shared storage to coordinate across organizations without centralized API gateways.
* **The Neo Hook:** Neo offers a uniquely comprehensive native stack: **Neo X** provides MEV-resistant, high-throughput EVM execution for high-frequency agent settlement; **NeoFS** provides native, verifiable decentralized object storage for multi-modal agent memory and model weights; and **native oracles** provide trusted off-chain state attestation without external middleware dependencies.

---

## 2. Market Analysis & Overview
* **Market Landscape & 5-Year Outlook:** The AI agent economy is projected to exceed billions of daily machine-to-machine interactions by 2030. Today, agent frameworks (e.g., LangChain, AutoGen, CrewAI) rely on centralized cloud services and fiat payment rails (e.g., Stripe) that suffer from high minimum transaction fees, account freezing risks, and lack of verifiable audit trails.
* **Target Users, Buyers & Stakeholders:** Autonomous AI agent developers, enterprise data providers, compute networks, decentralized AI agent protocol developers, and automated DeFi arbitrage/yield bots.
* **Core Problem & Unmet Needs:**
  1. *Payment Friction:* Traditional payment rails cannot handle programmatic sub-cent micro-settlements across non-human autonomous identities.
  2. *State & Memory Verification:* Agents lack verifiable, censorship-resistant shared memory to store execution traces, prompt graphs, and inference proofs across sessions.
  3. *MEV Exploitation:* Financial transactions submitted by automated trading/arbitrage agents on standard public blockchains are routinely frontrun and sandwiched by MEV searchers.

---

## 3. Concrete Opportunity & Product Archetype for Neo
* **Opportunity Definition:** Establish Neo (via Neo X and NeoFS) as the premier settlement and verifiable memory hub for decentralized AI agent swarms.
* **Plausible Product Archetype:** **Neo AgentHub** — A lightweight developer SDK and smart contract framework enabling:
  1. Instant programmatic wallet creation and role-based access control for AI agents on Neo X.
  2. Direct one-line integration for agents to persist and retrieve cryptographically signed execution traces to NeoFS.
  3. An MEV-shielded micro-payment escrow and billing registry settled in GAS.
* **Architectural & Technical Fit:**
  * **Neo X (EVM Sidechain):** Enjoys toxic MEV resistance (protecting autonomous trading and procurement agents) and high TPS for micro-payments.
  * **NeoFS:** Native decentralized storage provides high-throughput, low-cost persistence for model weights, context windows, and execution audit trails without IPFS pinning services.
  * **Native Oracles & SpoonOS:** Directly bridges external Web2 LLM API responses and state proofs into on-chain validation logic.
  * **Dual-Token Model:** Predictable, low-cost GAS consumption allows agent developers to forecast operating expenses accurately.
* **Competitive Market Analysis & Positioning:**
  * *Versus Base/Arbitrum:* Lacks native decentralized storage (must bolt on external IPFS/Arweave) and suffers from significant MEV extraction on public mempools.
  * *Versus Solana:* High throughput, but lacks MEV protection for agent transactions, has no native storage layer, and suffers from state bloating under high agent telemetry.
  * *Versus Filecoin/Bittensor:* Bittensor focuses on distributed model training/incentivization; Filecoin focuses on cold archiving. Neo's wedge is **operational coordination + instant settlement + active object memory**.
* **Production MVP Asset Intensity:** Low to Medium. Requires software engineering (SDK, smart contract escrow contracts, documentation, and agent framework plugins) and developer adoption grants. Does not require capital-intensive real-world asset legal wrappers, banking charters, or centralized custodian relationships.

---

## 4. Marketability, Attention & Token Dynamics
* **Narrative & Hype Factor:** Sits directly at the intersection of AI Agent autonomy and Web3 infrastructure. Highly attractive to Web3 venture capital, AI hackathons, and developer communities looking for real utility beyond speculative meme coins.
* **Token Utility & Demand Plausibility:** Every agent interaction, memory write to NeoFS, and cross-agent escrow settlement generates direct, non-speculative demand for GAS as network gas and storage collateral. NEO governance directly configures storage/settlement economic parameters.

---

## 5. Ecosystem & Partner Landscape
* **Key Competitors / Precedents:** Virtuals Protocol, Fetch.ai/ASI, Autonolas (Olas), Akash Network.
* **Potential Anchor Partners / Projects:** Open-source AI agent tooling communities (LangChain, CrewAI), Web3 compute providers, decentralized AI inference projects, and automated DeFi market makers.
* **Community Input & Builder Adjacencies:** Leverages existing community tooling from COZ (Mamba, Neon), R3E Network (FaaS/Agent orchestration), Neo Research, and NeoFS storage node operators.

---

## 6. Key Risks, Unknowns & Dependencies
* **Top 3 Execution / Technical Risks:**
  1. Developer toolchain adoption friction if agent SDKs are difficult to integrate into standard Python/TypeScript AI workflows.
  2. Ensuring NeoFS read/write latencies meet the real-time response requirements of conversational agent swarms.
  3. Rate of AI agent framework evolution requiring rapid adaptation of contract interfaces.
* **Regulatory / Compliance Considerations:** Low regulatory exposure compared to RWA/securities tokenization. Primarily technical compute and data transmission infrastructure.
* **Dependencies / External Prerequisites:** Robust Neo X RPC infrastructure, seamless NeoFS S3-compatible gateway availability, and developer documentation targeting mainstream AI engineers.

---

## 7. Category Assessment Matrix (Council Scoring Reference)
1. **Market timing:** Strong tailwinds; multi-agent systems are expanding exponentially in 2026 with no dominant Web3 settlement standard established.
2. **Real customer pain:** High; AI developers currently face severe payment gateway account bans, high fees, and lack of verifiable persistence.
3. **Clear buyer:** High; AI agent developers, data monetization platforms, and AI startup teams with existing cloud infrastructure budgets.
4. **Neo strategic fit:** Outstanding; directly leverages Neo's foundational identity as the "Smart Economy" platform uniting compute, storage, and assets.
5. **Technical leverage and architecture fit:** Very High; perfectly combines Neo X (MEV-protected execution), NeoFS (verifiable storage), and native oracles.
6. **Defensibility:** Moderate to High; once agent swarms establish identity, reputation, and memory history on NeoFS/Neo X, switching costs become high.
7. **Plausible revenue and economic model:** Clear; transaction fees, storage fees, and escrow protocol fees settled organically in GAS.
8. **Ecosystem catalyst:** High; brings net-new machine transactions, automated liquidity management to Neo X DeFi, and increased capacity utilization to NeoFS.
9. **Feasible execution:** High; core infrastructure (Neo X, NeoFS, Oracles) already exists; primary work is developer-facing SDKs, contracts, and integrations.
10. **Manageable legal, trust, and reputation risk:** Very Low; pure open-source developer tooling and infrastructure with minimal regulatory exposure.
11. **Learning velocity:** High; lightweight developer SDKs and hackathon challenges allow rapid testing and iteration cycles within weeks.
12. **Practical path to a real first product (MVP):** High; an end-to-end working prototype (Agent micro-escrow + NeoFS memory plugin) can be delivered in 6–8 weeks.
13. **Strategic flexibility:** High; the underlying micro-payment and storage primitives easily generalize to IoT, DePIN, and gaming use cases.
14. **Coherent narrative:** Excellent; "The Settlement and Memory Layer for the AI Agent Economy" is immediately clear to builders, investors, and media.
15. **Ecosystem builder momentum:** High; taps into the fastest-growing developer segment globally (AI engineers exploring Web3 primitives).
16. **Market attention, hype, and token demand:** High; AI + Crypto is a tier-1 narrative driving direct, organic transaction and storage demand for GAS.

9. Master Timeline & Deliverable Ownership

Below is the complete end-to-end timeline for Meteor Phase 0 and the transition into Phase 1/2:

Active Stakeholders: Research Team Council Community Builders / Devs

1

Sept 14, 2026

Research Team Council Community

Initiative Kickoff & Public Framework Disclosure

Public release of the Operation Meteor framework across the ecosystem. The 16 evaluation categories, research methodology, and governance rules are opened for ecosystem review.

Who is Active

Research Team, Council Members, Ecosystem Foundation, and Community.

Key Deliverable

Phase 0 charter, category definitions, and public participation channels open.

Community Action Window

Review the 16 evaluation criteria, join ecosystem discussions, and prepare candidate market problem statements.

2

Sept 14 – Sept 25, 2026

Council Community

Vote 1: Council Category Strategic Weighting

The 21-seat Neo Council engages in a 2-week voting window to assign relative strategic weights across the 16 decision categories, establishing the mathematical lens used for scoring candidate markets.

Who is Active

Neo Council (21 voting seats), Community Lobbying.

Key Deliverable

Mathematically weighted 16-category evaluation matrix.

Community Action Window

Directly lobby Council members across Discord, X, and governance forums on category tradeoffs (e.g. Near-term Speed vs. Long-term Moats, Token Utility vs. Technical Prestige).

3

Mid-September 2026

Council Builders / Devs

Core & Tooling Backlog Prioritization

Parallel 2-week Council voting session ranking technical backlog items, core infrastructure enhancements, and developer tooling priorities to ensure engine readiness for prioritized workloads.

Who is Active

Core Engineering Leads, Neo Council.

Key Deliverable

Prioritized technical backlog for core developer teams.

Community Action Window

Share feedback on developer tool bottlenecks (SDKs, indexing, compiler features, NeoFS tooling) in community developer channels.

4

Sept 14 – Mid-Oct, 2026

Research Team Builders / Devs Community

Field Intelligence Sourcing & Research Sprints

The nominated Research Team investigates global macro trends, interviews builders, aggregates community submissions, and clusters market opportunities into rigorous standardized templates.

Who is Active

Nominated Research Team (NNT, Lunar Strategy, NGD, R3E, Neo Research, Switcheo Labs, Ecosystem Leads), Global Builders.

Key Deliverable

Synthesized market data, builder interviews, and draft opportunity dossiers.

Community Action Window

Submit concrete market problems, developer friction points, and customer pain points to Research Team members on GitHub Discussions, Discord, and X.

5

Mid-October 2026

Research Team Community

Publication of 5–10 Market Opportunity Dossiers

Formal public release of 5 to 10 standardized Market Opportunity Dossiers detailing problem severity, target buyers, Neo technical leverage, commercial defensibility, unit economics, and required MVP assets.

Who is Active

Research Team, Ecosystem Observers, Community.

Key Deliverable

5–10 standardized dossiers published openly for ecosystem audit.

Community Action Window

Read, debate, and pressure-test published dossiers in public AMAs, Reddit threads, and Discord stages before Council scoring begins.

6

Mid-October 2026

Council Community

Vote 2 Kickoff: Independent Candidate Opportunity Scoring

2-week voting window where all 21 Council members independently score each published Market Opportunity Dossier across the 16 weighted evaluation categories (1–10 scale per criterion).

Who is Active

Neo Council (21 voting seats).

Key Deliverable

Round 1 confidential scoring ballot submissions.

Community Action Window

Highlight dossier strengths, hidden operational risks, or technical synergies to Council representatives during their initial scoring window.

7

Late October 2026

Council

Vote 2: Delphi Consensus & Outlier Review

1-week structured Delphi review cycle. Anonymized scoring distributions, standard deviations, and polarized outlier ratings are shared among Council members to deliberate differing perspectives.

Who is Active

Neo Council, Process Facilitators.

Key Deliverable

Outlier variance report and clarified evaluation notes.

Community Action Window

Observe public governance summaries detailing major points of debate and strategic alignment.

8

Early November 2026

Council Community

Vote 2: Final Ballot Adjustment & Public Results

1-week final adjustment window where Council members may update ballots based on Delphi insights. Scores are finalized, weighted, and the consensus opportunity rankings are published openly with full rationale.

Who is Active

Neo Council, Community, Global Press.

Key Deliverable

Finalized consensus rankings and public governance report.

Community Action Window

Review finalized rankings, score breakdowns, and approved opportunity priorities across official ecosystem channels.

9

November 2026+

Builders / Devs Community

Product Definition Workshops & Roadmap Handoff

Prioritized market opportunities enter Phase 1 Product Definition Workshops. Technical architects, product designers, and ecosystem leads author execution roadmaps, resource allocations, and grant programs.

Who is Active

Product Teams, Core Developers, Grant Committees, Ecosystem Builders.

Key Deliverable

Technical specifications, architecture RFCs, and funded project milestones.

Community Action Window

Apply for targeted builder grants, join working group hackathons, and begin building applications on the prioritized product roadmaps.

10

Ongoing Cycles (2026–2031)

Research Team Council Community

Iterative Review & Continuous Opportunity Injection

Operation Meteor is a recurring, living governance mechanism. Market shifts trigger periodic category re-weighting, new dossier research sprints, and iterative priority updates over the 2026–2031 horizon.

Who is Active

All Neo Ecosystem Stakeholders.

Key Deliverable

Continuous ecosystem alignment and strategic agility.

Community Action Window

Continuously submit emerging market trends, new DePIN/AI/RWA hardware protocols, and competitive landscape feedback.

10. Research Team Deliverable Checklist

To ensure absolute clarity on your team's obligations, please follow this deliverable checklist:

Deliverable 1 · Day 1 Sept 14, 2026

Elect & Announce Speaker

Nominated Research Team elects an official Speaker to represent the group across council and ecosystem communications.

Deliverable 2 · Continuous Sept 14 – Mid-Oct

Community Pitch Ingestion

Actively monitor, ingest, cluster, and evaluate market submissions and architecture pitches from community channels.

Deliverable 3 · Primary Mandate Mid-October 2026

5–10 Market Opportunity Dossiers

Deliver 5 to 10 completed, standardized dossiers adhering strictly to the schema and evaluated across all 16 voting categories.

Deliverable 4 · Consensus Support Late Oct – Nov 2026

Council Consensus & Handoff Support

Support Council Delphi review cycles, provide factual clarifications on scoring outliers, and assist Phase 1 workshop transitions.