System map

One profile, five substantial workflows.

The architecture is intentionally centered on verified personal context. Each vertical can evolve independently without asking the user to rebuild their history from scratch.

5Verticals
2Languages
1 profileSource of truth
01

Context

Career preparation is usually fragmented across resume builders, spreadsheets, interview notes, language-practice apps, and disconnected AI prompts. Each tool asks for the same personal history again, and the generated output quickly drifts away from the user’s actual experience.

02

Problem

Create one coherent system in which a living user profile becomes the source of truth for every career and opportunity workflow, while keeping generated output editable, attributable, and resistant to invented personal details.

03

Constraints

Five substantial product verticals must share one data model without becoming a monolith. The experience must work in Indonesian and English, remain useful before AI generation, support local development and serverless deployment, and keep listening audio pre-generated rather than triggering expensive TTS at play time.

04

Architecture

A Next.js application coordinates a shared UserProfile model through Prisma and libSQL/Turso. Document Suite, Application Ops, Interview Prep, English Readiness, and Opportunity Essays read from the same profile, while document versions, revision requests, practice sessions, certificate records, and audit logs preserve history and accountability. Supabase-backed services are prepared for production authentication and media storage.

05

Decisions

The profile is treated as a product primitive rather than an onboarding form. Generation must verify missing context before writing, every output remains editable, follow-up changes create explicit versions, and application tracking stays user-controlled instead of becoming an auto-apply bot. Indonesian and English are first-class modes rather than translated afterthoughts.