Collect and label every source note
Gather the notes you expect to use, but do not merge them into a single polished biography yet. Label each statement by source and date, such as an older resume, an employer document, a project record or personal recollection. Preserve the original wording so that later decisions remain traceable. Separate facts about dates, titles, responsibilities, tools and outcomes instead of treating a whole paragraph as one indivisible claim. If a source is unavailable, mark that limitation plainly. This first pass is about visibility, not writing quality. Radaryno can work from buyer career notes and ask rather than invent, but the buyer still needs to identify which statements are disputed and which sources support them.
Build a contradiction log
Create one entry for each conflict rather than relying on memory. A useful entry names the disputed fact, lists the competing statements, identifies their sources and explains why the difference matters. For example, a title conflict may affect whether the resume presents formal management or project coordination. A date conflict may create an apparent overlap with another role. Keep interpretation separate from evidence: “This may have been an interim assignment” is a hypothesis, not a confirmed fact. Do not rewrite the entries to sound consistent. The log should make disagreement easy to see and should remain available while you review the notes and prepare instructions for the next drafting pass.
Classify facts by confidence and ownership
Review each contradiction using clear categories: confirmed, plausible but unconfirmed, and unusable for a factual claim. Also assess ownership. A note may prove that you contributed to a project without proving that you led it, approved it or achieved its full result. Distinguish personal action from team activity, and formal title from an informal description. When a source supports only part of a statement, keep the supported part and isolate the remainder. This prevents a correct date from lending false certainty to an uncertain title or a documented task from becoming an unsupported ownership claim. Your classifications become drafting boundaries, not decorative labels.
Ask targeted confirmation questions
Turn each unresolved entry into a question that can be answered without reconstructing the entire career history. Ask for the exact title, the applicable dates, the scope of responsibility or the source for a result. Avoid leading questions that suggest the more favorable answer. If two statements could both be true, ask whether they describe different periods, an interim assignment or a distinction between formal title and working role. Record the answer in the career notes with its source and date. If the buyer cannot confirm a detail, keep it outside resume claims rather than filling the gap with a likely interpretation.
Create a confirmed-facts boundary
Before any resume text is drafted, prepare a concise boundary containing facts that may be stated, facts that require cautious wording and facts that must not appear. Include confirmed dates, formal titles, supported responsibilities and outcomes with evidence. For uncertain items, specify what wording is permitted, such as describing participation without claiming ownership. For excluded items, state the reason: conflicting dates, unverified scale, uncertain title or missing source. This boundary helps prevent a later rewrite from reintroducing a discarded claim. It also gives Radaryno useful input because the kit can select relevant experience, report gaps and ask rather than invent when the notes do not support a statement.
Draft from decisions, not from raw contradictions
Use the confirmed-facts boundary as the only basis for resume content. A role can include a verified formal title and a separately supported responsibility, but it should not combine competing versions into a single stronger claim. If the role is relevant, explain the contribution at the level the evidence supports. If a gap remains, let it remain a gap in the source material rather than disguising it with broad wording. Radaryno can produce an HTML and PDF resume and an optional cover letter in the offer language, but the generated documents should reflect your decisions, not replace them. Review the first draft against the contradiction log before considering style or layout.
Audit the generated documents and update the record
Read the generated resume and optional cover letter as factual documents, not only as formatted output. Check every date, title, ownership verb, project description and result against the confirmed notes. Look for accidental combinations created when nearby facts appear in the same paragraph. If the documents are prepared in more than one offer language, check that titles and responsibilities retain the same factual scope rather than gaining stronger meaning through translation. Correct the source notes or boundary first, then regenerate. Radaryno keeps files and generated documents on the buyer computer, while AI provider access remains separate from the kit purchase, so review both the local documents and the information sent to the chosen provider.
| Conflict type | Keep as confirmed | Set aside until confirmed | Useful evidence |
|---|---|---|---|
| Employment dates | Dates repeated by an official record and a consistent personal note | Overlapping months that cannot be explained | Offer letter, payroll record or professional profile |
| Job title | The title shown on an employer-issued document | An informal title used only in one note | Contract, HR record or dated internal document |
| Responsibility | A task directly supported by a project record or clear recollection | Ownership that may have belonged to a team or manager | Project brief, review or message assigning the work |
| Achievement wording | A factual action and its documented result | A precise percentage or scale without a source | Dashboard, report or approved presentation |
Worked example: separating a disputed role before drafting
Fictional:true — Before review, one note says “Product Operations Lead from March to October,” while an older resume says “Operations Coordinator from June to December.” Treat these as separate source claims rather than selecting the more senior title.
Fictional:true — Compare the dates, title and responsibilities independently. A contract may confirm the coordinator title, while a project brief may show lead-level duties during a limited period. Record those as different facts instead of forcing them into one employment line.
Fictional:true — After review, the confirmed statement could be “Operations Coordinator, June to December.” A separate responsibility could read “Coordinated launch planning for the internal product team,” provided the source supports that wording and does not imply formal ownership.
Fictional:true — If the March start date and Lead title remain unresolved, keep both outside generated claims. Ask the buyer to confirm them, then regenerate only after the decision is recorded in the career notes.