Labs at a glance
The five labs form one progression from a registered root questphase to a community-backed spoken scene. Each lab is a complete, mod-owned WolvenKit project with a start checkpoint, a completed checkpoint, an exact structural contract, and an in-game test guide.
Use the title, namespace, and project name in this table consistently. Lab 1
is the reader-facing number; cqa001 is its resource namespace;
CQA_Lab01_OneShot is its completed WolvenKit and installed-file stem. Those
three names belong to different domains and are not interchangeable.
Reading sequence
| Lab | Canonical title and namespace | Primary boundary | Build and test |
|---|---|---|---|
| 1 | First Signal · cqa001 | Root registration, journal state, real-time delay, one-shot fact | Overview · Author · Test |
| 2 | Signal Race · cqa002 | Immediate selection, pause conditions, parallel listeners, XOR-shaped convergence | Overview · Author · Test |
| 3 | Boundary Check · cqa003 | Streaming block/sector ownership, NodeRefs, marker, nested trigger volumes | Overview · Author · Test |
| 4 | Handoff Point · cqa004 | Registered root, archive-resolved external child, In1/Out1 handoff | Overview · Author · Test |
| 5 | First Contact · cqa005 | Community lifecycle, actor acquisition, one-line scene, named exit, cleanup | Overview · Author · Test |
The topical table of contents places each lab beside the system it teaches, so Lab 4 appears under Questphases before the later-numbered topical sections. The table above is the canonical practical sequence.
For each lab, read its overview, follow Author, then follow Test. Use the intervening system chapters when you need an explanation of a field or behavior; you do not need to read every advanced recipe before continuing.
Checkpoint identity
| Lab | Completed project/file stem | Start ZIP | Completed ZIP |
|---|---|---|---|
| 1 | CQA_Lab01_OneShot | Download | Download |
| 2 | CQA_Lab02_SignalRace | Download | Download |
| 3 | CQA_Lab03_BoundaryCheck | Download | Download |
| 4 | CQA_Lab04_HandoffPoint | Download | Download |
| 5 | CQA_Lab05_FirstContact | Download | Download |
A start and completed checkpoint for the same lab own the same depot paths. They are alternative source states, not two mods to install together. Lab 2’s edited timing variant is another separately unchanged candidate. Install only the candidate named by the current test case, with the game and framework processes closed.
Test one lab at a time. Labs 3–5 share the Allen Street site, so leaving an earlier lab installed can add overlapping triggers, pins, and objectives. Preserve a save from before starting any tutorial: Lab 5 specifically requires that clean lineage, even if you have already completed Labs 1–4 elsewhere.
How to use the checkpoints
All five completed checkpoints pass the repository’s source, graph, package,
and WolvenKit 8.19.0 round-trip checks. Use them to compare resource types,
properties, graphs, paths, and registration with your own work.
All five labs still await in-game acceptance. Their intended runtime behavior is Experimental, including the completed checkpoints.
After authoring, run the linked test guide from the required starting save. Check normal play, streaming, cleanup, and reload as applicable.
Shared practical baseline
The practical guides use Cyberpunk 2077 2.31a, WolvenKit 8.19.0, ArchiveXL
1.27.0, RED4ext 1.30.0, and redscript 0.5.31. See Tested
versions for roles and boundaries. Every runtime campaign
also requires the clean-save and candidate-isolation rules in its own test
page; sharing a tool version does not make two save histories equivalent.
Next: Glossary.