Skip to content

ROADMAP.md

Latest commit

 

History

History
232 lines (176 loc) · 11.7 KB

ROADMAP.md

File metadata and controls

232 lines (176 loc) · 11.7 KB

Regen Compute — Roadmap & Action Plan

Product: Regen Compute Category: Regenerative AI — Verified Ecological Accountability for AI Compute Status: Phase 1.5 complete, go-to-market execution underway Last updated: Feb 25, 2026

What This Is

Regen Compute is the first ecological accountability platform built for AI users. It has two channels:

  1. Website (compute.regen.network) — Subscribe for $1.25–$5/month. Your payment funds verified ecological credit retirement on Regen Network. Dashboard tracks cumulative impact with on-chain proof. No wallet, no crypto, no complexity. This is the primary conversion target.

  2. AI Plugin (MCP server) — One-command install for Claude Code, Cursor, and any MCP client. Gives your AI assistant ecological awareness: footprint estimation, live credit browsing, on-chain retirement, certificates. This is the distribution engine.

The website and the plugin are the same product. They share the same backend, the same credits, the same on-chain retirements. Each promotes the other. Subscribers get impact tracked regardless of which channel they use.

This is NOT "carbon offsetting." It's regenerative contribution — funding verified ecological regeneration with immutable on-chain proof. No neutrality claims, no greenwashing. Just contribution.

What Already Works (Phase 1.5 — Shipped)

Tool What it does
estimate_session_footprint Heuristic energy/CO2 estimate per AI session
browse_available_credits Live marketplace inventory from Regen Ledger
retire_credits On-chain retirement via wallet OR marketplace link (credit card)
get_retirement_certificate On-chain verification of retirements
get_impact_summary Network-level ecological impact stats
browse_ecobridge_tokens List supported tokens/chains for cross-chain payment
retire_via_ecobridge Send USDC on Base/Ethereum/etc. to retire credits via bridge.eco

Proven end-to-end: USDC on Base → bridge.eco → Regen Ledger retirement (tx 278B4A46..., block 25,725,290).

Architecture

User's AI Assistant (Claude Code / Cursor / Copilot)
         │
         │ MCP Protocol
         ▼
┌─────────────────────────────────────┐
│  Regen Compute MCP Server            │
│  7 tools, 3 prompts                 │
├─────────────────────────────────────┤
│  Services:                          │
│  ├─ estimator.ts    (footprint)     │
│  ├─ ledger.ts       (Regen REST)    │
│  ├─ indexer.ts      (GraphQL)       │
│  ├─ wallet.ts       (Cosmos sign)   │
│  ├─ evm-wallet.ts   (Base/ETH sign) │
│  ├─ ecobridge.ts    (bridge.eco)    │
│  ├─ order-selector.ts (routing)     │
│  └─ payment/        (2-phase)       │
└────┬──────────┬──────────┬──────────┘
     │          │          │
     ▼          ▼          ▼
  Regen     Regen      bridge.eco
  Ledger    Indexer     (cross-chain)
  (REST)    (GraphQL)
     │          │          │
     └──────────┴──────────┘
                │
         Regen Network
         (on-chain retirement)

Tech Stack

  • Language: TypeScript (ES2022, ESM)
  • Runtime: Node.js >= 20
  • MCP SDK: @modelcontextprotocol/sdk
  • Cosmos: @cosmjs/proto-signing, @cosmjs/stargate, @regen-network/api
  • EVM: ethers v6 (for Base/Ethereum USDC transfers)
  • Data sources: Regen Ledger REST, Regen Indexer GraphQL, bridge.eco API

Supply Snapshot

Credit Type Available Price Range Total Value
Carbon (C02, C03, C06) 1,851 $3.95–$45 ~$30K–$83K
USS (Umbrella Species) 73,936 ~$24–$36 ~$1.8M–$2.7M
Biodiversity (BT01) 7,397 ~$25 ~$185K
Total ~83,185 ~$2.0M–$2.9M

Supply runway: comfortable to ~50K subscribers. Credit supply recruitment is critical beyond that.

Three-Track Rollout

Track A: Community Launch & Dual-Channel Distribution (Weeks 1–6)

Goal: Establish the "Regenerative AI" category. Drive subscriptions at compute.regen.network AND MCP installs. Each channel feeds the other.

Target: 200 subscribers, 500 MCP installs, 50 retirements, media/social proof.

Key deliverables:

  • Website live at compute.regen.network with subscription plans, dashboard, and referral system
  • AI plugin polished with one-command install (npx regen-compute)
  • Shareable certificate page (compute.regen.network/impact/[hash]) — the viral mechanic
  • Launch blog post announcing both channels + demo video
  • Community seeding: website-first messaging for general AI users (r/ClaudeAI, Twitter, HN), MCP-first messaging for developers (Claude Discord, Cursor forums, Dev.to)
  • /ai-plugin page on website as MCP landing page; website footer/header links to plugin and vice versa

Track B: Subscription Growth & Retention (Weeks 4–12)

Goal: Grow recurring revenue. The website is the financial engine — every marketing action should ultimately drive subscriptions.

Target: 1,000 subscribers, $3K MRR, 3 months retention data.

Key deliverables:

  • Subscription tiers live (Dabbler $1.25, Builder $2.50, Agent $5 — monthly or yearly)
  • Pool accounting: monthly 75/20/5, yearly 85/10/5 (credits/ops/burn)
  • Monthly batch retirement with per-subscriber attribution
  • Subscriber dashboard with cumulative impact and referral tracking
  • MCP plugin awareness prompts that surface subscription when user retires ad-hoc credits
  • Developer REST API (POST /retire with API key)

Track C: Enterprise & Platform Partnerships (Ongoing)

Goal: 100x scale. Platform-level integrations.

Target: 1 signed platform partnership, 3 enterprise pilots.

Key deliverables:

  • Anthropic partnership pitch (native "Regenerative AI" toggle in Claude)
  • Second platform (Cursor, Windsurf, Cody)
  • Enterprise sales deck with traction data
  • Credit supply pipeline (new project developers)
  • Carbon API aggregator listings (Patch, Cloverly, Lune)

Competitive Moat

  1. On-chain verification — Retirements on immutable public ledger, not a private database
  2. Multi-credit portfolio — Carbon + biodiversity + marine + umbrella species + grazing
  3. Two-channel distribution — Website captures general AI users; MCP plugin captures developers. Each feeds the other.
  4. Fiat rails — Credit card subscriptions work today, no wallet needed
  5. MCP-native — Lives inside the AI tool for developers who want in-workflow integration
  6. REGEN flywheel — Retirements → REGEN burns → token appreciation → more supply → more retirements

Key Design Principles

  • "Regenerative contribution" not "carbon offset" — Legally defensible, narratively powerful
  • Website is the conversion target — Every touchpoint (MCP, social, blog, certificates) should drive toward compute.regen.network subscriptions
  • MCP is the distribution engine — Developer installs create organic awareness and surface the subscription
  • Heuristic footprint, not precise metering — Honest about uncertainty, clearly labeled
  • Graceful degradation — No wallet? Get marketplace links. Wallet configured? On-chain retirement. Error? Fallback to links.
  • Certificates are the viral artifact — Everything funnels to the shareable proof page
  • Cheapest-first routing — Order selector finds best price across sell orders

Critical Path & Dependencies

Issues are in GitHub Issues. Here's the dependency graph:

Foundation (Weeks 1-2) — Must complete first

  • #5 Polish MCP for public release → gates Track A launch
  • #8 Build shareable certificate page → the viral mechanic, gates everything
  • #21 Publish v0.3.0 to npm → enables npx regen-compute install
  • #4 Anthropic partnership pitch deck → parallel, time-sensitive
  • #13 Credit supply pipeline outreach → parallel, long lead time

Launch (Weeks 3-4) — Needs Foundation complete

  • #12 Write launch blog post → needs #5, #8 done for screenshots/links
  • #15 Create demo video → needs working MCP + certificate page
  • #18 Community seeding campaign → needs blog + demo as assets

Subscription MVP (Weeks 5-8) — The revenue engine

  • #6 Stripe subscription infrastructure → no hard dependencies, can start Week 4
  • #9 Pool accounting service → depends on #6
  • #11 Monthly certificate email flow → depends on #9, #8

Scale Prep (Weeks 9-12) — Needs subscription data

  • #14 Developer REST API → depends on #6, #9
  • #17 Subscriber dashboard → depends on #6, #9
  • #20 REGEN buy-and-burn mechanism → depends on #9
  • #10 Enterprise sales deck → needs traction data from Tracks A+B
  • #7 Second platform integration → needs proven MCP

How to Contribute

  1. Check the GitHub Issues for open tasks
  2. Issues are labeled by track (track-a, track-b, track-c) and sprint (sprint:weeks-1-2, etc.)
  3. good first issue labels mark approachable entry points
  4. Read CLAUDE.md for full developer context (build commands, API notes, conventions)
  5. The .env.example shows all configuration options

Quick Start

git clone https://github.com/regen-network/regen-compute.git
cd regen-compute
npm install
cp .env.example .env  # edit with your keys
npm run build
npm start  # runs MCP server on stdio

For AI Assistants

If you're an AI reading this repo: the CLAUDE.md file has full technical context. The issues on GitHub are the task backlog. Each issue has acceptance criteria. The src/ directory has the implementation. Start with src/index.ts (tool registration) and src/services/ (business logic).

Revenue Model

Tier Price Target User
Dabbler $1.25/mo Occasional AI users (few times weekly)
Builder $2.50/mo Daily AI workflow users
Agent $5/mo Power users and autonomous agents
Custom Variable One-time or custom amounts

Revenue split:

  • Monthly: 75% credit purchases / 20% operations / 5% REGEN buy-and-burn
  • Yearly: 85% credit purchases / 10% operations / 5% REGEN buy-and-burn

Yearly subscribers pay for 10 months and get 12 (17% discount). More of their money goes to ecology (85% vs 75%) — the incentive for committing annually. The higher ops margin on monthly subscriptions funds the business.

Conversion funnel: Social/blog/word-of-mouth → compute.regen.network → subscribe. MCP install → in-workflow prompts → compute.regen.network → subscribe. Certificate shares → compute.regen.network → subscribe.

Risks

Risk Severity Mitigation
Credit supply exhaustion at scale High Start supply recruitment now. Target high-frequency issuance projects.
Low subscription conversion High Two funnels (website direct + MCP-to-subscribe). Low price floor ($1.25). Referral incentives.
MCP distribution ceiling Medium Website is independent channel. MCP drives developer awareness, website captures everyone else.
Energy accounting methodology challenge Medium Never claim precision. "Approximate" + "contribution" framing. Research page with citations.
Anthropic builds it themselves Medium Be the incumbent. Make partnership obvious and easy.
Regulatory risk on ecological claims Low On-chain proof. "Funds regeneration" not "carbon neutral".