THE RADARYNO NOTEBOOK

Stop AI from Turning Personal Projects into Employment

Personal and open-source work can demonstrate useful skills without being employment. The risk appears when an AI system turns a repository, experiment, or volunteer contribution into a client engagement, company role, or production deployment. This guide shows how to audit the source context before asking AI to write a resume entry. You will separate ownership, payment, audience, operational use, and outcomes, then preserve uncertainty instead of filling gaps with plausible claims. The process applies whether you use Radaryno or another system that works from your career notes.

01

Collect the original project context

Open your career notes, repository records, project documentation, or other source material and gather the facts that existed before any AI rewrite. Record the project name, dates, ownership, purpose, collaborators, payment status, intended audience, operating environment, and evidence for each outcome. Separate what you personally did from what a library, school, community, or other contributor did. If a fact is missing, mark it as unknown instead of supplying a plausible answer. This first pass establishes provenance and gives the generator a factual basis for distinguishing personal work from employment.

02

Add an explicit relationship label

Give every project a clear relationship label before asking for resume language. Suitable labels include personal project, open-source contribution, volunteer work, academic work, contract work, or employed work. Add a short explanation where the label could be misunderstood, such as “personal project published publicly” or “volunteer contribution for a community group.” Do not rely on a project title, repository visibility, or technical complexity to communicate the relationship. A direct label makes it harder for a model to convert an interesting project into an invented job, client engagement, or employer assignment.

03

Audit claims about use and operations

Review every statement that could imply real customers, business ownership, production operation, or organisational responsibility. Ask whether the project had confirmed external users, what data it handled, where it ran, and whether anyone depended on it. Distinguish a local test, a public demo, a hosted preview, and a production service. If your evidence only shows that the application worked in a test environment, retain that narrower description. Avoid turning a deployment method into proof of operational use. This is the point where unsupported employment narratives often enter an otherwise accurate project description.

04

Separate activities from employment signals

Rewrite source notes so they describe actions without borrowing the language of a job unless a job actually existed. “Built,” “documented,” “tested,” and “contributed” can describe personal or community work. Terms such as employer, client, team assignment, paid engagement, company product, and production owner require supporting context. Also check titles: calling yourself a founder, consultant, or engineer may be misleading if the title was never used or if it suggests a relationship that did not exist. Preserve the useful technical detail while removing status claims that the source notes cannot support.

05

Generate with uncertainty preserved

Give the cleaned notes to the resume system and instruct it to use only confirmed context, report gaps, and ask questions rather than inventing answers. The Radaryno Resume Kit uses buyer career notes, selects relevant experience, reports gaps, and asks rather than inventing; its generated files stay on the buyer computer. It can produce an HTML and PDF resume in the offer language, but output format does not validate a claim. Review whether the generated entry keeps the relationship label, dates, audience, and operating boundary intact. If the system asks about an unsupported detail, leave it unresolved until you verify it.

06

Compare the draft with the source record

Perform a final provenance comparison line by line. Confirm that every employer, client, title, payment statement, user claim, and production reference appears in the source notes or has been separately verified. Check that personal and open-source work remains in an appropriate section and is not merged with employment history merely because the wording sounds professional. If the draft is too vague, add documented scope or technical detail; if it is too strong, narrow the wording. Keep a corrected version of the source note so later generations do not reintroduce the same unsupported context.

Context checks that keep project claims separate from employment history
Source contextPayment or employerSafe descriptionClaim to avoidRequired evidence
Personal projectNo employer or clientBuilt and maintained a personal tool to explore a stated problemPresented it as company work or client deliveryThe notes confirm the build, maintenance and personal setting.
Open-source contributionNo employer unless separately documentedContributed code, documentation, or issue work to a public projectCalled the project a job or paid engagementThe notes identify the actual contribution and relationship.
Volunteer workAn organisation may exist; payment is not assumedCreated or improved something for a named organisation as a volunteerImplied an employment relationshipThe notes confirm volunteer status and the described activity.
Academic workSchool or research settingCompleted a course, thesis, or research project with defined scopeClaimed commercial ownership or customer useThe notes confirm the academic setting and completed work.
Contract or employmentDocumented client or employerReported work under the confirmed role and datesAdded an unverified title, client, or operational outcomeThe notes confirm the relationship, title, dates and actual work.

A worked provenance review

  1. Consider a fictional developer who built a budgeting application at home, published the source code on GitHub, and received no payment. The initial note says, “Created a budgeting platform used by customers.” That wording combines a personal project with an unsupported customer claim, so it is not safe input for a resume generator.

  2. The developer checks the evidence and records a narrower context: personal project, unpaid, self-directed, published repository, demonstration data, and no confirmed external users. The work may still show technical decisions, testing, documentation, or deployment practice, but those claims must remain tied to what actually happened.

  3. The corrected source note becomes: “Built and maintained a personal budgeting application with a JavaScript interface and PostgreSQL storage; published the code on GitHub; tested with sample data; no employer, client, or confirmed production users.” Each clause identifies an observable activity without implying employment.

  4. A generated entry can now describe the build, technologies, and testing boundary. If the system asks whether the application supported customers or operated in production, the answer should remain unknown or no rather than being inferred from a public URL. The project is evidence of personal work, not employment.

Put it into words

Before and after

Fictional examples: not real people.

Before

Confirmed notes describe a maintained personal budgeting app with sample data, GitHub publication and workflow tests. AI draft: Built a budgeting platform for customers.

After

Built and maintained a personal budgeting application with sample data; published the code on GitHub and tested the main workflows.

Before

Confirmed notes describe unpaid code and documentation contributions to an open-source analytics project, with no employer or client. AI draft: Worked as a developer on an open-source analytics product.

After

Contributed code and documentation to an open-source analytics project; no employer or paid client relationship was involved.

Before

Confirmed notes describe a volunteer prototype for a local organisation; production use is unconfirmed. AI draft: Deployed a production service for a local organisation.

After

Created a volunteer prototype for a local organisation; production use was not confirmed.

Before

Confirmed notes describe a personal inventory prototype and task coordination with online contributors, with no formal team or employer. AI draft: Led a team delivering an inventory system.

After

Coordinated tasks with online contributors while developing a personal inventory prototype; no formal team or employer existed.

A few details

Frequently asked questions

Does publishing a project online make it professional employment?

No. A public repository, demo, or hosted page shows visibility, not an employer relationship. Describe the work as personal, open-source, academic, or volunteer activity unless your notes document paid work or a confirmed role. You can still describe the technical decisions and contributions without presenting them as employment.

Can a personal project mention real users?

Yes, when the users and scope are documented. Specify whether they were you, testers, community members, or confirmed external users. Do not use “customers” merely because a project was publicly accessible. If usage is unknown, say so or omit the claim rather than allowing an AI system to infer an audience.

How should open-source contributions appear if there was no employer?

Describe the contribution and the project relationship directly. You might state that you submitted code, documentation, tests, or issue fixes to an open-source project. Keep the project’s maintainers, sponsoring organisation, and your own role distinct. Public collaboration does not by itself establish employment, payment, or a company assignment.

What if I do not know whether a project reached production?

Keep the operational status unknown until you can verify it. A local build, hosted demo, staging environment, or successful test does not prove production use. An accurate entry can mention the environment you know about and the testing performed. A resume generator should report the gap or ask a question instead of selecting the stronger interpretation.

Can a resume kit prevent every invented project claim?

No tool can replace source review. The Radaryno Resume Kit is designed to work from buyer career notes, report gaps, and ask rather than invent, but the quality of the result still depends on the accuracy and clarity of those notes. Review the generated HTML and PDF against your source record before using either document.

Does local document storage mean the AI works without an online provider?

No. The generated files and source documents can stay on the buyer computer, but local file storage does not mean offline AI inference. Access to an AI provider is separate from the one-time Radaryno purchase. Review the provider arrangement and your own data preferences before sending career notes for generation.

RADARYNO RESUME KIT

Your experience, selected for each offer.

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

See the kit