Base roster
Some threats are just part of the week or tied to difficulty. They are not deep secrets.
Layers
Three things get mixed together in most public unlock guides
Split them apart and the whole progression path becomes calmer.
Salvage expansion
Other additions come from free-roam choices and reshape later nights or route access.
Permanent secrets
The secret chain and true completion goals sit above a single weekly run and need deliberate planning.
Safe order
The safest path to 100 percent is staged, not heroic
First learn the office, then branch saves, then clean up deep secrets.
Stage one
Learn the normal week and keep early clears readable before chasing every side condition.
Stage two
Once endings make sense, keep route saves instead of trying to improvise every path in one go.
Stage three
Use unlock logic only after you know whether the run is really a salvage build, mask build, or true-ending project.
Triage
Unlock problems get easier once you ask which layer is actually failing.
Most messy save files are not broken everywhere. They are broken in one layer and misunderstood in two others.
Roster question
If the confusion is about who should already be available, stay in the base-roster layer first. Do not jump straight to secret logic.
Route question
If the unlock issue only matters because you are chasing a specific ending branch, move into the matching route page before you keep reading unlock lists out of context.
Completion question
If the real goal is 100 percent or true-ending cleanup, treat the save like a long project with staged checkpoints instead of one heroic all-in run.
Save hygiene
A clean unlock guide should help you keep the save readable, not just give you more things to chase.
Why branching saves helps
Branch saves reduce the classic problem where a player can no longer tell whether a route failed because of office play, salvage choices, or permanent secret progress. Cleaner saves make every later guide easier to trust.
Why this page belongs in the system cluster
This page adds value by separating unlock logic from endings, bosses, and roster summaries. It should make the project calmer. If it ever turns into one giant checklist with no boundaries, it stops helping.