superme-cv

name	superme-cv
description	Use when generating, updating or exporting the user's CV or academic profile from the superme database — "update my CV", "add this paper", "export CV to PDF", or building a tailored CV for an application.

superme-cv

The CV is generated from db/, not maintained as a separate document. Facts live once, in db/outputs/ and db/affiliations/; the CV is a rendering.

Existing pipeline

~/Desktop/cv_design/ already builds the PDF:

cd ~/Desktop/cv_design
node export_cv_pdf.mjs        # cv.html -> cv.pdf

Reuse it. Do not build a second CV pipeline.

A career-notes repo, if one exists, holds the existing profile material and is the seed for db/outputs/. It is referenced, not absorbed.

Entity shapes

# db/outputs/2026-method-natcomms.md
id: output-method-natcomms-2026
type: output
title: "<paper title>"
kind: paper            # paper | talk | poster | teaching | software | award
venue: Nature Communications
status: submitted      # draft | submitted | in-review | accepted | published
date: 2026-03-01
role: first-author
project: project-method

# db/affiliations/institute.md
id: affiliation-institute
type: affiliation
title: <institute name>
role: ...
start: 2024-01-01
end: null

Building a tailored CV

1. superme index so the derived index is current.
2. Read db/_index/output.json and db/_index/affiliation.json.
3. Select and order for the specific application — a tailored CV is a selection problem, not a formatting one.
4. Render through cv_design/.
5. Never invent an output, a date, or a role. If something is missing from the database, add it via superme capture first, with the user confirming it.

Keeping it current

When a paper is submitted, accepted or published, capture the status change rather than editing the CV. The CV re-renders; the database is what persists.