The transit is over before the mind quite catches up. The Wormhole is behind the ship. The client finishes loading the system. The Grid may look empty, and for a moment the familiar windows make the arrival feel almost ordinary.
It is not.
You know that the ship came through this connection. You know the system now shown by the client. You do not yet know whether anyone watched the transit, whether another route is already failing or whether the quiet will last long enough to matter.
Chapter 1 remains inside those first seconds. The task is not to solve the whole system before moving. Leaving the threshold means keeping the difference between what is known, what is suspected and what is still recoverable intact.
Crossing the Threshold
A Stargate delivers a ship into an established network. A Wormhole delivers it through one observed connection. That connection is limited by time and by the mass carried through it. The fact that it worked a moment ago does not promise that it will remain.
Arrival in Anoikis confirms less than it first appears to. It establishes a ship, a system, a connection and a moment. The rest of the route still has to be found.
The familiar interface makes that change easy to miss. The same icons and windows are still in place. Yet a system name no longer places the ship on a route whose next steps are known. An empty participant list no longer gives the warning a pilot may expect. The nearby Wormhole is not infrastructure. Familiar controls are answering narrower questions now.
The system may hold Celestials, Structures, Signatures, active pilots and other connections. Some will be visible. Some will require Scanning or movement. Some may remain hidden. None should be promoted from possibility to fact merely because the screen is quiet.
The Wormhole behind the ship is different. It carries the first useful piece of route knowledge in the new system: it leads back to the place just left. If that meaning is not preserved, the object may remain visible while the return path has already been lost in practice.
Crossing the threshold creates two directions of work. Read what lies ahead. Protect what allows the crossing to be reversed. Moving before either has been done turns a moment without trouble into an assumption of safety.
Read Before Moving
Do not spend the first quiet moment by reflex.
After the jump, post-jump invulnerability protects the ship until a command is given or the protection expires. At the same time, a ten-second Session Change temporarily prevents some actions, including another jump. The two conditions are separate. One protects the ship; the other limits rapid changes of state.
Together they offer time to look. Not safety, and not certainty - simply a brief chance to read the new Grid before choosing what the ship will do next.
The useful question is not “Is anything here?” It is “What can this position show me, and what could still remain outside the answer?”
Several sources begin answering that question:
- the System Identifier states where the client says the ship is;
- the Grid shows objects that are present and visible nearby;
- the Overview presents objects allowed by its current configuration;
- the Wormhole itself confirms the immediate point of return;
- the Probe Scanner presents detectable signatures and anomalies; and
- the Directional Scanner can report selected objects within its configured search.
Preparation decides how much of that moment is available. An Overview can show everything it was configured to show and still hide a category the pilot needs. A scanner window can be accurate and badly arranged. The danger is not that the interface lies. It is that the pilot forgets the limits of the question it was asked.
Read in the order of consequence. A ship on Grid matters before a distant possibility. The return connection matters before an attractive Site. A timer that limits the next action matters before a label that can be interpreted later.
Keep every answer attached to its Source. “No ships are on my Overview” is useful. It describes one display at one moment. “No ships are in the system” claims more than that display can know. In the other direction, a visible Structure confirms an object, not an active owner. Scanner Probes confirm Probes, not the purpose or allegiance of the pilot who launched them. A ship on Grid confirms presence, not intent.
Let each Observation change the picture only as far as it reaches.
Silence Proves Nothing
Local is empty. The sight can feel like an answer because the same window has answered a larger question elsewhere.
In Wormhole Space, pilots do not automatically appear in Local when they enter. They appear after speaking. An empty list therefore describes the conversation, not the population of the system.
That limit belongs in the first arrival picture. A Directional Scanner result with no ships is similarly bounded: the configured scan returned no ship at that moment. Another pilot may be elsewhere or outside what the instrument can show.
Negative observations remain useful when their boundaries travel with them:
- Observed: No ship was reported by this scan from this position at this time.
- Assumed: The system is empty.
The first can support a decision. The second hides the distance between the instrument and the claim. Chapter 9 returns to that distance when the Pathfinder must build awareness without a roster.
Silence is neither safety nor danger by itself. Keep it in the picture, but do not make it speak.
Preserve the Return
The easiest route to underestimate is the one already behind the ship.
At arrival, that Wormhole carries something no other object in the system yet has: a confirmed relationship to the place just left. This makes it the first fixed point on the new map, but it is not permanent. Wormholes are comparatively short-lived, and the total mass they can carry is limited. The connection can age while the scout works. Other ships can pass through without being seen. A route available on entry may later weaken or collapse.
Preserving the return is therefore more than dropping a label. The record must carry enough meaning to survive the moment in which it was made:
- the exact location of the connection on this side;
- the system from which it was reached;
- the time at which the relationship was observed;
- the available evidence about its present condition; and
- the fact that the information may become stale.
Memory quickly turns a sequence into a comfortable story: the route was stable, the system was quiet, the exit was obvious. A record keeps the rough edges that memory removes. It preserves what was known and when. Another pilot inherits that Observation and its age, not the confidence felt by the person who made it.
Later chapters set the conventions for Bookmarks and maps. The principle comes first. A marker without origin, time or meaning may return the ship to an object while failing to explain whether that object is still the route the pilot intends to use.
Before moving away, ask one question: if the next Grid is bad, what lets me reverse this step?
The answer does not guarantee survival. It exposes what the plan depends on. If the answer is only memory, the plan is fragile. If it rests on another pilot’s record, the age and origin of that Report belong to the decision.
Build a Picture
The first decision does not need a complete map. It needs a picture honest enough to show where it is thin.
Return to the quiet arrival: a Structure is on the Overview, Local shows no names and the return connection is still on Grid. A careless summary would be short: “Empty system. Abandoned Structure. Safe exit.”
A field note built from the same moment looks different:
- the structure is visible now;
- its operational state and current users have not been established;
- Local has disclosed no speakers;
- the presence of other pilots remains Unknown; and
- the return connection was usable at the recorded entry time.
The Structure and the Local window are Observed. The connection between the current and previous systems is Derived from the transit. Anything inherited from a Fleet Member or Shared Map is Reported. The presence of silent pilots remains Unknown.
Those labels can change as the situation changes. When the pilot checks a Report, a fresh Observation joins or replaces it. When new evidence closes an Unknown, it may support a Derived conclusion. A clear Grid can remain a true description of the past while becoming useless for the next decision.
The longer field note feels less certain because it refuses to hide its gaps. That is its strength. It shows what can be acted on, what deserves another look and what the current position cannot answer.
Time belongs in that picture. “The Grid was clear” is unfinished without it. Ships move. Pilots enter and leave. Connections age. A timestamp cannot keep a fact fresh; it shows the next pilot how far freshness has been allowed to fade.
First Decisions
The ship must eventually do something. It can return, hold position, move to gather more information or continue deeper. None of those choices is safe in every system, and none is foolish in every system.
Returning protects one kind of certainty while giving up the chance to learn more. Waiting preserves the present Grid but spends time. Moving can improve the picture while revealing the ship to new Grids and new observers. Going deeper increases the value of the route and the dependence on every connection behind it.
Before acting, bring the choice down to four questions:
- What do I know now?
- What am I only assuming?
- What will this action reveal or expose?
- What still lets me reverse it?
The ship and the consequence set the amount of confidence required. A reversible step by a disposable scout can carry more Unknowns than a decision that commits a Fleet or a ship that cannot withdraw easily. The scout’s information is not better. The cost of being wrong is smaller.
If a ship appears on the arrival Grid, its presence is immediate; its intent is not. Range, capability, the Session Change, Fleet support and the loss of post-jump protection may all shape the response. The sighting matters, but it does not issue the command.
If the Grid is clear, Local silent and a broad scan reports no obvious activity, the system has offered fewer warnings - not proof of safety. A low-value scout may continue. A vulnerable or expensive ship may need a stronger return plan. The same view can support different actions because the consequences are different.
This way of thinking should become faster with practice, not slower. The aim is not to hold the ship motionless while every uncertainty is discussed. It is to prevent speed from erasing the question the next action depends on.
Then the cycle begins again. Movement changes scan geometry. Speaking in Local changes what the channel reveals. Warping changes the Grid. Passing through a Wormhole spends time and contributes mass. Every action produces the first observation of the next decision.
Field Principle
The first task in Anoikis is not movement. It is knowing what has been shown, what remains Unknown and what must stay recoverable.
Certainty is not required. Honesty is. An empty Local window must remain an empty Local window, not an empty system. A quiet Grid must remain one quiet Grid. A visible return must remain a temporary connection whose future has not been promised.
That is the welcome Anoikis offers. Geography becomes something pilots keep alive together. Silence becomes an answer with edges. The way Home becomes a condition to protect.
The next chapter looks beyond the arrival Grid and into the geography that makes all of this necessary.