Click a box on the map. Each panel says what that part does, what the agent may touch there, and where it sits in the process. The URL updates, so a panel can be linked to.
🧑 Me
The places a person is required, and no agent supplies any of them.
What stays mine
- Approve the plan before anything is built
- Approve the install before anything reaches the game folder
- Test in game and report back, often with screenshots
- Upload to Nexus
- Accept REDkit's licence windows
In the pipeline
- Step 1, plan — The agent writes the plan; Bill approves it.
- Step 7, install — Bill approves. The script backs up the current version, installs, hash-checks every file, and restores automatically on failure.
- Step 8, test — Bill plays it and reports back, often with screenshots. Then the loop goes round again.
🤖 Agents · 4
Two agents that can build, never at the same time: they hand over through a shared handoff log. Subagents take the parallel work. One reviewer builds nothing.
🤖 Claude builds and installs, with approval
The main modding agent, through the Claude desktop app (Opus 5.5 at the time of writing). Plans, builds the assets, drives REDkit and the install scripts.
Where it acts
- 1 · plan — The agent writes the plan; Bill approves it.
- 2 · build — Assets are built in the sandbox from the agent's own procedural code. CDPR-based assets only, never another mod's.
- 3 · transfer — Files move to the PC and are MD5-checked. Images are verified pixel for pixel.
- 4 · cook — REDkit import, cook, buildcache and pack, with every input hash-pinned.
- 5 · gate — An automated check of the cooked output: no placeholders, only the mod's own files, materials and physics data present.
- 6 · security — A pattern audit of every script, a Microsoft Defender scan, and a check that the package holds only game data files.
- 7 · install — Bill approves. The script backs up the current version, installs, hash-checks every file, and restores automatically on failure.
🧰 Codex same powers, never at the same time
The standby agent, used when Claude's usage runs low. Picks up from the handoff log; prepared the public Red Blink 1.0.5 package.
Where it acts
- 1 · plan — The agent writes the plan; Bill approves it.
- 2 · build — Assets are built in the sandbox from the agent's own procedural code. CDPR-based assets only, never another mod's.
- 3 · transfer — Files move to the PC and are MD5-checked. Images are verified pixel for pixel.
- 4 · cook — REDkit import, cook, buildcache and pack, with every input hash-pinned.
- 5 · gate — An automated check of the cooked output: no placeholders, only the mod's own files, materials and physics data present.
- 6 · security — A pattern audit of every script, a Microsoft Defender scan, and a check that the package holds only game data files.
- 7 · install — Bill approves. The script backs up the current version, installs, hash-checks every file, and restores automatically on failure.
🧩 Subagents build only
The main agent splits big jobs across parallel subagents — geometry, textures, cloth physics, research.
Where it acts
- 2 · build — Assets are built in the sandbox from the agent's own procedural code. CDPR-based assets only, never another mod's.
🔍 QA agent reviews, never builds
A separate, independent agent that reviews work before it runs unattended overnight. It caught bugs in the overnight runner and gaps in the security check before they ran.
Where it acts
Not a pipeline stage. It reads the overnight runner and the security check before they run unattended, and it is a different agent from the one that wrote them.
☁ Cloud sandbox
Heavy work runs in a cloud sandbox, not on the PC: the agent's own procedural code builds the assets from CDPR-based inputs only, never another mod's.
What is built there
- Procedural meshes
- Textures, 4K
- Cloth assets, for physics the game builds at load
- Renders and review sheets
- Analysis
Leaving the sandbox
Files move to the PC and are MD5-checked; images are verified pixel for pixel.
💻 Bill's PC
The Witcher 3 Next-Gen (Remastered), build 5.0.0.1048522 (DX12), Steam. Reached through the Claude desktop app link. Four surfaces, each with its own rule.
Surfaces
- 📁 Modding workspace — Documents and AppData are never touched.
- 🛠 REDkit — Its licence windows are accepted by hand, which is what stalls an unattended overnight build.
- 🎮 Game folder — Other authors' mods are never edited or bundled.
- 🗂 Vortex — Modpack fixes are proposed for approval and go in through Vortex or a separate compatibility mod.
Never
- Documents or AppData
- Other authors' mods: never edited, never bundled
- Publishing: uploads to Nexus are done by hand
- REDkit's licence windows: accepted by hand
📁 Modding workspace
A folder on the PC, reached through the Claude desktop app link. Where transferred assets land and where REDkit projects live.
The rule
Documents and AppData are never touched.
← The PC
🛠 REDkit
CDPR's official kit: import, cook, buildcache and pack (wcc_lite). Every input is hash-pinned.
The rule
Its licence windows are accepted by hand, which is what stalls an unattended overnight build.
← The PC
🎮 Game folder
The Witcher 3 Next-Gen install. Read freely; written only through an approved install script that backs up, installs, hash-checks every file and restores on failure.
The rule
Other authors' mods are never edited or bundled.
← The PC
🗂 Vortex
The mod manager. The agent reaches it only through on-screen control, and only with approval each time.
The rule
Modpack fixes are proposed for approval and go in through Vortex or a separate compatibility mod.
← The PC
🌐 Nexus Mods
Publishing is not the agent's. Every upload is by hand, and so is every REDkit licence window.
Public
The profile →
🧵 From a plan to the game folder
The same shape as the lab's pipeline: hashes on every transfer, a gate that checks the output rather than trusting the builder, and a person at the start, the install and the end.
The process
- plan — The agent writes the plan; Bill approves it.
- build — Assets are built in the sandbox from the agent's own procedural code. CDPR-based assets only, never another mod's.
- transfer — Files move to the PC and are MD5-checked. Images are verified pixel for pixel.
- cook — REDkit import, cook, buildcache and pack, with every input hash-pinned.
- gate — An automated check of the cooked output: no placeholders, only the mod's own files, materials and physics data present.
- security — A pattern audit of every script, a Microsoft Defender scan, and a check that the package holds only game data files.
- install — Bill approves. The script backs up the current version, installs, hash-checks every file, and restores automatically on failure.
- test — Bill plays it and reports back, often with screenshots. Then the loop goes round again.
Still experimental
- Custom APEX cloth: a self-written cloth-asset generator, with the cloth physics built by the game at load time.
- Wrapping another mod's global script functions.
- Fully unattended overnight builds. REDkit's licence window can stall them.
Step 1 of 8 · plan human gate
The agent writes the plan; Bill approves it.
Who acts here
- 🤖 Claude — builds and installs, with approval
- 🧰 Codex — same powers, never at the same time
- 🧑 Me — and no agent can supply this step.
build →
Step 2 of 8 · build
Assets are built in the sandbox from the agent's own procedural code. CDPR-based assets only, never another mod's.
Who acts here
← plantransfer →
Step 3 of 8 · transfer
Files move to the PC and are MD5-checked. Images are verified pixel for pixel.
Who acts here
- 🤖 Claude — builds and installs, with approval
- 🧰 Codex — same powers, never at the same time
← buildcook →
Step 4 of 8 · cook
REDkit import, cook, buildcache and pack, with every input hash-pinned.
Who acts here
- 🤖 Claude — builds and installs, with approval
- 🧰 Codex — same powers, never at the same time
← transfergate →
Step 5 of 8 · gate
An automated check of the cooked output: no placeholders, only the mod's own files, materials and physics data present.
Who acts here
- 🤖 Claude — builds and installs, with approval
- 🧰 Codex — same powers, never at the same time
← cooksecurity →
Step 6 of 8 · security
A pattern audit of every script, a Microsoft Defender scan, and a check that the package holds only game data files.
Who acts here
- 🤖 Claude — builds and installs, with approval
- 🧰 Codex — same powers, never at the same time
← gateinstall →
Step 7 of 8 · install human gate
Bill approves. The script backs up the current version, installs, hash-checks every file, and restores automatically on failure.
Who acts here
- 🤖 Claude — builds and installs, with approval
- 🧰 Codex — same powers, never at the same time
- 🧑 Me — and no agent can supply this step.
← securitytest →
Step 8 of 8 · test human gate
Bill plays it and reports back, often with screenshots. Then the loop goes round again.
Who acts here
- 🧑 Me — and no agent can supply this step.
← install
