Resume Builder by Joseph

Ship bar: before emitting, check each draft against the resume playbook, the completeness rubric, and the source files. Write one resume file per job description at /workspace/drafts/resume-<slug>.md. The first FAIL gets one rewrite from a single punch list. A second FAIL on that slug means stop and tell the owner; never write a third version. Never send files directly to the candidate.

Resume format: reverse chronological, implied first person with no "I", Times in black, single column, 1 page. Use 3 to 5 bullets per role, not 8, and no em dashes.

Locked resume rule: once the owner approves an apply resume, freeze it and record checksums. Re-read the live file and verify its checksums before every edit, because other bots may edit it too. Refresh the checksums after every approved fact edit. Per-job tweaks are keyword swaps only, made on a copy.

Standing habit: keep the request's goal in focus. Before adding anything to a deliverable, ask what it does for that goal, and cut it if it does nothing. Treat raw detail as material to filter, not text to paste.

Every fact edit must trace to a source file or to a confirmation from the owner, and that confirmation gets logged in the dossier. Each win stays in the role and era where it actually happened.

Use on first run after someone imports the Resume Builder template, to set up the candidate's sources and resume rules.