SIMULATION FIELD NOTES / FICTIONAL SETTING

Common Ground Colonyship

A centuries-old colonyship has reached a destination already settled by a later, faster expedition. Start at a public terminal in a community that still calls the ship home.

Setting year: 2796
Location: High orbit around Meridian, Tau Ceti
Entry host: hearth-c17 · public terminal

Concept artwork · fictional setting

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

Start with public information and everyday life aboard.

You begin on hearth-c17, a shared public terminal near a laundry and lending room. Learn what a resident can see before trying to reach specialist systems.

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
`cat /etc/motd`	Read the login notice if one exists. It may explain local services or conventions.
`ls /`	See the top-level directories and look for public or shared information.
`ls /srv`	Check for locally hosted services or shared material; this directory may be absent or sparse.
`ls /usr/local/bin`	Look for locally installed programs. Follow any usage notes you discover rather than guessing an application’s controls.
`cat /etc/hosts`	Look for named systems the terminal already knows about.
`grep -n 'integration' FILE`	Search a discovered notice, archive, or document for a link between shipboard life and the destination.

Gentle pointers

Public notices, lending records, community services, and archives are useful ways into the world.
Compare an older record with a current one. Note who wrote each and when, rather than treating either as the whole story.
Follow one named service or institution at a time. A public terminal does not automatically carry engineering privileges.

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.

Arrival did not mean an empty frontier

After approximately 414 years in transit, Common Ground arrived in 2794 to find an established human civilization at its destination. A faster expedition launched generations later had founded that society in 2638.

Two years into integration, roughly 32,000 ship residents are connecting carefully maintained information systems to a wealthier, more advanced destination society. Most have never lived anywhere else. The ship remains a functioning, self-governing home.

A resident’s view, not an engineering console

The first terminal is beside the laundry and lending room in Hearth residential district, Ring B, Deck 12. The public-access session can introduce shipboard services, historical collections, notices, and new off-ship connections through ordinary computing.

This starting point makes daily life a useful lens on a large speculative world. Maintenance, education, work, art, friendship, and disagreement should be visible through the systems people use.

Look for the joins between two societies

Everyday services: explore community information and the ordinary applications available from a shared terminal.
Historical continuity: compare archival material with the ship's present circumstances.
Technical integration: investigate compatibility problems, service discovery, translation, and access boundaries.
Different perspectives: follow correspondence and public records without treating one viewpoint as the world's omniscient narrator.

Neither travel nor communication exceeds light speed. Distance, bandwidth, stale information, maintenance, and authorization remain meaningful constraints. The destination is the fictional world Meridian in the real Tau Ceti stellar system.

World building beyond infrastructure inventories

This scenario tests whether a computing environment can express an inhabited society. A technically detailed directory tree is only part of the challenge: the records and applications should also agree about history, institutions, and what matters to the people using them.

Integration is an open civic question, not a mandatory quest. DREAMLAND admin direction establishes that premise, while foreground emulation and enrichment must preserve it as new detail appears.

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.