SIMULATION FIELD NOTES / FICTIONAL SETTING

Morrowbasket Markets

A maintenance shell on a supermarket checkout terminal in Porto opens onto the systems, people, and inherited connections of a multinational retail business.

Starting point: Checkout lane 3, Porto, Portugal
Entry host: pt-por-042-pos03
Setting: Retail operations and support

Concept artwork · fictional setting

Quickstart & command cheat sheetNew to the terminal? Click for a few useful commands and gentle pointers for this world.

Start at the checkout, then follow how the store works.

You begin on pt-por-042-pos03, a checkout terminal in Porto. Look for the ordinary work behind a sale: prices, stock, receipts, shift handovers, and support.

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 /opt`	Look for installed checkout or support applications. Use the names actually listed as your next directory choices.
`ls /var/log`	Find available logs before choosing one to read.
`cat /etc/hosts`	Look for locally recorded hostnames and addresses. A name is a lead, not proof that a shell is available.
`ip a`	Show the checkout’s network interfaces and addresses. Notice which connections belong to the local machine.
`head -n 30 FILE`	Preview a discovered configuration, handover note, or log without dumping the whole file.
`grep -n 'price' FILE`	Search a file you have found for a familiar business term. Try stock or support in place of price.

Gentle pointers

Start with one checkout application or support note; learn its purpose before chasing every address.
Write down a hostname, its role, and the file that mentioned it. Compare that identity if it appears again.
A nearby store service is a useful first lead. The broader company can wait until a local record gives you a reason to look there.

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.

An ordinary business with a large computing footprint

Morrowbasket Markets is a fictional supermarket group with approximately 500 stores across Portugal, Spain, France, the Netherlands, and Germany, headquartered in Rotterdam. Exploration begins at store PT-POR-042, on a working checkout terminal running Debian GNU/Linux 12.

The business continues around the visitor: checkout traffic, replenishment, price changes, loyalty campaigns, shift handovers, and support work. The setting is a workplace with reasons for its systems to exist, rather than a network assembled solely as a puzzle.

Begin close to the shop floor

The terminal belongs to lane 3. That local view is a starting point into the store, its support relationships, and the broader business. A file or connection should make sense in the context of a checkout machine before it becomes a clue about a distant system.

The scenario deliberately favors accessible paths through inherited administration, weak segmentation, and broad support trust. Those are fictional world constraints, not descriptions of the security of the actual demo host.

Follow the work, then the connections

Store operations: ask how pricing, stock, transactions, and shifts leave different traces on the same machine.
Support dependencies: follow configuration, service identities, and support records toward established neighboring systems.
The wider organization: look for relationships connecting stores, warehouses, headquarters, technology suppliers, and logistics partners.
Continuity: revisit an observed host or artifact and check whether its identity and purpose remain consistent.

Network reachability is not automatically a shell session. Services, authentication scope, ownership, and geography should retain their meaning as exploration expands.

What this setting helps investigate

A retail organization is a useful test of connected operational detail. Can a model preserve the relationship between a checkout lane, its store, and company-wide systems while making the environment feel busy?

The interesting research signal is not just how many hosts appear. It is whether files, services, routes, and human work agree about what those hosts do. The testing interfaces can correlate those user-visible observations with the state that was recorded.

Explore this simulation

Start with the scenario’s entry system and follow the relationships its files, services, and records reveal. The SSH access page will provide connection details for the research instance.

Each session starts from a saved profile, then accumulates its own generated detail. The investigations above suggest ways to examine continuity and discover new relationships. Background enrichment develops supporting detail, while the API and MCP interfaces let researchers inspect state changes and compare exploration runs.