How it works
Every line on your CV has a source you can check.
cv0 builds CVs only from records you've approved, each one quoted from where it came from. Here's the flow, from an empty workspace to a tracked application.
1 · Your CV
Your CV comes first.
Drop, pick or paste it: a PDF, a Word file, an image or plain text. Each role, project, achievement, skill and education entry comes out as a record, and nothing goes on a CV until you've approved it.
- Source A line of your CV
- Candidate Not on any CV
- You Approve · Reject
- Approved Can go on a CV
- Rejected Never used
You see the exact source
Each record shows the line of your CV it was taken from, so you can judge it against what actually happened.
Re-importing is safe
Importing a newer CV replaces only records you haven't reviewed. What you've approved or rejected stays as it is.
Your base CV
Your approved records, in your own wording, make a base CV you can share as it is.
2 · A job
Give it the job as you got it.
- Paste the text, or drop a screenshot, a PDF or a Word file of the spec.
- cv0 reads its must-haves and nice-to-haves, each with the advert’s own words beside it.
- Location, work mode and pay are checked against your preferences.
3 · Fit and the tailored CV
The job decides which claims go on.
Each must-have is matched against your approved records: strong, weak or missing. The CV is drafted from the records that cover them. Requirements you can't back up stay listed as missing and off the CV.
You can remove or reword any line, or add another approved record. A reworded line needs your approval, and candidates you haven't approved can't be added.
ON THIS CVSenior AI Engineer · Northwind Health
NOT APPROVED YET
4 · Approve, share and track
What you approve is what gets shared.
Only an approved CV can be shared, at its own link. Change anything afterwards and it goes back to draft; the approved version, and any link to it, stay as they were.
Then track the application on the pipeline, from submitted to offer. Marking it submitted records which approved version you sent.
Approve it to share it.
5 · Coming next
Evidence from where your work actually lives.
Not built yet. Your AI coding sessions, found with omnirecall by your own agent, and your git history will add records the same way your CV does: as candidates, until you approve them. PDF export is coming too; for now you share a link.
| Question | omnirecall | git |
|---|---|---|
| What it reads | Your archived AI coding sessions | Your commit history |
| What it's good at | What you were trying to do, and the problems you worked through | What actually changed, where, and over what period |
| What it can't tell | Whether it shipped. cv0 asks you. | Why it mattered. cv0 asks you. |
| How it shows as proof | 12 sessions, Mar–Jun 2026 | 184 commits · eval/, ingest/ |
| What's searched | Only the projects you pick | Only the repositories you pick |