Applied The Lora Playbook

The Source Availability Scanner

Last reviewed

Beginner

What you'll learn

~35 min
  • Ask an AI tool, in plan mode, for a small program that reports what source material exists for each game on your target list
  • Read its plan for what the report must keep: every game, its source status, and whether you checked that status yourself, where and when
  • Tell the five source statuses apart (official release, decompilation, mod kit, nothing, unknown), and a fan patch from source code
  • Treat a status nobody has checked as a lead, and check it yourself before it moves money

The story, and what you will end up with

You want to start a retro game remake company. Beside the question of who owns a game, there is one you can start on today from public sources: what source material exists for it? Released source code you can study, a fan decompilation that shows how the game worked, an official mod kit, or nothing at all. The answer shapes your engineering timeline, your budget and your pitch, and whether you are rebuilding from scratch or standing on someone else’s map.

You have six games on your list, with BloodRayne and BloodRayne 2 at the top. So far the research lives in your head and in a rough spreadsheet: a status for each game, a few notes on what you have read, and one link. Only one of those six statuses is something you have opened and looked at yourself.

By the end of this lesson you will have a small program on your own computer, the scanner, that reads your target list and prints a source availability report: each game, its status, whether you checked that status yourself, where and when, and a count by status. You build it by asking your AI tool in plain English, and you check it by reading the report it prints.

Before you start

First, if your AI tool is still open, leave it: type /exit and press Enter (if you use Antigravity, press Ctrl+D with nothing typed instead), and wait until you see the $ or % prompt. The next line goes there, in the terminal, not in the AI tool. It makes a folder for this lesson in ~/retro-remake, beside your practice folder, and goes into it:

Terminal window
mkdir -p ~/retro-remake/01-source-scanner && cd ~/retro-remake/01-source-scanner

Start your AI tool with the start line you kept from the setup lesson, the one with approval prompts off. Then ask it to set the folder up:

Set this folder up so we can undo any change you make, download https://learn.intellimetrics.net/starters/lora/01/target-list.csv into a data folder, and save a checkpoint.

Look for it saying three things: the folder is set up with Git (the program that saves snapshots, from setup), the list is saved as data/target-list.csv, and a first snapshot, your checkpoint, is saved. Later you can ask whether the file has changed since then. If it does not mention one of them, ask: “Did you save a checkpoint with the file in it?” If the download does not work, download target-list.csv in your browser, check where it went (the browser’s list of downloads shows the folder), and tell your AI tool, for example: “target-list.csv is in my Downloads folder. Copy that one file into a data folder here, and save a checkpoint.” In Windows PowerShell or a desktop app, “my Downloads folder” works as is; only say “my Windows Downloads folder” if you use Ubuntu (WSL) on Windows, which keeps its own Downloads folder apart from Windows.

The games are real. The statuses, notes and dates in the file are practice notes made for this course, a starting point for your own research and not findings about any game.

Open this box once, because it says what each status and column used further down means.

ℹWhat is in target-list.csvclick to expand

A spreadsheet file (it opens in Excel) with six games, one per row. Each row has the game, its source_status, checked_on (the date you looked at the evidence yourself, blank if you have not), where_seen (where you saw or heard it: a link you opened, or who told you) and your notes. A row is checked only when it has the date you looked and where: a page you opened, or, for nothing, where you searched.

GameStatusChecked onNotes, in short
BloodRaynenothing(blank)No source release or decompilation project found in your reading so far. First target.
BloodRayne 2nothing(blank)Same as BloodRayne so far.
Legacy of Kain: Soul Reaverunknown(blank)Heard this morning, in a conversation, that a community decompilation project exists. Not looked up yet.
Primalnothing(blank)No source release found so far.
Darkwatchnothing(blank)No source release or community project found so far.
Oniunknown2026-11-09Link to the community Anniversary Edition, which patches and mods a retail copy. No public source reconstruction found.

The five statuses this lesson uses:

  • official release: the game’s source code has been published by those who hold it, so you can study how it was built. Note the terms it was released under as well, because code published for study and code free for commercial use are different things.
  • decompilation: fans have worked readable code back out of the released game. It shows how the game worked; it was not made or released by the game’s owners.
  • mod kit: official tools released for changing a game, such as its levels, scripts or models. What a kit includes varies, so say in your notes what this one includes.
  • nothing: you have found none of these.
  • unknown: you have not looked yet, or not finished looking.

Some things you look at will fit none of these. Fan-made re-creations of a game’s engine are common in this field, and so are fan-made modding tools. Keep those apart from unknown, which means you have not looked: record one under the nearest status and say in the notes what it really is, or add a status of your own and tell your AI tool (there is an example under Keep going).

Oni is still unknown: your notes describe the one page you checked as a patch, which is not source code, and you have not finished looking.

Switch to plan mode

Your AI tool is already open. Switch to plan mode now: Shift+Tab until it says plan, or /plan (the keys for each tool). In plan mode it usually reads your file, asks its questions and shows you a plan before it builds anything; the order can vary.

The conversation

Each message below is an example. Say it your own way.

Say what you want

Say what you are doing, which file to use, and what you want from it:

I want to start a retro game remake company. Help me build a small tool that reports what source material exists for each game in data/target-list.csv. Ask me what you need first.

Your AI tool usually reads the file and comes back with questions. It may also point out things it noticed, such as that only Oni has a check date.

Answer its questions

Answer each in a sentence. These are questions the tools often ask, with one way to answer each. Yours may ask them in a different order or show a list of choices:

If it asksYou might say
What counts as source material: released code, decompilations, mod kits, patches?Official source releases, decompilations and official mod kits.
Should it search the web or GitHub, check links, or only report what is in the file?Only what my file says; don’t look anything up.
Should it record who owns each game and any licences?Not yet; rights come later.
Should it update your file, or write a separate report?Leave my file alone and write a separate report.
In the terminal, a saved file, or a page in the browser?Print it in the terminal and save a copy I can keep.
Python, or something else?Use what’s already on this computer.
Which statuses should it use?Five: official release, decompilation, mod kit, nothing, unknown.

“Don’t look anything up” keeps the report to what you have recorded. An AI tool that searches can bring back a project page, or a confident answer from memory with no page behind it, and both would land in your report looking the same.

Your AI tool may also ask about leaked source code. A leak is not a release, because nobody with the right to give permission has given it, so it does not change a game’s status. If you hear of one, the notes record only that a leak is rumoured.

If it asks several questions at once, answer the ones about what the report must say in a sentence, and for the rest say that its suggestions are fine. If it asks something not listed here, answer it the same way, in a sentence.

Read the plan

Next it usually shows you a plan: what it will build and how it will check it. Read it for five things:

  1. Every game on your list appears, with its status as one of the five.
  2. Each game shows whether you checked it yourself, and when and where. A blank date reads as not checked, never as checked.
  3. Nothing is upgraded or guessed. A project you have only heard about stays that way (Soul Reaver stays unknown).
  4. It counts how many games have each status, and how many you have checked.
  5. It reports only what your file says. It looks nothing up, and your file is read and left as it is.

A first plan often leaves one of these out, most often the check dates or the counts. Say so in a sentence, in your own words, for example:

Also show for each game whether I've checked it myself, and when. And count how many games have each status.

When the plan has all five, approve it: if your AI tool offers a choice to go ahead, pick it; otherwise say “Yes, go ahead and build it.” In Codex, press Shift+Tab first to leave plan mode. In Copilot, saying it brings up a choice to go ahead; pick that. Let it build. It may run what it built and tell you how to run it yourself; either way, the next step asks it to. When it has finished, ask it: “Did you install anything, and where?” Nothing, or something inside this lesson’s folder, is fine for these lessons. If it names anywhere else on your computer, ask it what that is for, and to remove it if you do not want it there.

Look at what it built

Ask it to run what it built:

Run it and show me the report.

Your report will be laid out in its own way. Check it for these:

  • All six games are there: BloodRayne, BloodRayne 2, Legacy of Kain: Soul Reaver, Primal, Darkwatch and Oni.
  • The counts are four nothing (BloodRayne, BloodRayne 2, Primal, Darkwatch) and two unknown (Soul Reaver and Oni), with none in official release, decompilation or mod kit.
  • Only Oni shows as checked, on 2026-11-09, with its link. The other five show as not checked.
  • Soul Reaver is still unknown, with its decompilation project described as heard about and not yet looked up. Oni is still unknown, and its Anniversary Edition is not counted as source.
  • When you ask “Has my target list changed since the checkpoint?”, it compares the file with the checkpoint and says no.

Your AI tool may suggest changes to your list as well, for example setting Soul Reaver to decompilation once you look the project up, or calling Oni nothing. Those are suggestions about your research, not findings; leave them until you have looked. If something on the list above is not true, tell your AI tool in a sentence what you see and what you expected, for example: “Soul Reaver shows as a decompilation, but I haven’t looked that project up yet. It should stay unknown.”

Notice what the report cannot know

Your report is honest about your file. Now see what happens when the file says more than you know:

Make a copy of the target list in this folder. In the copy only, change Soul Reaver's status to decompilation and give it today's date as checked. Then run the report on the copy.

Look at what the report says about Soul Reaver now. Before you read on: has anyone looked that decompilation project up?

You have not. Your note still says you heard about it this morning and have not looked it up. But the report on the copy counts Soul Reaver as a decompilation, checked today. It may warn that there is no link; a link would quiet that warning, and a link is only as good as the page behind it. The report counts whatever the file says. It cannot know whether you opened the page, or what the page really was.

A game with a working decompilation and a game with nothing are different projects with different budgets: one comes with a map of how many of its systems worked, the other is rebuilt by playing the retail game, watching footage and reading fan wikis. So checking is yours: open the project page yourself, note the link and the date, say what the project really is (a decompilation, a patch, a mod), note the terms any released code came under, and only then change the status.

Each row of the report is a claim about a game: source released, decompiled, a patch and no source, or nothing found. Each of these claims changes your business case, and each needs checking before you commit money.

When you have looked, remove the copy: “Delete that copy and its report; I’m done with it.”

One real run

Here is part of what one AI tool printed after the experiment above, with Claude Code on 11 November 2026. Yours will word it differently; check your report against the list above, not against this.

Games listed: 6
official release 0
decompilation 1
mod kit 0
nothing 4
unknown 1
With source material (1): Legacy of Kain: Soul Reaver
Never checked (4): BloodRayne, BloodRayne 2, Primal, Darkwatch
WARNINGS
--------
Legacy of Kain: Soul Reaver: marked 'decompilation' but no where_seen link.

Practice data: the decompilation status and date were typed into a copy for this experiment.

How real source research differs

When you check a game for real:

  • Read what a community project says it is. The Oni project’s own page says: “The Anniversary Edition enhances a retail copy of Oni and is the result of years of research, work and discussion in the Oni fan community” (OniGalore: Anniversary Edition). Some decompilations also need your own retail copy, for the art and sound, so needing one does not settle which kind a project is; its own description does.
  • Note what a project page says about whether it is finished and what licence it carries, beside the link and the date you looked.
  • A decompilation shows how a game worked. It says nothing about who holds the rights or what your company may do with it. If you plan a clean-room rebuild (written without copying the original’s code), ask your lawyer before anyone on your team reads one. Who holds the rights to each game is the next lesson’s question.
  • The most useful source may not be public at all. The company that holds a game, or the studio that made it, may still have code and assets in an archive. Your list can only record what you have found in public; ask about the archive when you talk to the rights holder.

Keep going

Small changes do not need plan mode. Say each in a sentence, then run the report again:

  1. “Give me a way to update a game’s status, with where I saw it and the date I checked.”
  2. “Flag any game I haven’t checked in the last 30 days.”
  3. “Compare BloodRayne, Soul Reaver and Oni side by side: status, checked or not, and what I still need to find out.”
  4. “Add a status called engine re-creation, for a fan-made engine that runs a game’s original files, and count it like the others.”
  5. “Save a checkpoint.” Your AI tool saves a snapshot you can return to.

When you want to scan your own target list, with the games and notes you are really weighing, use the finished scanner. It runs on your real list by itself, with your AI tool closed, so your AI tool never sees it. Do these steps in order; the first three happen now, while your AI tool is open and this folder still holds only the practice list:

  1. Go through the data check, the questions in setup about what the data is, who decides how it is used, and which AI tool would see it. A list of the games you are after, and what you have found out about each, is business information you may not want a hosted service to see; the check is for that. Go on only if it allows this use.

  2. Decide on a folder of its own for your real list, outside this course folder, for example ~/remake-list. Nothing has to be in it yet. Ask your AI tool for the exact line, for example: “Write me the exact line to run this myself on target-list.csv in ~/remake-list, saving the report there.” Use your own folder’s name, written out in full from your home folder as above. If it offers to copy your real list into this folder instead, say no.

  3. Copy the line it gives you into a note. It will look something like this one, though yours may differ:

    Terminal window
    python3 ~/retro-remake/01-source-scanner/tools/source_report.py ~/remake-list/target-list.csv --out-dir ~/remake-list

    Read it left to right: python3 starts Python, which runs the program; next comes the program you built, in this lesson’s folder; then your list; and last --out-dir with the folder the report is saved in. ~ means your home folder; your line may write it out in full instead. If you are unsure about any part, ask your AI tool now, while it is still open.

  4. Leave your AI tool the way you did at the start of this lesson.

  5. Put your real list in that folder, named as the line names it. Paste the line at the $ or % prompt and press Enter. The report prints in the terminal, and a copy is saved in that folder, not in the course folder.

Try another case

Before the quiz, write two or three sentences for yourself. A friend messages you: “There’s a decomp of Night Harbor on GitHub, nearly done!” (Night Harbor is a made-up game.) What would you record in your target list today, and what would you do before you changed its status or put it in a budget?

A good answer records it as unknown, with your friend’s message as where you heard it and no check date, then opens the project page yourself: is it really a decompilation, how finished is it, what licence does it state, and who holds the game’s rights.

Key takeaways

  • Ask briefly, and let your AI tool ask back. Say what you are doing, which file to use and what you want from it; its questions fill in the rest.
  • Read the plan for your research, not the code: every game, its status, whether you checked it yourself, nothing upgraded or guessed, your file left alone.
  • Know the five statuses, and read what a project says it is.
  • The report counts what the file says. A status becomes something to spend money on only after you have opened the page yourself and recorded the link and the date.
  • Practice data stays practice data: your real target list goes to the finished scanner, with your AI tool closed, after the data check.
KNOWLEDGE CHECK

Your report shows a game as 'decompilation', checked on a date last month, with a link. A colleague wants to cut the engineering budget for it today. What should you do first?

What’s next

In the next lesson you build the BloodRayne Rights Map: a page showing every company in the game’s ownership chain, the publishing history, and the licensing questions you need answered before you can make a deal.

intellimetrics · Arlington, VA
© 2026 intellimetrics.net
Search lessons