THE RADARYNO NOTEBOOK

Verify AI Resume Claims Against Career Notes

An AI-generated resume claim can sound precise while combining several facts from different projects, roles, or dates. A claim-to-source ledger gives you a controlled review method: preserve the draft, split compound statements, locate the relevant career note, classify each part, and rewrite only what the notes support. This guide focuses on tracing existing statements rather than proofreading style, resolving contradictory records, or creating a new resume. The method also fits documents produced with the Radaryno Resume Kit, whose workflow uses buyer-provided career notes and asks when evidence is missing.

01

Preserve the generated draft

Select one resume version and copy the relevant section into a review document without editing it. Record the document language, role context, and generation date if those details are available in your own records, but do not infer missing metadata. The goal is to create a stable reference for what the AI actually wrote. If the Radaryno Resume Kit produced the document, you can review the generated HTML or PDF text alongside your career notes; the kit’s documents remain on your computer. Keep the original separate from any corrected version so later changes can be traced to a specific claim.

02

Create one ledger row per claim

Build a simple ledger with fields for the original claim, its smaller factual parts, the source note, the evidence classification, and the proposed correction. Enter the claim before deciding whether it is accurate. A sentence may contain a tool, action, audience, date, ownership level, scale, and outcome, so one row may be too broad. Use separate rows when a phrase could be supported while another phrase cannot. This structure is useful whether the document was written manually or generated from buyer-provided career notes with the Radaryno Resume Kit.

03

Split compound statements before judging them

Read each sentence as a collection of factual assertions rather than as one polished unit. Separate who did the work, what they did, which technology or process was involved, for whom, when, and what changed. Pay close attention to verbs such as led, owned, managed, delivered, and designed because they can raise the level of responsibility beyond the notes. Also separate numerical outcomes from the underlying activity. This step is the main safeguard against accepting a sentence merely because some of its words match the career record.

04

Trace each part to a career note

For every small assertion, locate the closest supporting passage in the career notes and copy enough context to show what it actually says. Record the note’s wording rather than relying on memory. A source can support a technology but not an outcome, or an activity but not a leadership claim. If the notes do not contain a direct match, record that absence plainly. Do not fill the gap from common industry practice, the job description, or what would sound persuasive. The ledger should show the boundary between documented experience and an attractive inference.

05

Classify evidence with precise boundaries

Use three practical classifications: supported, unsupported, and uncertain. Mark a statement supported only when the notes clearly establish the same activity, scope, and level of responsibility. Mark it unsupported when the notes provide no basis for the detail, including an invented metric or tool. Use uncertain when the notes suggest the detail but do not establish it clearly enough to state as fact. Apply the classification to each claim part, not only to the sentence as a whole. This makes the review useful when a generated sentence mixes accurate and inaccurate details.

06

Rewrite and recheck the corrected claim

Replace unsupported wording with the narrowest statement the source can defend. Remove invented metrics, reduce ownership verbs when necessary, and keep a supported technology or activity if it remains accurate. For uncertain details, either omit them or phrase the record conservatively without implying proof. Then compare the corrected sentence with the original ledger row and confirm that every remaining factual element has a source. If the Radaryno workflow reports a gap or asks rather than inventing, use the same discipline during your review: unanswered evidence questions should remain open rather than becoming polished claims.

Fictional illustrative claim-to-source ledger for checking generated resume statements
Draft claimCareer note locatedFindingSafer correction
Fictional illustrative example: Led a PostgreSQL migration that cut reporting time by 40%.Maintained PostgreSQL reports; notes mention no migration and no measured reduction.Only the technology and reporting context are supported.Maintained PostgreSQL reporting workflows; migration ownership and time reduction were removed.
Fictional illustrative example: Built a JavaScript dashboard for the finance team.Notes say created an internal JavaScript dashboard for finance analysts.Supported, with wording narrowed to the documented audience.Built an internal JavaScript dashboard for finance analysts.
Fictional illustrative example: Managed three engineers during the platform launch.Notes describe coordinating launch tasks with three engineers; no direct-management statement.Coordination is supported; people management is uncertain.Coordinated launch tasks with three engineers.
Fictional illustrative example: Automated weekly exports and saved the team ten hours.Notes confirm automated exports but contain no time estimate.Automation is supported; the quantified outcome is unsupported.Automated weekly exports; the time saving was not stated in the notes.

A worked review sequence

  1. Start with one generated sentence and preserve it exactly. For the fictional claim about leading a PostgreSQL migration, mark the technology, activity, ownership, and measured outcome as separate evidence questions. This prevents a supported tool name from making the entire sentence appear reliable.

  2. Next, search the career notes for direct support for each part. The fictional notes confirm PostgreSQL reporting work, but they do not describe a migration or a forty percent reduction. Record the closest source without upgrading it into proof.

  3. Then classify the parts separately. The technology and reporting context are supported, while migration ownership and the metric are unsupported. If a note is suggestive but incomplete, use an uncertain classification instead of forcing a yes or no.

  4. Finish by rewriting only the supported substance and retain the ledger beside the corrected draft. In this fictional case, the safer statement describes maintaining PostgreSQL reporting workflows and removes both the unverified ownership and the unrecorded measurement.

Put it into words

Before and after

Fictional examples: not real people.

Before

Fictional illustrative example: Managed three engineers during the platform launch.

After

Fictional illustrative example: Coordinated launch tasks with three engineers.

Before

Fictional illustrative example: Built a JavaScript dashboard that saved ten hours weekly.

After

Fictional illustrative example: Built an internal JavaScript dashboard; no time saving was recorded.

Before

Fictional illustrative example: Led a PostgreSQL migration that cut reporting time by 40%.

After

Fictional illustrative example: Maintained PostgreSQL reporting workflows.

Before

Fictional illustrative example: Delivered a multilingual resume for every regional market.

After

Fictional illustrative example: The notes support preparing documents in the requested offer language; market coverage was not documented.

A few details

Frequently asked questions

What counts as a supported resume claim?

A claim is supported when the career notes clearly establish the same activity, technology, scope, ownership level, and outcome stated in the draft. A matching tool name alone is not enough. For example, notes about maintaining PostgreSQL reports do not support leading a PostgreSQL migration or claiming a measured time reduction.

Should I mark a claim uncertain when the notes are vague?

Yes. Use uncertain when the notes point toward a detail but do not establish it clearly. This is different from unsupported: uncertain means there may be relevant evidence that needs clarification, while unsupported means the notes provide no basis. Until the record is clarified, omit the detail or use wording that does not present it as a confirmed fact.

Can the Radaryno Resume Kit verify every generated statement automatically?

The supplied product facts describe a workflow that uses buyer career notes, selects relevant experience, reports gaps, and asks rather than inventing. They do not establish automatic line-by-line verification of every statement. Use the ledger method to inspect the generated document yourself. The kit writes documents locally, but local storage does not mean the AI provider works without separate provider access.

What should I do with an unsupported metric?

Remove the metric unless a career note directly supports it. Keep the underlying activity if that activity is documented, and state the result without a number when appropriate. Do not estimate from memory or calculate a figure from assumptions. If the metric may be recoverable, mark it uncertain and check the original record before adding it.

How is this different from ordinary proofreading?

Proofreading focuses on spelling, grammar, consistency, and presentation. A claim-to-source ledger checks whether each factual component came from the career notes and whether the wording preserves the documented level of responsibility. It can reveal an invented connection between real details, an unsupported metric, or an inflated ownership verb even when the sentence is grammatically correct.

RADARYNO RESUME KIT

Your experience, selected for each offer.

A downloadable kit for Claude Code or Codex. Gaps stay visible.

See the kit