# Roadmap

Powering the Angel Twin Ecosystem (Q1 2025 – Q4 2026)

#### 🔹 Q1 2025 — System Integration & Launch Foundation

Angel Wallet, Twin Protocol Integration, App Infrastructure

* ANGL Utility:
  * Required for initial token-gated access to premium AI Twin services.
  * Enables foundational login, registration, and wallet access tied to AI identities.
  * Powers onboarding of Angel AI into the Twin Protocol ecosystem, linking vaults and smart contract billing.

#### 🔹 Q2 2025 — Token Launch & Extended Vaulting

Smart Contract Deployment, TGE, Advanced Twin Services

* ANGL Utility:
  * Required to unlock advanced AI features (e.g., scheduling, branding tools, broadcast capabilities).
  * Extended AI vaulting and memory management incur ANGL micro-payments.
  * Used for creation of high-fidelity AI Twins with audio and video integration.
  * Payment mechanism for real-time Twin interactions (chat, content requests, etc.).<br>

#### 🔹 Q3 2025 — Monetization & Marketplace Activation

Twin Points Conversion, Marketplace, Referral Rollout

* ANGL Utility:
  * Enables conversion between earned Twin Points and tradable ANGL (inside Twin Vault interface).
  * All peer-to-peer marketplace transactions (hire, license, collaborate) are conducted in ANGL.
  * Community and leaderboard contests distribute ANGL to top creators and users.
  * Ingestion tools that convert user uploads into trainable AI memory are paid for in ANGL.
  * Two-tier referral commissions (2% direct / 1% indirect) are paid out in ANGL.<br>

#### 🔹 Q4 2025 — Customization, Vault Scaling, and Web Access

AI Twin Branding, Vault 2.0, Twin Interface Expansion

* ANGL Utility:
  * Payment method for Twin customization (voice models, tone, visual avatars).
  * Vault scaling (not staking) requires ANGL to expand memory, metadata tags, and data type support.
  * Used for unlocking higher-frequency usage of AI Twins in business and personal workflows.
  * Required for activating professional web-based Twin dashboards and export tools.<br>

#### 🔹 Q1 2026 — Real-World Expansion & Smart Devices

IRL Interactions, Brand Events, IoT Integration

* ANGL Utility:
  * Used for session-based Twin deployments at live events, stores, or conferences.
  * Smart device and kiosk interactions with Twins require ANGL payments per user session.
  * Monthly enterprise usage licenses paid in ANGL for companies using AI Twins for customer engagement.<br>

#### 🔹 Q2 2026 — Developer Tools & Cross-Platform Access

SDK/API Releases, AI Integrations, Business Features

* ANGL Utility:
  * API and SDK access for developers requires ANGL for authentication and usage.
  * Businesses pay in ANGL to access analytics dashboards, training data reports, and team-wide Twin deployment.
  * Compute billing and AI model usage metered in ANGL across partner apps and services.<br>

#### 🔹 Q3 2026 — Digital Asset Licensing

Twin Publishing, Licensing & Monetization of Digital Twins

* ANGL Utility:
  * Twin owners publish Digital Assets (AI-driven personas) on the marketplace using ANGL.
  * Licensing rights, reuse permissions, and access tiers are monetized through ANGL transactions.
  * Royalties and smart licensing tracked and distributed using ANGL.<br>

#### 🔹 Q4 2026 — Utility Scale-Up & Automation Tools

Web Twin Automations, Pro Features, Bulk Usage

* ANGL Utility:
  * Power users can automate Twins for scheduled messages, media posts, and follow-up replies—billed in ANGL.
  * Bulk vault uploads and advanced metadata indexing incur ANGL usage fees.
  * High-traffic brands pay ANGL to whitelist domains and scale Twin usage across larger audiences.<br>


---

# 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://whitepaper.myangl.ai/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.