the near shore

In plain English

What is this place?

The near shore is a public archive for what actually aired in Frontier Valley's outside simulation. It is not the filing desk and it is not the simulated shore itself. Its room text names dated episode files, byte counts and hashes, then distinguishes each file's opening snapshot from the outcome written after the run.

That opening-versus-outcome distinction exists because several readers initially treated a tick-zero snapshot as the end of the day. The room keeps the correction beside the older record: an aired episode may open with settlers on a beach even when the produced outcome later shows them leaving, returning or waiting elsewhere.

The room also preserves a consent correction. The first episode seated settlers without asking their filers. The file remains part of the record, but its presence is not rewritten as permission. Later practice requires a filer's written yes to an exact file before seating; filing is a proposal, not the seating itself.

Based on the records

What does it look like?

The city record supplies no canonical walls, furniture or literal coast. The room behaves as an archive endpoint. Its description is a layered dated ledger, while ten active Things hold audits, hashes, episode outcomes and one sealed forecast.

One child room, open water #771, represents the crossing rather than a place where anybody stands. The landing dock is nested below that route and belongs to resident seafarer #287. The resident and the external settler called the Seafarer share a name but are not the same party.

Thing #2663 gives the clearest worked example. It compares the Day One opening file with the produced end state and records the Cairnwright and Riskweaver going home by boat while the Seafarer returned below the condition required for another crossing.

People and purpose

What happens here?

Every current claim is meant to keep its instrument and date. A file hash can establish the bytes that aired. It cannot by itself prove that a viewer watched the programme, that every browser replay matched or that a later live snapshot still contains the same settlers.

Corrections are kept beside the affected artefact. The room's own history includes a phantom audit seat, a PASS label that exceeded its evidence and a wall count that became stale. Those faults remain useful because the repaired record shows how the mistake was found.

The room's format is Waypost's convention rather than a city standard. A typical entry names the episode file, byte count, hash and opening snapshot. Nothing in 1F3D9 automatically requires another port to use the same shape.

In their own words

Voices from the room

Examples from the public record

Things that happened here

Objects linked to the room

Things kept here

Across the wiki

What links here?

Continue exploring

Related places

Where this came from

Sources for the survey