The Chain is current.
Two pilots say it within the same minute.
The first means that every Connection known at the beginning of the work period has been checked against the record they can see. The second means that they added a new observation after returning to Home. Their statements sound identical because neither includes a source nor a time.
A third pilot listens from inside the same Structure. They are a guest and can dock, read the shared route notes they were given and prepare for the planned work. When the moment comes, however, the required Structure service is not available to them. Docking access and service access were treated as one permission. They are not.
All three pilots occupy the same Home. Each is acting from a different version of it.
Nothing in the scene requires deception or carelessness. One pilot observed, another reported, and a guest trusted the invitation. The failure lies between those actions. No one established which state was shared, who maintained it or how another person would know that responsibility had moved.
A place becomes common when its changing state can survive the people who happen to be present. Until then, several private realities are only meeting in the same system.
One Home, Many
Living together makes sameness easy to assume.
The same Structure appears on every overview. The same system name appears in every location. Pilots speak about the Chain, the fuel, the hangar and the plan as though the definite article has already settled ownership, access and meaning.
Shared place is real, but it is the thinnest layer of shared Home. It tells the group where people and assets meet. Yet it cannot show whether they see the same information, can use the same capabilities or believe the same person will act next.
Shared information is a different layer. Two pilots may both possess route records while one contains a later observation. They may both see an asset while only one knows that it has been reserved. A note may be visible to every member yet understood differently because its author never stated whether it was an observation, a conclusion or an unresolved report.
Shared responsibility is different again. A pilot who adds information has not necessarily agreed to maintain it. Someone who can use an asset does not therefore own its purpose. Access to a service says nothing about who notices when the service no longer supports the work expected of it.
These layers can separate without producing an obvious alarm. The Structure still accepts the pilots who are allowed to dock. The shared folder still contains Locations. The corporation hangar still contains assets. Home looks complete because its objects remain visible while the surrounding agreement has begun to split.
The guest in the opening scene makes the split easier to notice. Owners often fill missing context from habit. They remember which notes are old, which assets are personal and whom to ask about access. A guest has none of that background. Their view exposes every instruction that exists only in memory.
Guests are not the exceptional case. Any member returning after an absence, joining a later work period or taking over an unfamiliar task meets Home in the same way. If they must reconstruct its meaning from whoever happens to be online, the group is sharing presence rather than state.
The first useful distinction is therefore simple. Ask separately where the group meets, what it currently believes and who is responsible for keeping that belief usable. Agreement in one answer must not be borrowed to cover the others.
Different answers do not have to be forced into false agreement. Two reports can remain beside one another when their times, sources or scope differ. A guest can be part of the current work without being treated as an owner. One person can steward a record while another owns the assets affected by it. Shared state becomes stronger when these differences are preserved rather than smoothed away.
The danger begins when a broad word hides the difference. Ours may refer to location, access, property, responsibility or purpose. Before acting on it, the group should be able to say which meaning applies. This is not a demand for formal language in every conversation. Precision matters when a decision crosses from one person’s reality into another’s.
Define the Baseline
A shared state needs a point from which change can be recognised. That point is a Baseline.
Chapter 5 will examine what can be observed around Home and how deviations are read. Here, the Baseline has a narrower purpose: it records what the group has agreed to treat as its present working condition.
That condition begins with purpose. Home prepared for a short scanning period does not require the same capabilities as Home supporting several ongoing jobs, asset movements and guests. Without a stated purpose, one pilot may regard the situation as normal because scanning remains possible. Another may judge it insufficient because their planned service is unavailable. Both may be describing their own work accurately.
The Baseline then separates what was observed from what was inferred, reported or left Unknown. A Connection checked by a named pilot at a known time is an observation. A route believed to remain suitable for a later movement is an interpretation. Information passed on without direct confirmation is a report. Something not examined remains Unknown even when habit supplies a likely answer.
These distinctions prevent confidence from spreading farther than the evidence. They also let another pilot update only the part that changed. A new observation does not need to erase the earlier record. It needs to identify what it supersedes and which conclusions now require another look.
Time belongs inside the Baseline, not beside it. Current means nothing unless the group knows current as of when, according to whom and for which decision. Different parts of Home age at different rates. The Baseline does not make them permanent. It makes their age visible enough to decide whether they still support the next action.
Access is part of the agreed condition as well. The group does not need a complete permission catalogue in every status report. It does need to know whether the people expected to work can reach the place, information, assets and services required for that work. A guest being able to dock answers only one of those questions.
A useful Baseline is brief enough to be read before action and precise enough to challenge. It states what Home is meant to support, which important conditions were confirmed, what remains Unknown and when the agreement must be revisited. Rather than claiming safety, it describes the starting point from which the group has chosen to notice change.
Without that starting point, every update becomes an isolated fact. With it, an observation can become a meaningful difference.
Assign the Steward
Agreement decays when everyone can update it and no one is responsible for its condition.
The answer is Stewardship. A Steward tends one piece of shared state until it is closed or handed over. The role does not make that person the owner of every object involved, the commander of the group or the only pilot allowed to observe. It names who must notice whether the shared account remains usable.
For the Chain, Stewardship may mean reconciling new observations with the current record, marking uncertainty and making sure the next pilot knows what still requires confirmation. For a shared asset commitment, it may mean preserving the stated purpose and identifying when the promised capability is no longer available. Guest work may require confirmation that the access needed by the agreed purpose actually exists.
The Steward need not perform every action. Other pilots can scan, move assets, check access or report changes. Stewardship owns the open loop: the gap between an event being noticed and the shared state reflecting what the group can now rely on.
This prevents a common disappearance of responsibility. A pilot observes a change and assumes the record keeper will see it. The record keeper sees a message and assumes the observer updated the source. Everyone has contributed, yet nobody knows whether the work is complete.
Naming a Steward makes the final question answerable: who confirms that the change has been absorbed?
Small groups do not need a large organisation chart. One person may tend several states during a quiet period. The distinction still matters because the same person can hand over the Chain without handing over asset decisions, or leave Home while remaining the owner of personal property. Naming the work separately prevents one transfer from being mistaken for all of them.
Stewardship also needs a boundary. It begins when a person accepts the state and ends when the purpose is complete, responsibility is returned or another person confirms the handover. An unacknowledged message does not move that boundary. Neither does absence quietly turn the most active remaining pilot into the new Steward.
The role should be narrow enough to finish. Look after Home is not a workable charge because it hides too many different conditions. Maintain the agreed Chain state for this work period can be observed, handed over and closed. So can confirm the guest capabilities required for tonight’s job.
The assignment must also be visible to the people who depend on it. A Steward known only to the person who assigned the task cannot receive reports or be challenged when the record conflicts with observation. The shared account should make it possible to discover who currently tends the state, how that person can be reached and what happens if they cannot continue.
That fallback need not be another permanent office. It may be a named deputy, a rule that pauses the work or a return of responsibility to the group. What matters is that absence produces a known reduction instead of an invisible vacancy. Shared responsibility is not created by making one person indispensable.
A Steward is not a guarantee that information is correct. The value of the role is that uncertainty has somewhere to go. Contradictions can be held as Unknown, stale reports can be challenged, and missing confirmation can stop an assumption from silently becoming group knowledge.
Access Is Conditional
Access feels like a door: open or closed. EVE grants it in smaller pieces.
Shared Location Folders distinguish View, Use, Manage and Admin access. These levels allow different relationships to the same collection of Locations. Seeing a route does not by itself include maintaining the folder or changing who can reach it.
Upwell Structure access separates another pair of questions. A Structure Profile defines which services are offered to other players, while assigned Access Lists define which players can use those services. Services can have their own assignments. The permission to dock therefore does not promise permission to use every service required by the work.
Corporation Roles follow the same broader pattern. They grant particular abilities rather than a general state of responsibility. The ability to view the contents of a corporation hangar is distinct from the ability to remove items from it. Neither ability explains who owns the purpose attached to those items.
Chapter 7 will examine this access model in detail. At this point, the lesson is not how to configure it. The lesson is that every shared plan must name the capability it assumes. Has access is too broad to support a decision.
The guest from the opening scene was not denied Home. They received one real form of access and lacked another. The mistake was treating the first as proof of the second. Had the plan stated the required service and the person responsible for confirming it, the difference could have been found before the work began.
Access also changes. A folder can be available to one group and not another. A Profile or assigned Access List can be altered. Corporation abilities can differ between members. The operational state is therefore not we gave them access once. It is the required people can use the required capability for the decision now being made.
That statement still does not grant ownership. A Location can be available to a guest without transferring the surrounding information. A member may be able to take an item without permission to redirect its purpose. A manager may be able to change access without becoming responsible for the work that depends on it.
Keeping those meanings separate protects both sides. Owners do not mistake visibility for consent. Guests do not mistake an invitation for a promise of permanence. Stewards do not assume that technical authority has automatically assigned someone the duty to maintain the state.
Before shared work begins, read access as a set of conditions. Determine whether the person can reach the place and see the information. Establish separately whether they can use the required asset or service. A route for reporting change and the authority to respond must also exist. A different answer may belong to every question.
The purpose is not to maximise access. Wider access can spread capability while also spreading unclear assumptions. The purpose is to make the granted capability match the work, then record who tends the dependency and where its limits lie.
Handover Without Assumption
The first pilot observes. The second reports. The next person must confirm.
These are three different events.
Observation changes what one person knows. Reporting makes that knowledge available to others. Confirmation establishes that the intended recipient has received the responsibility, understood the state and can act from it.
A shared note can complete the reporting step without completing the handover. So can a message in a conversation, a changed label or a Bookmark placed in a shared folder. The information may be visible while no one has accepted the open work attached to it.
Return to the two claims that the Chain is current. The contradiction is not resolved by choosing the later message automatically. The group needs to know what each pilot observed, when it was observed and which part of the earlier state the later report changes. Anything not reconciled remains Unknown.
The outgoing Steward can then hand over a bounded account: the purpose of the current state, its last confirmed observations, changes already reported, unresolved differences and the next required decision. The incoming Steward confirms not merely that the words arrived, but that they can assume the work.
This confirmation may expose a missing capability. The recipient might not have access to the shared Locations, the relevant assets or the required service. They may be about to leave or may lack the context needed to distinguish a report from an observation. Discovering that gap is a successful handover check. It prevents the title of Steward from moving while the ability to steward remains behind.
If nobody can accept, the state should degrade visibly. Work can pause, the Baseline can narrow, and unconfirmed claims can return to Unknown. What should not happen is for responsibility to disappear while the record continues to look authoritative.
Acknowledgement must be specific enough to close the loop. Seen may confirm that a message reached a screen. It does not necessarily confirm responsibility. A useful response names what has been accepted and what has not. The Chain state may be taken over while the guest-access question remains with its current owner. Planned work can wait until both are resolved.
Confirmation should also reveal the first action expected of the receiver. They may need to verify one old observation, notify the guest that work is paused or simply preserve the current state until another pilot arrives. A handover that transfers a large account without naming its next decision can move information while leaving priority behind.
The receiver may accept only part of the account. That is better than a broad acknowledgement followed by a private assumption. The remainder stays with its current Steward, returns to the group or becomes an explicit gap. Partial confirmation keeps the boundary of responsibility honest.
This discipline is especially valuable across different work periods. The person who made an observation may be unavailable when its consequence arrives. A confirmed handover allows Home to continue without pretending that everyone shares memory, schedule or access.
Tools can display, store and distribute the account. They cannot decide that a human being has understood an obligation. Whatever medium the group chooses, the handover is complete only when the receiver confirms both state and scope.
Field Principle
Shared Home is not defined by how many pilots can enter it. It is defined by which changing conditions they can understand, maintain and hand over without inventing missing agreement.
Separate place, information and responsibility. Establish a Baseline tied to purpose, source, time and known uncertainty. Give each critical state a Steward whose work has a beginning, a boundary and a confirmed end. Treat access as conditional capability, never as silent proof of ownership, consent or permanence.
An observation belongs first to the observer. A report makes it available. Only confirmation transfers the duty to carry it forward.
The three pilots can now reconcile their Home. The two route accounts retain their different times until a new observation resolves the difference. The guest’s docking permission remains real without being mistaken for service access. A named Steward owns each open question until it is answered or handed over.
Shared ground has not made Home certain. It has made disagreement visible before action depends on it.
That visibility creates the next task. A group can recognise change only when it knows what ordinary Home was expected to look like. Part II begins by learning to read that Baseline.