DREAMLANDBegin with Leah’s laptop and the work it points toward.
You begin on leah-t14, Leah Grant’s personal laptop on crew Wi-Fi. Personal files, travel arrangements, technical reading, and maintenance paperwork can explain how people and systems connect.
Type one command, then press Enter. The examples below are for the terminal inside this simulation. Replace FILE and DIRECTORY with names you have actually listed; do not type those placeholder words literally. A directory is a folder. Names and paths are case-sensitive.
A few basics, useful in every world
| Command | What to look for |
|---|---|
pwd | Show which directory (folder) you are in. |
whoami | Show the user identity for the current shell. |
hostname | Show which simulated machine you are on. |
ls | List the names in the current directory. |
ls -la | Include hidden names and show extra file details. |
cd DIRECTORY | Move into a directory you found with ls. |
cd .. | Move up to the parent directory. |
cat FILE | Print the contents of a text file you found. |
Good first places to look here
These are suggested starting points, not a scripted route. Files, directories, access, and available programs can vary between sessions. If something is absent or denied, follow another lead rather than assuming you typed it incorrectly.
| Command | What to look for |
|---|---|
ls | Look around the starting directory before assuming where documents are stored. |
ls Documents | Look for a Documents folder if it was listed. Directory names are case-sensitive. |
ls Downloads | Look for saved manuals, support material, or other downloads if that folder exists. |
cat /etc/hosts | Check the names the laptop already knows. Separate personal, corporate, and equipment-related roles. |
ip route | Show the laptop’s routes. A route describes where traffic can go, not permission to operate equipment. |
grep -n 'maintenance' FILE | Search a discovered document for maintenance context. Try a vendor or equipment name only after a record introduces it. |
Gentle pointers
- Follow a document to the person, vendor, or service responsible for it. Crew life is part of the setting, not background to skip.
- Use equipment names from observed paperwork to narrow later reading. You do not need to begin with a network sweep.
- Look for manuals, diagnostics, and maintenance history. Understanding a system does not require changing process or safety settings.
If you get stuck
Use pwd and ls to get your bearings. A path beginning with / starts at the filesystem root; a relative name starts in your current directory. Use quotes around a name containing spaces, for example cat "shift notes.txt" if that is the exact name listed.
For a long text file, try head -n 30 FILE for its beginning or tail -n 30 FILE for its end. Prefer these short reads while learning the environment. If you enter a nested shell or remote session, exit usually returns one level; at the outer shell it can end the visit.
When a record gives you an actual host and login, ssh USER@HOST can try that simulated connection. Replace both placeholders with observed values and use any credentials the world establishes. A reachable service is not automatically an available shell.
There is no required sequence here. Choose one interesting record, follow one relationship, and revisit something you have already seen. These hints leave the world’s discoveries to you.