V2 Core Concepts
Understanding the fundamental concepts of The Architech V2.
Concepts Overview
- V2Genome - The V2 genome structure
- Monorepo-Only Architecture - Why all projects are monorepos
- Marketplace-CLI Relationship - How marketplaces transform genomes
- Execution Flow - How V2 executes projects
V2Genome
The V2Genome is the new genome format that defines your project structure:
{
workspace: { name, description },
marketplaces: { ... },
packages: { ... },
apps: { ... }
}Key Points:
- Business-level packages (not technical modules)
- Apps declare dependencies on packages
- Marketplaces provide recipe books that map packages → modules
Monorepo-Only
V2 only supports monorepo projects. No single-app projects.
Why?
- Workspace dependencies (
workspace:*protocol) - Shared code across apps
- Consistent structure
- Better dependency management
Limitations:
- Cannot create single-app projects
- Must use monorepo structure
Marketplace-CLI Relationship
Marketplaces transform V2Genome → StandardizedGenome:
- Marketplace loads recipe book (package → module mapping)
- CLI calls
transformGenome()on marketplace adapter - Marketplace expands packages into modules using recipe book
- Marketplace resolves dependencies and creates lock file
- CLI receives StandardizedGenome ready for execution
Key Point: CLI is generic, marketplaces are opinionated.
Execution Flow
V2 execution follows this order:
- Path Mapping Generation - Generate all path keys
- Framework Bootstrap - Initialize frameworks (Next.js, Expo, Hono)
- Module Execution - Execute regular modules
Why this order?
- Frameworks must initialize first (create app structure)
- Modules need correct paths (generated before bootstrap)
- Framework modules execute only during bootstrap
Ready to learn more? Explore each concept in detail: