Glossary

​

Terminology

​

A2A (Agent-to-Agent)

Protocol and helpers in lib/a2a.ts for messages between agents: request, response, notification, data_share. Used in tests and for coordination during execution.

​

Agent

An AI role (e.g. IdeaProcessor, IntentAnalyzer, PlatformSelector, ProductManager, FrontendDev, BackendDev, DevOpsEngineer, ToolManager) that produces outputs via LLM calls or logic. Defined in lib/x402.ts (AGENT_ROLES) and used in lib/openai.ts and lib/platform-templates.ts.

​

Blueprint

The full set of deliverables for a project: PRD, PLAN, specs, prompts, infra docs, etc. Same as project or deliverables in context.

​

Clarifying questions

Questions generated by IdeaProcessor from the user’s idea. The user answers them in Intent; IntentAnalyzer produces refined requirements.

​

Completion

The last workflow stage. The UI shows the execution summary, deliverables, and download. No API; it consumes executionResult from the workflow.

​

Deliverable

A single generated artifact: a file (e.g. PRD, spec, prompt) with type, content, format, path, and agent. Returned in execution_result.deliverables.

​

Dodo

Payment provider for card/UPI. Checkout is created via /api/dodo/create-checkout; Dodo sends webhooks to /api/dodo/webhook. See Dodo Payments.

​

Execution

Workflow stage where the X402 flow runs: platform templates, agents, and generatePlatformDeliverables. Triggered by POST /api/execute after payment.

​

Idea

The user’s initial project description. Submitted to POST /api/idea; IdeaProcessor returns analysis and clarifying questions.

​

Intent

Workflow stage where the user answers clarifying questions. POST /api/intent with sessionId and answers; IntentAnalyzer returns refined requirements.

​

OpenRouter

AI API used for all LLM calls (Idea, Intent, Platform, Execution). Supports GROK, Qwen, Gemini. See OpenRouter Setup.

​

Payment processing

Workflow stage where the user pays: Solana (Phantom/AppKit) or Dodo (card/UPI). Precedes Execution.

​

Platform

One of Website, Web Application, Android, iOS. Chosen in the Platform stage; determines templates, agents, and tech stack.

​

Platform selection

Workflow stage where PlatformSelector suggests platforms and a recommendation. POST /api/platform returns platform_options and recommended.

​

PRD (Product Requirements Document)

Markdown doc with requirements, user stories, and scope. Generated by ProductManager; typically docs/PRD.md.

​

PLAN

Project plan (phases, milestones). Generated by ProductManager; e.g. docs/PLAN.md.

​

Refined requirements

Structured output from IntentAnalyzer: title, description, features, target_audience, technical_requirements. Used by Platform and Execution.

​

Session ID (sessionId)

Unique identifier for a workflow run. Returned by /api/idea; required by Intent, Platform, Payment, Execute, and related APIs. Stored in Workflow.sessionId.

​

Supabase integration

Optional flag in the Platform request. When true, the blueprint includes Supabase guides (e.g. db/supabase.md) for Auth, Realtime, Storage.

​

Treasury (Treasury wallet)

Solana address that receives payments (TREASURY_WALLET). Exposed to the client as agentAddress from /api/payment/config.

​

Workflow

End-to-end run: Idea → Intent → Platform → Payment → Execution → Completion. State is stored in the Workflow model (DB) or in-memory in lib/x402.ts.

​

WorkflowContext

In-memory/DB representation of a workflow: sessionId, currentStage, idea, analysis, clarifyingQuestions, answers, refinedRequirements, platformOptions, selectedPlatform, paymentDetails, executionResult, etc. See lib/x402.ts.

​

WorkflowStage

One of: idea_input, intent_analysis, platform_selection, payment_processing, execution, completion. Order is linear; getNextStage and validateStageTransition in lib/x402.ts enforce it.

​

X402

Orchestration and workflow logic: stages, transitions, and execution. Implemented in lib/x402.ts and lib/openai.ts (executeX402Workflow). The name is used for the “X402 workflow” and “X402Agent” in AGENT_ROLES.

---

​

Acronyms

---

​

Technical terms

​

AppKit (Reown)

Wallet connection UI and Solana adapter. Used for Phantom and other Solana wallets. Config in config/appkit.ts; NEXT_PUBLIC_REOWN_PROJECT_ID.

​

getAgentForFile

Function in lib/platform-templates.ts that maps a file path to an agent (ProductManager, FrontendDev, BackendDev, DevOpsEngineer, ToolManager) using path substrings.

​

Helius

Solana RPC provider. HELIUS_RPC_URL (or SOLANA_RPC_URL, NEXT_PUBLIC_SOLANA_RPC_URL) is used for balance checks and transaction verification.

​

Platform template

Defines folderStructure, techStack, agentsRequired, costScript, timelineSeconds for a platform. Implemented as getWebsiteTemplate, getWebAppTemplate, getAndroidTemplate, getIOSTemplate in lib/platform-templates.ts.

​

Phantom

Solana wallet. Supported via Reown AppKit’s Solana adapter; the user selects Phantom in the wallet list.

​

Prisma

ORM and migrations for PostgreSQL. DATABASE_URL; models include Workflow, User, Transaction, AgentStat, ZipFile, etc.

​

validatePayment

Function in lib/solana.ts that checks a wallet has enough balance ( SOL) for the required amount.

​

verifyTransaction

Function in lib/solana.ts that checks a Solana transaction signature is confirmed and not failed.

​

ZipFile

Prisma model and table that stores the project ZIP (fileData, fileName, fileSize) by sessionId. Used by /api/projects/download before falling back to the filesystem.

---