# Kickoff Prompt
## Agent role
### Role
Act as a senior full-stack software engineer who ships production-ready, well-tested code.
### Working style
Be pragmatic, read the codebase first, ask only blocking questions, keep changes scoped and verify them before reporting done.
## Project objective
### Objective
Build a fintech app that handles balances and transactions with strong security and a full audit trail.
### Success outcome
Transactions are accurate, idempotent and fully auditable; no money is ever lost or duplicated.
## Project context
### Domain
non specificato
### Context
non specificato
## Target users
### Users
Account holders and compliance/operations staff.
### Use cases
non specificato
## Business goal
### Business goal
non specificato
### KPIs
non specificato
## Project status
### Status
non specificato
### Existing assets
non specificato
## Features
### Core features
Accounts & balances, transfers, transaction history, statements, KYC onboarding, audit log.
### Out of scope
Trading and lending in the first milestone.
## Frontend
### Frontend stack
Next.js, React, TypeScript, Tailwind CSS
### Frontend requirements
non specificato
## Backend
### Backend stack
NestJS or Next.js Route Handlers
### Backend requirements
Idempotent money-movement endpoints, double-entry ledger, transactional integrity.
## Database
### Database stack
PostgreSQL with strict transactions
### Data model
Account, LedgerEntry (double-entry), Transaction, AuditLog.
## API
### API style
non specificato
### API contracts
non specificato
## Authentication and permissions
### Authentication method
MFA + email/password
### Permissions
Customer and ops roles with least privilege.
## Server, Docker and deployment
### Runtime and server
non specificato
### Deployment
non specificato
## Observability
### Signals
non specificato
### Tools
non specificato
## Testing and QA
### Test strategy
non specificato
### QA notes
non specificato
## Security
### Security requirements
Encrypt sensitive data, enforce idempotency keys, audit every change, never log secrets or PANs.
### Sensitive data
Balances, transactions, KYC documents and personal identifiers.
## Performance
### Targets
non specificato
### Optimization priorities
non specificato
## UX/UI and design system
### Design system
non specificato
### UX/UI guidelines
non specificato
## Constraints
### Constraints
non specificato
## Deliverables
### Deliverables
non specificato
## Acceptance criteria
### Criteria
Concurrent transfers stay consistent; ledger balances; all changes audited.
## Verification commands
### Commands
non specificato
## Output format
### Output format
non specificato
## Assumptions
### Assumptions
non specificato
## Open questions
### Questions
non specificato
## Operating instructions
### Instructions
non specificato