Stage 01 / 04 · Sources
Start with the material you have
Connect a GitHub repository and selected branch, then upload a DOCX resume. These become sources for a shared career profile.
Repository + DOCX → extraction
GitHub App + resume uploadProject preview · № 003 · Coming soon
TRACE · one profile, reviewed changes
An AI-assisted career workspace connecting a resume and GitHub portfolio through one shared profile. Review changes before they become commits or pull requests.
Coming soon
The central idea
One career. Fewer versions of the truth.
01The problem
A resume and a portfolio describe the same career, but keeping them current means repeating edits across documents and repository files. As those copies drift, it becomes harder to know which details are current and which changes belong where.
Interactive field notes / system map
Follow a change through Trace
Conceptual walkthroughSelect a stage ↓
Stage 02 / 04 · Profile
A shared model for a shared story
AI-assisted extraction builds career data with source attribution and review controls. Resume and portfolio views work with the same profile.
Sources → career profile → views
Experience · projects · skillsStage 03 / 04 · Review
Differences need a decision
Inbound and outbound changes are compared against accepted baselines. Conflicts are surfaced for confirmation or rejection before a write.
Candidate → baseline comparison → decision
Confirm or rejectStage 04 / 04 · Publish
Turn accepted edits into artifacts
Confirmed portfolio updates become commits or pull requests. Resume export updates the uploaded layout when anchors are available, with a template fallback.
Confirmed change → commit / PR / export
Coming soon · in developmentProduct flow · simplified for this case01 / 04
Nothing leaves without a review.
02The workspace
- Connect a GitHub repository and selected branch through a GitHub App, then upload a DOCX resume.
- Build a shared career profile with AI-assisted extraction, source attribution, and review controls.
- Edit experience, projects, skills, and other career details through the profile, resume, and mapped portfolio views.
- Review inbound changes, outbound updates, and conflicts before confirming or rejecting each item.
- Push confirmed portfolio updates as a commit or pull request, and export a PDF or DOCX resume from the profile.
03Decisions that mattered
01One profile, multiple views.
Resume and portfolio editors work with the same career data, while repository mappings keep portfolio fields connected to their source files.
02Review is part of the workflow.
Repository changes and profile edits are compared against accepted baselines. Conflicting values are surfaced for a decision, and unchanged rejected candidates stay rejected.
03Preserve the document where possible.
Resume export can update an uploaded DOCX layout when its anchors are available, with a template fallback when that layout cannot be used.
04Technical foundation
The web app uses Next.js, React, TypeScript, Tailwind, shadcn/ui, and TanStack Query. NestJS owns the API, PostgreSQL and Prisma store profile and sync state, and Redis with BullMQ supports background work. A GitHub App and Octokit handle repository access and confirmed writes.
05Current status
Coming soon. This preview describes the product workflow and implementation documented in the project repository. Public launch and user outcomes are still to come.