One Schema. Six Banking Missions. Six Different API Flows.
Select a mission first. The same BankTransaction schema is processed differently through CRUD/API behavior, generated UI, project files and validation.
1. Select Mission
Every showcase uses the same schema, but solves a different banking problem and follows a different API flow.
DATASET SCHEMA
transactionId : string
customerId : string
type : TRANSFER | PAYMENT | DEPOSIT
amount : number
status : SUCCESS | PENDING | FAILED
channel : MOBILE | WEB | ATM
createdAt : datetime
Mission Flow & Project Files
Select one of the six cases to see its unique process.
PROJECT STRUCTURE
Select a mission first.
2. Validate Prompt
Prompt Context
Prompt Quality Gate
AI should know the banking goal, schema, API operation, files it may change, failure behavior and acceptance criteria before generating code.
AI should know the banking goal, schema, API operation, files it may change, failure behavior and acceptance criteria before generating code.
3. Architecture Generator — Frontend ↔ Express API ↔ Dataset
This simulation changes with the selected mission.
🖥 Frontend / Consumer
→
⚙ Express API
↔
🗃 BankTransaction
4. Code Preview
Generated code is still PREVIEW ONLY.
Files Changed
5. AI Validation & Review
AI checks the generated preview, but does not authorize deployment.
Integration Contract
6. Human Approve
👤 HUMAN APPROVAL GATE
Review business intent, file scope, API behavior, tests and privacy. AI cannot press this button.
7. Production Showcase
Built-in Web Server
http://vlab.local:8080 · RUNNING
Serves the generated Production App.
Internal Express API Simulator
/api/transactions · RUNNING
In-memory CRUD state shared with the Production window.
Server Request Log
[BOOT] Waiting for Production deployment...