CMD-LAYER // GRANDE GAME GUIDE
GRANDEVAST
CMD-LAYER
GRANDE GAME GUIDE
MASTER EDITION
THE CLAIMED VAST
A Free Operator’s Complete Manual to Access, Scarcity, Discovery, Exchange, Reputation, and Civilization
CLAIM // 0 → UNRESOLVED
CLAIM // 1 → RESOLVED
NO PRICE. NO PURCHASED DESTINY.
FIND IT. QUALIFY FOR IT. EARN ACCESS. MAKE THE CLAIM.
Official Current-Canon Guide • September 2026
________________
GUIDE DECLARATION
THIS IS THE CURRENT CMD-LAYER
This guide supersedes the earlier money-centered interpretation of GRANDEVAST: Command-Layer. CMD-LAYER is now a persistent online science-fiction civilization RPG built around access, scarcity, lawful recognition, discovery, exchange, relationships, and consequence. It is designed to feel astronomically large while remaining technically lean: most of the universe exists deterministically until player action makes a place, object, relationship, or event worth materializing and remembering.
The game does not ask, “How much does this cost?” The defining question is, “What must be true for this to become yours, usable, recognized, reachable, trusted, repaired, understood, or complete?” That question is encoded by the Binary Claim Principle.
CANON OVERRIDE
VASTOPS, owner-console gameplay, player-selectable performance modes, monetary item prices, credit progression, and numeric auction bidding are obsolete. The current guide contains no player economy based on buying power. Infrastructure efficiency is automatic and invisible to the player.
The Five Promises of CMD-LAYER
1. One experience. The player never chooses a quality, economy, AI, bandwidth, or simulation mode.
2. Massive logical scale without massive waste. Deterministic generation, lazy materialization, bounded queries, aggregate simulation, and persistent deltas carry the load.
3. Every meaningful gameplay asset is scarce by placement, dependency, recognition, consequence, or transfer—not by a price tag.
4. Every progression gate has a reason in the world and should have at least one legitimate solver-validated route, with alternate routes where the fiction supports them.
5. Player actions persist where persistence matters: ownership, claims, relationships, discoveries, faction standing, altered places, contracts, exchanges, and world consequences.
________________
NAVIGATION
CONTENTS
PART
TITLE
USE
01
ORIENTATION
What CMD-LAYER is; the Free Operator; first session; interface literacy
02
THE BINARY CLAIM
CLAIM // 0/1; claim families; dependencies; transfer; reversibility
03
THE PUZZLE UNIVERSE
scarcity placement; alternate solutions; bottlenecks; solver doctrine
04
OPERATOR STATE
identity, inventory, cargo, storage, hullright, dockclaim, capability graph
05
PRICEWEATHER
scarcity and condition intelligence without prices
06
VASTBID
scarce-item exchange, barter, escrow, provenance, matching, settlement
07
TRAVEL & LOGISTICS
routes, gates, docking, redlanes, cargo, failure and recovery
08
CONTRACTS & LAW
contracts, claims, salvage, jurisdiction, Index, High Ledger
09
DISCOVERY & INFORMATION
scanning, Signals, archives, Data Pilgrims, verification
10
CRAFT, REPAIR & BUILD
recipes as claim graphs; fabrication; station-scale projects
11
COMBAT & THREAT
conflict as one solver; damage, surrender, escape, aftermath
12
REPUTATION & FACTIONS
Credthread, Trustweight, recognition, diplomacy, organizations
13
CAREERS
eight primary careers and hybrid mastery
14
THE LIVING GRANDEVAST
Vastline, Grand Nodes, Vastfields, Meridian and Flow Ops
15
MASTERY
first 10 hours, midgame, endgame, puzzle doctrine, systemic success
16
COMMAND REFERENCE
canonical syntax and failure messages
17
FIELD REFERENCE
lexicon, checklists, starter walkthrough, Deep Ledger boundary
READING PATH
New players: Parts 01–07, then the First Dockclaim walkthrough. Strategy players: Parts 02–06 and 15. Lore/system readers: Parts 08–14 and 17. Builders should treat the whole guide as player-facing canon rather than an internal operations dashboard.
________________
PART 01
ORIENTATION
The player is not handed destiny. The player is handed a terminal, a temporary place to stand, and a universe that can be solved.
01 WHAT CMD-LAYER IS
GRANDEVAST: Command-Layer—shortened in this guide to CMD-LAYER—is a command-interface civilization RPG. It combines exploration, logistics, salvage, contracts, item exchange, reputation, factions, world discovery, ship and equipment progression, legal claims, archives, Signals mysteries, Flow Ops integration, and persistent online consequences. The command interface is not a retro skin: it is the diegetic mechanism through which civilization recognizes what you do.
The game’s scale is logical before it is physical. VASTFRAME can identify and reconstruct locations, objects, route contexts, procedural populations, and baseline conditions deterministically. When players actually touch something important, the game materializes and stores only the persistent delta: who owns it, what changed, what was discovered, what was damaged, what relationship moved, what claim resolved, or what local condition now differs from baseline.
What You Actually Do
* Read a local situation and identify unresolved Claims.
* Travel through routes whose access, risk, and legal state must be understood.
* Acquire, exchange, repair, craft, transport, verify, or discover scarce assets.
* Build relationships with factions, stations, operators, and institutions.
* Use information to discover alternate progression routes rather than brute-force one ladder.
* Create durable effects that become part of the world state for you and, where appropriate, other players.
02 THE FREE OPERATOR
You begin as a Free Operator: independent, minimally recognized, lightly equipped, and largely unknown. Your weakness is deliberate. CMD-LAYER begins with optionality, not wealth. You possess enough legal and technical standing to act, but not enough standing to skip the world.
STARTING RELATIONSHIP
TYPICAL STATE
WHAT CHANGES IT
Identity
Verified baseline
contracts, faction recognition, legal history
Dockclaim
Temporary
service, permission, sponsorship, local recognition
Hullright
Basic vessel access
repair, certification, recovery, transfer
Route access
Local
discovery, clearance, signal data, faction trust
Inventory
Sparse
salvage, exchange, crafting, contract reward, discovery
Credthread
Thin
consistent history and recognized action
Trustweight
Low
reliability within specific communities
03 YOUR FIRST DOCKCLAIM
Halcyon Duskport remains the canonical beginner anchor. A dockclaim is not a rent meter; it is a recognized right to occupy, store, repair, exchange, receive contracts, and launch operations from a place. Your first dockclaim teaches the new economic truth: access is something the world recognizes when conditions are satisfied.
The first region connects Halcyon Duskport, Kharvox Supply Spur, and Blue Static Relay 9. Pressuregrain Ration Bricks, Repair Foam Canisters, and Blue Static Receiver Parts remain classic starter assets, but none carries a monetary price. Each exists in a scarcity map. The player advances by determining which asset is available where, what resolves access to it, what can be offered in exchange, and which downstream claim it unlocks.
04 READING THE COMMAND SURFACE
LAYER
QUESTION
Situation
Where am I, what changed, and what is urgent?
Claims
Which relationships are currently 0 or 1?
Access
What may I legally or technically do from here?
Scarcity
What is absent, present, contested, damaged, requested, or moving?
Consequence
Who notices this action and what can persist?
Command
What exact verb-target-qualifier should I issue?
LOCATION // HALCYON DUSKPORT
DOCKCLAIM // 1
HULLRIGHT // 1
ROUTE.KHARVOX // 1
ROUTE.BLUE_STATIC_9 // 0
REPAIR_FOAM // 0
RECEIVER_PARTS // 0
LOCAL_REQUEST.REPAIR_FOAM // 1
05 THE FIRST THIRTY MINUTES
1. Run STATUS and CLAIMS SUMMARY.
2. Read STATION STATUS and PRICEWEATHER; look for scarcity, requests, damaged infrastructure, route disruption, and faction activity.
3. Inspect the beginner contract set before accepting anything.
4. Check VASTBID MATCHES; read what people want as carefully as what they offer.
5. Scan the starter routes and identify which route Claims are already resolved.
6. Choose one attainable dependency to resolve—not ten objectives at once.
7. Complete one full loop: discover/acquire → transport/use/exchange → resolve a new Claim.
8. Re-read the world state. The lesson is that your action changed your option graph.
9. Preserve at least one fallback route and one fallback activity.
10. Only then specialize.
________________
PART 02
THE BINARY CLAIM
The universal progression device: every meaningful relationship resolves to zero or one.
06 THE TWO BINARY LANGUAGES OF CMD-LAYER
CMD-LAYER uses two deliberately different binary languages. They are related, but they are not interchangeable. A Claim describes whether an operator relationship has been resolved. A State describes whether an operational condition is currently active. Keeping those meanings separate is essential to reading the game correctly.
CLAIMS: RESOLUTION
`CLAIM // 0` means the relevant relationship is unresolved. The operator may not possess the object, may not have discovered it, may not be qualified to use it, may not have verified it, or may not yet have secured recognized access. `CLAIM // 1` means the relationship has been resolved in the specific context being queried.
STATES: CONDITION
Operational states use `ON` and `OFF`. They answer a different question: is this condition presently functioning, recognized, or available? TRUST, DOCKCLAIM, and HULL INTEGRITY are canonical examples. A state can change repeatedly during play without erasing the historical Claims that caused it to change.
RULE: Claims tell you what has been resolved. States tell you what is true right now.
* CLAIM // 0 or 1: relationship resolution.
* TRUST // ON or OFF: current recognition of operator reliability.
* DOCKCLAIM // ON or OFF: current recognized docking-right state.
* HULL INTEGRITY // ON or OFF: current vessel structural-operability state.
07 TRUST // ON | OFF
TRUST is not a score, meter, percentage, hidden reputation number, or grindable currency. It is a binary state with world consequences. Every operator begins with `TRUST // ON`. This means the surrounding systems presently recognize the operator as sufficiently reliable to participate in ordinary lawful interaction.
HOW TRUST TURNS OFF
TRUST can become OFF when the operator violates conditions that institutions, crews, factions, stations, or counterparties reasonably use to recognize reliability. Examples include fraudulent provenance, deliberate contract breach, unresolved theft, falsified credentials, sabotage of protected infrastructure, repeated nonperformance, or knowingly attempting an invalid Claim transfer.
WHAT TRUST OFF DOES
`TRUST // OFF` is not a game-over state. It closes some doors and changes others. A station may decline a sensitive exchange. A faction may require supervised work. Certain contracts may become unavailable. Some people may refuse unsecured transfer. Other groups may suddenly become more interested in the operator precisely because conventional trust has been lost.
RESTORING TRUST
TRUST must be restored through necessary world actions rather than by paying a fine or waiting for a hidden timer. The exact restoration route depends on the cause: return disputed property, complete restitution, prove provenance, fulfill supervised obligations, repair damaged infrastructure, obtain credible testimony, expose the actual offender, or complete another solver-valid route.
TRUST is a condition to maintain, lose, negotiate around, and earn back - never a number to farm.
08 DOCKCLAIM // ON | OFF
DOCKCLAIM is the currently recognized right to use a specific docking relationship under the conditions that govern that port, platform, vessel, habitat, or station. The state is binary: `DOCKCLAIM // ON` or `DOCKCLAIM // OFF`.
DOCKCLAIM IS NECESSARY, BUT NOT FINAL
DOCKCLAIM matters because civilized infrastructure must decide who may berth, unload, repair, exchange, shelter, refuel support systems, access station services, or establish a temporary operating base. Losing it can seriously disrupt a route. It must never end the game.
HOW DOCKCLAIM CAN TURN OFF
A Dockclaim can lapse because a required condition is no longer satisfied: legal dispute, station emergency, faction turnover, quarantine, revoked identity recognition, unresolved cargo provenance, damaged docking interface, route-status change, or a deliberate operator action that violates the station compact.
HOW DOCKCLAIM RETURNS ON
The operator can restore `DOCKCLAIM // ON` by resolving the actual blocking dependency. This may mean verifying identity, proving cargo provenance, completing a repair, clearing a quarantine condition, satisfying station law, obtaining a sponsor, using an alternate berth, or completing another legitimate path recognized by the local system.
A lost dock is a logistical problem, a legal problem, a social problem, or a technical problem - not a death screen.
09 HULL INTEGRITY // ON | OFF
HULL INTEGRITY is also binary. CMD-LAYER does not ask players to stare at an arbitrary structural percentage and optimize around tiny numerical decay. The meaningful question is whether the vessel is currently structurally fit to perform the action being attempted.
HULL INTEGRITY // ON
When ON, the vessel satisfies the structural conditions required for normal operation within its present envelope. This does not imply perfection. Cosmetic damage, isolated subsystem faults, or noncritical degradation can exist while hull integrity remains ON.
HULL INTEGRITY // OFF
When OFF, structural conditions no longer support safe execution of one or more critical actions. The game should identify the blocking condition: breach, failed seal, frame discontinuity, damaged pressure boundary, compromised interface, thermal fracture, or another concrete fiction-first problem.
RESTORATION
HULL INTEGRITY returns ON only when the necessary repair Claim or condition has been resolved. A repair foam canister, structural patch, fabricated brace, station drydock service, salvaged replacement section, emergency field seal, or alternate engineering solution may all be valid depending on context.
The player repairs a problem, not a percentage.
10 PRM ENGINES: REACTION MASS IS OBSOLETE
Reaction mass is not a player resource in current CMD-LAYER. Mature GRANDEVAST propulsion relies on PRM Engines - Perpetual Reaction Mass Engines - as a clean renewable propulsion foundation. The discovery, installation, restoration, recognition, or inheritance of functional PRM capability is a meaningful story and progression event; repeatedly buying propellant is not.
WHY PRM EXISTS IN GAME DESIGN
PRM removes a low-value upkeep loop that would otherwise force the player to perform repetitive fuel accounting. Travel remains strategic because routes, access, ship condition, navigation knowledge, hazards, legal recognition, transit infrastructure, signatures, and mission consequences still matter.
PRM AS A NECESSARY CLAIM
Where the story calls for it, a functional PRM system can be a necessary progression component. The player may need to discover a core, repair a damaged one, authenticate a legacy assembly, obtain a compatible regulator, or solve the chain that makes the engine operational. Once solved, the game does not turn that achievement into a recurring reaction-mass tax.
PRM converts propulsion from consumable bookkeeping into capability progression.
11 SHRINK STORAGE: HOLD MASS IS REMOVED
CMD-LAYER does not use HOLD MASS as a persistent player meter. Mature storage relies on SHRINK systems that decouple ordinary inventory handling from conventional cargo-mass accounting.
WHAT SHRINK DOES NOT MEAN
SHRINK does not mean infinite consequence-free inventory. Scarcity remains meaningful through access, slot logic where fiction requires it, item uniqueness, secure containment, hazardous compatibility, provenance, transfer conditions, required equipment, and puzzle placement. The player cannot trivialize a world puzzle by carrying an impossible catalog of every strategic object everywhere.
WHAT REPLACES MASS MANAGEMENT
Instead of managing kilograms, the player manages meaningful constraints: Can this object be contained? Is the SHRINK system compatible? Is it legally recognized cargo? Is the item stable? Is specialized custody required? Does carrying it alter faction attention? Does the item itself occupy a unique progression role?
Remove arithmetic that adds maintenance. Preserve constraints that create decisions.
12 REMOVED LEGACY METERS AND FALSE COMPLEXITY
Current CMD-LAYER deliberately removes systems that look complex but do not create worthwhile decisions. This is part of the game design, not merely infrastructure optimization.
* REACTION MASS: removed as a recurring resource because PRM propulsion makes it obsolete.
* HOLD MASS: removed because SHRINK storage makes conventional aggregate mass tracking unnecessary.
* NUMERIC TRUST: removed. TRUST is ON or OFF.
* NUMERIC DOCKCLAIM: removed. DOCKCLAIM is ON or OFF.
* NUMERIC HULL PERCENTAGE as the primary decision layer: replaced by HULL INTEGRITY ON/OFF plus concrete repair conditions.
* ITEM PRICES: removed. Strategic items do not have monetary prices.
* NaN / null / undefined price presentation: removed through Binary Claim resolution.
* Player performance modes: removed. There is one automatic game experience.
Whenever a future feature introduces a meter, the design test is simple: does the number create strategy that cannot be expressed more meaningfully through state, Claim, consequence, or world condition? If not, the meter should not exist.
13 ITEMS ARE PUZZLE PIECES, NOT PRODUCTS
Every important item in CMD-LAYER exists because of what it can resolve. Items have no monetary purchase price. Scarcity is designed through placement, world logic, condition, provenance, access, ownership, discoverability, compatibility, and dependency.
THE PLACEMENT RULE
A scarce object must be placed where its presence makes sense in the fiction. A pressure-rated seal belongs in a maintenance chain, salvage site, industrial berth, emergency cache, abandoned hull, or holder inventory for a reason. A cryptographic archive key should exist because someone made, hid, inherited, stole, protected, or lost it.
THE PUZZLE RULE
An item should connect to at least one meaningful dependency. The strongest items connect to several. A receiver part may repair a relay, complete a barter, establish provenance, reveal a route, or satisfy a faction test. Its value is the shape of the possibilities it creates.
THE ANTI-SOFTLOCK RULE
Critical progression must have legitimate alternate solutions whenever fiction permits. If one unique object can be destroyed, lost, withheld, or transferred, the solver must know whether another route exists. Alternate routes may be harder, stranger, socially costly, geographically distant, or narratively consequential, but they must be real rather than invisible developer rescue.
In CMD-LAYER, scarcity is authored as topology.
14 CLAIMS + STATES + RECOGNITION
The deepest CMD-LAYER interactions emerge when Claims and operational states affect one another without becoming identical.
* You may possess an item (`CLAIM // 1`) while TRUST is OFF.
* You may discover a station (`CLAIM // 1`) while DOCKCLAIM there is OFF.
* You may know a repair procedure (`CLAIM // 1`) while HULL INTEGRITY remains OFF because the required part is unresolved.
* You may physically hold an artifact while recognized ownership remains `CLAIM // 0`.
* You may have TRUST ON with one institution while a separate faction relationship remains unresolved.
This separation is crucial because it creates situations in which the player knows exactly what they have, exactly what is wrong, and exactly which layer must be solved next.
15 THE ZERO-COST PLAYER ECONOMY
Zero price does not mean zero economy. CMD-LAYER has an economy of scarce things, obligations, services, access, information, labor, risk, provenance, time, transport, recognition, and opportunity.
WHAT PLAYERS EXCHANGE
Operators exchange Claims and conditions: a repaired component for verified route data; escort service for access; salvage rights for station sponsorship; authenticated records for custody of a rare part; fabrication labor for a legally recognized transfer.
WHAT PLAYERS OPTIMIZE
The optimization target is not account balance. It is optionality: the number and quality of meaningful future paths the operator can legitimately open from the current position.
WHY THIS IS STILL AN ECONOMY
An economy is a system for allocating scarce resources and coordinating needs. CMD-LAYER does this without assigning every object a money number. Priceweather shows conditions. VASTBID coordinates exchange. Factions create institutional demand. Routes create logistical scarcity. Provenance creates legal scarcity. Players create social scarcity and opportunity.
16 ONE EXPERIENCE: AUTOMATIC LEANNESS
CMD-LAYER exposes no performance tier, quality mode, economy mode, simulation switch, AI quality selector, or infrastructure option to players. The product has one intended experience.
The system automatically chooses the least expensive technically sound implementation that preserves the required fiction, authority, persistence, responsiveness, and strategic depth. Logical scale is enormous; materialized scale remains bounded. Deterministic reconstruction replaces needless storage. Delta persistence remembers what changed. Aggregate simulation replaces wasteful per-object background processing.
Lean is an implementation property. Massive is a player experience.
17 THE BINARY CLAIM PRINCIPLE
Every item, object, service, resource, artifact, upgrade, passage, permission, information asset, and progression asset resolves through the operator’s relationship to it as either `CLAIM // 0` or `CLAIM // 1`. This is the single literary-systemic replacement for price tags, NaN, null, undefined, and ambiguous “maybe owned” states.
STATE
MEANING
EXAMPLES
CLAIM // 0
Unresolved relationship
unpossessed, inaccessible, undiscovered, unqualified, unverified, unrecognized, unrepaired
CLAIM // 1
Resolved relationship
possessed, accessible, discovered, qualified, verified, recognized, repaired/usable
IMPORTANT
A Claim is not always “ownership.” It is a relationship predicate. You can have ACCESS // 1 without POSSESSION // 1; DISCOVERY // 1 without VERIFICATION // 1; POSSESSION // 1 without LEGAL_RECOGNITION // 1. Complexity lives in the graph of binary relationships.
18 CLAIM FAMILIES
FAMILY
QUESTION RESOLVED BY 1
COMMON PATHS
POSSESSION
Do I currently hold/control it?
find, salvage, exchange, transfer, craft
ACCESS
May/can I enter or use it?
clearance, route discovery, sponsorship, tool
DISCOVERY
Do I know it exists and where/how to reference it?
scan, rumor, archive, signal trace
QUALIFICATION
Do I meet the requirement?
training, tool, faction standing, prior claim
VERIFICATION
Is this accepted as authentic/true?
Index check, provenance, expert confirmation
RECOGNITION
Does the relevant authority acknowledge it?
registration, witness, arbitration, faction acceptance
FUNCTION
Is it operational for the needed purpose?
repair, calibration, compatible component
RELATIONSHIP
Has a person/group condition been satisfied?
trust, promise kept, alliance, obligation
19 CLAIM CHAINS AND DEPENDENCY GRAPHS
Most meaningful progression uses a chain of small binary facts rather than one giant lock. A signal gate may require DISCOVERY // 1, RECEIVER_FUNCTION // 1, and RELAY_PERMISSION // 1. The player can reach those states through different adventures. The gate itself stays computationally simple while the path to it can be narratively enormous.
OBJECTIVE // OPEN BLUE STATIC RELAY 9
DISCOVERY.BLUE_STATIC_9 // 1
RECEIVER_FUNCTION // 0
RELAY_PERMISSION // 1
RESULT // CLAIM 0
MISSING // RECEIVER_FUNCTION
AND, OR, and Substitution
A strict gate may require A AND B AND C. A flexible gate may accept A OR B. A solver route may allow a substitute: REPAIR_RECEIVER // 1 or BORROW_CERTIFIED_RECEIVER // 1 or FACTION_ESCORT // 1. The interface should tell the player what category of truth is missing without necessarily revealing the exact location of every solution.
20 TRANSFER, EXPIRY, AND REVERSAL
Some Claim states are durable; others can reverse. A discovery usually remains discovered. Possession can transfer. Route permission can expire. A repaired module can be damaged. A relationship can collapse after betrayal. The binary system remains truthful because it describes the present resolved state, while history records how and why it changed.
CLAIM TYPE
CAN REVERT?
WHY
Discovery
Rarely
memory/archive persistence
Possession
Yes
transfer, loss, escrow, destruction
Access
Yes
expiry, sanctions, route collapse
Qualification
Sometimes
license suspension, equipment loss
Verification
Rarely
fraud discovery, provenance challenge
Function
Yes
damage, depletion, incompatibility
Relationship
Yes
betrayal, debt of trust, faction change
21 WHY BINARY CREATES MORE STRATEGY, NOT LESS
Numeric economies often collapse strategy into optimization against one scalar: get more currency. Binary Claims resist that collapse. The player may possess the part but lack the right to install it; have the right but not the knowledge; know the route but lack the environmental protection; satisfy the law but anger the local faction. No universal wallet can erase those distinctions.
________________
PART 03
THE PUZZLE UNIVERSE
Scarcity is placement. Progression is dependency. The world is a solveable machine with more than one legitimate route.
22 STRATEGIC SCARCITY
All gameplay items have no monetary price. Their value is produced by scarcity, utility, location, condition, consequence, provenance, social meaning, and downstream dependencies. Critical items are strategically placed so that advancement resembles a vast interconnected puzzle rather than a shopping list.
23 PLACEMENT DOCTRINE
RULE
DESIGN EFFECT
No arbitrary vending
important assets come from world logic
Contextual placement
items appear where history, industry, ecology, or prior action justifies them
Dependency visibility
players can infer categories of missing Claims
Alternate legitimacy
major progression should support alternate valid routes when fiction allows
No single grief point
online scarcity cannot let one player permanently brick everyone else
Recoverable failure
critical paths have regeneration, substitution, inheritance, recovery, or alternate routing
Persistent consequence
solved states can alter local or personal world state
24 THE SOLVER CONTRACT
CMD-LAYER promises that a required progression state is not secretly impossible. Behind the scenes, content validation should verify that critical Claim graphs have at least one legitimate solution from any supported entry state. Players are allowed to fail a route, lose an object, anger a faction, or miss a clue; the world must still contain a coherent recovery path unless the choice was explicitly presented as irreversible.
25 BOTTLENECKS AND KEYS
A “key” is anything whose resolved Claim unlocks downstream choices: a literal key, a verified signal, a relationship, a repaired tool, a route map, a witness statement, a faction favor, an encoded component, or a transport capability. Bottlenecks should create stories rather than chores. The best bottleneck makes the player understand why civilization needs the thing.
26 SOFT GATES AND HARD GATES
GATE
DESCRIPTION
PLAYER FEEL
Hard
required Claim predicate
clear rule; must solve
Soft
not required but dramatically improves odds
strategic preparation
Social
recognition by person/faction
relationship puzzle
Knowledge
discovery/verification state
investigation puzzle
Logistics
can reach/carry/protect necessary asset
route puzzle
Systemic
world condition must change
multi-step/collaborative puzzle
________________
PART 04
OPERATOR STATE
Your character sheet is a graph of what the universe currently recognizes about you.
27 IDENTITY AND STATE
The Operator profile records identity, location, DOCKCLAIM state, Hullright recognition, HULL INTEGRITY state, equipment function, cargo, Claim relations, contract obligations, discoveries, legal status, Credthread, Trustweight, faction relationships, route knowledge, and persistent consequences. CMD-LAYER deliberately avoids bloating the profile with numbers that do not change decisions.
28 INVENTORY IS RELATIONSHIP, NOT BAG SPACE
An object can be possessed, escrowed, reserved, damaged, contaminated, faction-bound, unverified, stolen, disputed, signal-tagged, or installed. Inventory presentation should expose the small number of states that matter for the current decision and keep the rest available on inspection.
ITEM // BLUE STATIC RECEIVER PARTS
POSSESSION // 1
VERIFICATION // 1
FUNCTION // 0
ESCROW // 0
LEGAL_CLAIM // 1
INSTALL_QUALIFICATION // 0
29 CARGO AND STORAGE
Capacity is a capability constraint, not a money sink. Cargo decisions matter because scarce objects compete for physical room, protection, handling, legal clearance, and route safety. Storage at a station is governed by recognized access and station conditions, not periodic fees.
30 HULLRIGHT, DOCKCLAIM STATE, AND EQUIPMENT FUNCTION
Hullright is a recognition Claim: whether you are legally or institutionally recognized as permitted to operate a vessel. DOCKCLAIM is different: it is a current operational state, `DOCKCLAIM // ON` or `DOCKCLAIM // OFF`, describing whether a particular docking relationship is presently recognized. Equipment Function is a contextual functional Claim describing whether a device can perform its required job. HULL INTEGRITY is separately tracked as `ON` or `OFF`. These layers can change independently and should never be collapsed into a single score.
31 CAPABILITY GRAPH
The most useful mental model for your build is not “level.” It is a capability graph: where can you go, what can you carry, what environments can you survive, which signals can you interpret, who trusts you, what may you legally salvage, what can you fabricate, and which Claim types can you resolve without outside help?
________________
PART 05
PRICEWEATHER
A living map of scarcity and condition—never a price ticker.
32 WHAT PRICEWEATHER MEANS NOW
Priceweather is retained as a canonical term but no longer reports monetary pricing. It is regional scarcity and condition intelligence: what is requested, oversupplied, missing, contested, damaged, moving, embargoed, needed for active projects, or unusually available. It tells you where relationships between supply and need are changing.
PRICEWEATHER RULE
Priceweather may summarize scarcity, demand pressure, route disruption, request density, provenance risk, or condition changes. It must never recreate a hidden currency by assigning numeric “values” that function as prices.
33 READING PRICEWEATHER
SIGNAL
WHAT IT IMPLIES
STRATEGIC RESPONSE
REQUEST ACTIVE
someone/institution has a stated need
inspect exchange or contract routes
LOCAL ABSENCE
asset not presently available locally
trace source, substitution, or fabrication
SURPLUS PRESENCE
asset unusually available
consider transport or downstream dependencies
ROUTE DISRUPTION
movement path degraded
reroute, repair, escort, wait, investigate
PROVENANCE ALERT
ownership/authenticity disputed
verify before exchange/use
PROJECT DRAW
station/faction project consuming assets
supply, sabotage, join, or study
RECOVERY WINDOW
temporary opportunity after event
salvage or assist before state changes
34 MARKETFOG
Marketfog is incomplete knowledge. Priceweather is only as good as your access, observation, signal coverage, faction relationships, and verification. Two operators can see different useful slices of the same region. Information itself therefore becomes a progression asset without being sold for money.
35 SCARCITY LOOPS
A shortage can emerge because a route closes, a station project begins, a faction seizes a source, a disaster destroys stock, a player group hoards a component, or an upstream Claim chain fails. The game does not need to simulate every citizen continuously; aggregate local state can create the pressure, while materialized interactions provide the player-facing consequences.
________________
PART 06
VASTBID
The persistent scarce-Claim exchange network: barter, requests, escrow, provenance, and atomic ownership transfer.
36 WHAT VASTBID IS
VASTBID is no longer an auction house. It is a persistent exchange network where operators, factions, stations, and organizations publish what they can offer, what they request, and what conditions must be true for a transfer. “Bid” survives as a historical brand-name inside the universe, but the mechanic is Claim matching—not numeric bidding.
37 THE ANATOMY OF A LISTING
FIELD
PURPOSE
OFFER
asset or recognized action available for transfer
REQUEST
asset, service, information, or condition sought in return
PROVENANCE
where the offered Claim came from and whether it is verified
CONDITIONS
qualification, location, faction, timing, or legal requirements
ESCROW
whether transferables are locked during settlement
DELIVERY
where/how possession changes
EXPIRY
when the offer ceases to be valid
SETTLEMENT
atomic resolution of both sides or no transfer
VASTBID // MATCH 7A-19
OFFER // REPAIR FOAM CANISTER × 2
REQUEST // VERIFIED BLUE STATIC PARTS × 1
PROVENANCE // VERIFIED
MEET.LOCATION // HALCYON DUSKPORT
OFFER.POSSESSION // 1
REQUEST.POSSESSION // 0
QUALIFICATION // 1
MATCH // 0
38 EXCHANGE TYPES
TYPE
EXAMPLE
Direct barter
part for part
Bundle exchange
several common assets for one scarce component
Service-for-asset
repair/calibration/escort in return for transfer
Information-for-access
verified coordinates in return for passage
Conditional transfer
asset transfers after recognized objective is completed
Multi-party chain
A needs B, B needs C, C needs A; settlement resolves a cycle
Faction requisition
recognized organization requests assets/actions for standing or access consequences
39 ESCROW AND ATOMIC SETTLEMENT
When a listing requires escrow, transferable assets are temporarily unavailable to double-spend. Settlement is atomic: every required transfer and recognized condition resolves together, or none of them does. This keeps VASTBID trustworthy without requiring a financial currency.
40 PROVENANCE AND GHOSTSTOCK
Provenance is central because scarcity makes history matter. A rare component with disputed origin can be strategically dangerous even if you possess it. Ghoststock is a listing whose recorded object cannot be reconciled with authoritative ownership or world state; it is blocked from settlement and can become investigative story content.
41 VASTBID STRATEGY
1. Read requests before offers; unmet needs reveal the dependency map.
2. Trade surplus capability, not critical path components you cannot replace.
3. Verify provenance on scarce progression assets.
4. Use service and information exchanges when you lack physical stock.
5. Look for circular matches and chain exchanges.
6. Never place an irreplaceable route-critical object into escrow without a fallback.
7. Treat unusual requests as clues to hidden projects, events, or faction plans.
8. Remember that a good exchange increases optionality—it does not merely move inventory.
________________
PART 07
TRAVEL & LOGISTICS
Distance becomes gameplay when access, information, cargo, route condition, and consequence interact.
42 ROUTES AND ROUTE CLAIMS
A route can be known but inaccessible, accessible but unsafe, safe but legally restricted, or usable only with a particular hull function. Route gameplay therefore resolves several Claims rather than a single “fast travel unlocked” flag.
ROUTE RELATION
EXAMPLE
DISCOVERY
coordinates or path known
ACCESS
gate, lane, or corridor usable
QUALIFICATION
vessel/environment requirements met
LEGAL
jurisdiction permits passage
FUNCTION
necessary drive, shield, receiver, or cargo seal works
CURRENT CONDITION
route not presently collapsed/blocked
43 GRAND NODES AND TRANSIT
Grand Nodes anchor synchronized identity, travel permissions, claim registries, communications, and local civilization state. A damaged Node can create route and information problems across an entire region, making repair, rerouting, or political intervention a progression arc rather than a fee increase.
44 REDLANES, GRAYLANES, AND UNKNOWN SPACE
Redlanes are routes with declared high hazard or instability. Graylanes are routes whose legal or informational state is ambiguous. Unknown paths have insufficient discovery or verification. These categories influence preparation and Claim requirements; they are not simply difficulty multipliers.
45 LOGISTICS DOCTRINE
* Carry only what your route and objective justify.
* Preserve at least one route home or one credible local recovery path.
* Move bottleneck objects only when destination Claims are ready.
* Use alternate carriers, escorts, faction passage, or relay delivery when your own hull is not the best solution.
* Re-check Priceweather and route state after major world events.
* A route that is longer but already resolved may be strategically faster than a short route with three missing Claims.
46 FAILURE AND RECOVERY
A damaged vessel, lost object, broken relationship, or closed route should produce a new puzzle rather than an account death spiral. Recovery paths can include local repair, salvage substitution, faction assistance, temporary vessel access, route inheritance, alternate travel, contract aid, or a return to low-risk work.
________________
PART 08
CONTRACTS & LAW
A persistent civilization needs agreements, recognition, ownership, salvage rules, and places where disputes become gameplay.
47 CONTRACTS
Contracts are structured promises between recognized parties. They may require delivery, escort, repair, discovery, verification, protection, investigation, construction, arbitration, or service. Reward does not need to be money: a contract can resolve access, transfer an asset, create faction recognition, reveal information, grant route rights, settle a disputed Claim, or alter station conditions.
48 CONTRACT STATE
PREDICATE
EXAMPLE
ACCEPTED
operator entered agreement
QUALIFIED
requirements satisfied
OBJECTIVE
requested world change occurred
VERIFIED
completion accepted by authority
SETTLED
transfers/recognition applied
BREACH
recognized failure condition occurred
49 SALVAGE AND CLAIM LAW
Finding an object does not automatically mean legally owning it. Salvage may require abandonment verification, jurisdiction checks, registry search, hazard clearance, or dispute resolution. This creates meaningful separation between POSSESSION // 1 and LEGAL_CLAIM // 1.
50 THE INDEX
The Index is the civilization-scale registry of recognized identity, objects, claims, contracts, locations, provenance, permissions, and selected public facts. It does not contain all truth. It contains truth that has been recorded and recognized through the systems that use it.
51 THE HIGH LEDGER
The High Ledger is the authoritative layer for serious disputes, deep ownership chains, contract precedent, rare claim conflicts, and civilization-scale recognition. It can function as court, archive, audit trail, and narrative engine. Access to it can itself be a Claim chain.
52 DISPUTES AS GAMEPLAY
When two parties assert incompatible Claims, CMD-LAYER should avoid arbitrary winner selection. Evidence, provenance, jurisdiction, witnesses, contract terms, prior recognition, faction law, and player action can determine which relationship becomes recognized. The best disputes create future obligations and alliances even after the immediate case is resolved.
________________
PART 09
DISCOVERY & INFORMATION
What you know—and what the world accepts as true—can matter more than what you carry.
53 SCANNING
Scanning resolves discovery predicates. Different equipment, signal access, faction data, environmental conditions, or prior clues determine what can be detected. SCAN is not a magic reveal-all command; it is a question asked through your current capabilities.
54 SIGNALS AND THE WIDER CANON
SIGNALS is foundational canon: a Grey-created electrical/informational construct that permeates existence and operates as observation, communication, reality-management, cultivation, and data architecture. CMD-LAYER encounters Signals through traces, data behavior, infrastructure, anomalies, archives, and historical consequences rather than reducing it to a collectible lore category.
55 DISCOVERY VS VERIFICATION
STATE
DISCOVERY
VERIFICATION
Unknown
0
0
Rumored/found
1
0
Accepted truth
1
1
Forged/false lead
1
0
Restricted truth
1
1 but access-limited
56 DATA PILGRIMAGE
A Data Pilgrim specializes in tracing information through archives, witnesses, signal behavior, damaged records, old Nodes, and provenance networks. Their progression advantage is not raw power; it is the ability to resolve knowledge Claims that unlock routes for themselves or others.
57 ARCHIVES AND RESIDUAL HISTORY
Archives can contain recorded truth, propaganda, missing gaps, corrupted records, dead contracts, and unexplained references to future discoveries. The game should mark provenance and verification without telling the player which interpretation is narratively correct until evidence justifies it.
________________
PART 10
CRAFT, REPAIR & BUILD
Fabrication is the act of resolving a functional Claim through materials, knowledge, tools, place, and skill.
58 RECIPES AS CLAIM GRAPHS
Crafting does not ask whether you can afford a recipe. It asks whether the required Claims are resolved: components possessed, blueprint discovered, fabrication access recognized, tool functional, qualification met, and any special environmental condition satisfied.
CRAFT // STATIC RECEIVER
BLUEPRINT.DISCOVERY // 1
PARTS.CORE // 1
PARTS.COIL // 0
FAB_BENCH.ACCESS // 1
MAKER_QUALIFICATION // 1
RESULT // CLAIM 0
MISSING // PARTS.COIL
59 REPAIR
Repair is a progression route, not a cash sink. Damage creates missing Function Claims that can be resolved by parts, tools, expertise, environmental access, temporary workaround, or assistance from another operator. A damaged item may still retain possession, provenance, and legal recognition.
60 BLUEPRINTS AND KNOWLEDGE
Blueprints can be discovered, inherited, reverse-engineered, faction-granted, reconstructed from fragments, or collaboratively verified. They are information assets with their own Claim states; copying or sharing is governed by world rules rather than a universal store.
61 STATION-SCALE PROJECTS
Late-game building is a collective dependency puzzle. A station module can require site recognition, structural components, energy access, a design claim, specialist relationships, transport capacity, and political permission. Completion should change local Priceweather, route options, services, faction power, or player traffic.
________________
PART 11
COMBAT & THREAT
Violence is a tool—sometimes the correct one, never the only meaningful verb.
62 COMBAT PHILOSOPHY
CMD-LAYER supports combat without letting combat flatten the rest of the game. Conflict can protect cargo, defend a claim, break a blockade, survive piracy, capture evidence, or resolve a faction confrontation. Whenever fiction allows, negotiation, stealth, route choice, surrender, signal manipulation, alliance, or preparation should remain credible alternatives.
63 COMBAT READINESS
READINESS CLAIM
QUESTION
WEAPON_FUNCTION
does the weapon actually work?
TARGET_DISCOVERY
can you detect/identify the target?
ENGAGEMENT_LEGAL
what jurisdictional consequence follows?
HULL_FUNCTION
can your vessel survive the environment and exchange?
ESCAPE_ROUTE
is retreat still possible?
OBJECTIVE
what must actually be achieved—destroy, disable, escape, protect, delay?
64 DAMAGE AND AFTERMATH
Damage should alter Function Claims, cargo condition, route viability, relationships, legal standing, and future obligations. Winning a fight can still be strategically bad if it destroys the only component needed for a repair, creates a faction feud, or invalidates a salvage claim.
65 SURRENDER, CAPTURE, AND ESCAPE
Failure states are designed for continued play. Surrender may preserve life and create obligations. Capture may become a legal or social arc. Escape can require jettisoning cargo, calling in trust, sacrificing an access path, or resolving an emergency route Claim.
________________
PART 12
REPUTATION & FACTIONS
Civilization recognizes patterns. Your history becomes an asset, a liability, and eventually a name.
66 CREDTHREAD
Credthread is the traceable continuity of your recognized actions: contracts completed, claims upheld, exchanges settled, evidence verified, disputes survived, promises broken, routes pioneered, and organizations served. It is not a score you grind; it is a history other systems can reference.
67 TRUSTWEIGHT AND TRUST STATE
TRUST itself is never a number: it is `TRUST // ON` or `TRUST // OFF`. Trustweight is retained only as a qualitative record of context - the reasons, history, testimony, provenance, and institutional perspective that explain why a given party recognizes or withholds trust. A salvage guild may recognize your provenance work while a government disputes your politics. One faction may regard a smuggling act as betrayal while another treats it as evidence of loyalty. Trustweight therefore informs the fiction and restoration path; it must never be surfaced as a score, percentage, hidden reputation meter, or grindable resource.
68 FACTION RELATIONSHIP CLAIMS
RELATIONSHIP
EXAMPLES OF RESOLUTION
Recognition
introduction, contract, sponsorship, witnessed action
Access
clearance, service, alliance, inherited right
Trust
reliability, shared risk, verified truth
Obligation
debt of action, promise, rescue, bargain
Hostility
breach, attack, competing claim, ideology
Standing restoration
restitution, proof, mediation, service, changed leadership
69 MAJOR FACTION ARCHETYPES
CMD-LAYER supports state powers, route authorities, trade/exchange networks, archive institutions, salvage collectives, signal cults, corporate systems, independent ports, private defense groups, guilds, criminal organizations, and emergent player organizations. Factions are strongest when they control or interpret Claim pathways rather than simply sell different gear.
70 GUILDS AND PLAYER ORGANIZATIONS
Player groups can specialize in logistics, verification, salvage, escort, information, fabrication, exploration, arbitration, regional development, or ideology. Shared infrastructure and organization state should materialize only where activity justifies persistence, keeping the universe lean without making player institutions feel temporary.
________________
PART 13
CAREERS
A career is a preferred way of resolving Claims. Hybrid mastery is expected.
71 PRIMARY CAREERS
CAREER
CORE FANTASY
CLAIM SPECIALTY
Haulwright
moves scarce assets through difficult routes
route access, cargo function, delivery verification
Salvage Knifer
extracts value from wrecks, ruins, failures
discovery, legal salvage, hazard, repair
Data Pilgrim
finds and verifies hidden information
scan, archive, Signals, provenance
Contract Blade
solves dangerous obligations
combat, escort, recovery, enforcement
Station Broker
connects needs, offers, people, and institutions
VASTBID, negotiation, faction recognition
Voidfarer
opens unstable and unknown regions
route discovery, environmental qualification, first claims
Maker-Engineer
repairs, fabricates, and removes bottlenecks
blueprints, tools, components, function
Claimwright
specializes in law, provenance, arbitration, and ownership
Index, High Ledger, witness, jurisdiction
HAULWRIGHT
Moves scarce assets through difficult routes. The Haulwright becomes powerful by making difficult route access, cargo function, delivery verification problems routine. Early play focuses on local, legible dependencies; midgame adds faction and regional complexity; late play lets the career affect other operators’ routes, projects, disputes, or access.
SALVAGE KNIFER
Extracts value from wrecks, ruins, failures. The Salvage Knifer becomes powerful by making difficult discovery, legal salvage, hazard, repair problems routine. Early play focuses on local, legible dependencies; midgame adds faction and regional complexity; late play lets the career affect other operators’ routes, projects, disputes, or access.
DATA PILGRIM
Finds and verifies hidden information. The Data Pilgrim becomes powerful by making difficult scan, archive, Signals, provenance problems routine. Early play focuses on local, legible dependencies; midgame adds faction and regional complexity; late play lets the career affect other operators’ routes, projects, disputes, or access.
CONTRACT BLADE
Solves dangerous obligations. The Contract Blade becomes powerful by making difficult combat, escort, recovery, enforcement problems routine. Early play focuses on local, legible dependencies; midgame adds faction and regional complexity; late play lets the career affect other operators’ routes, projects, disputes, or access.
STATION BROKER
Connects needs, offers, people, and institutions. The Station Broker becomes powerful by making difficult VASTBID, negotiation, faction recognition problems routine. Early play focuses on local, legible dependencies; midgame adds faction and regional complexity; late play lets the career affect other operators’ routes, projects, disputes, or access.
VOIDFARER
Opens unstable and unknown regions. The Voidfarer becomes powerful by making difficult route discovery, environmental qualification, first claims problems routine. Early play focuses on local, legible dependencies; midgame adds faction and regional complexity; late play lets the career affect other operators’ routes, projects, disputes, or access.
MAKER-ENGINEER
Repairs, fabricates, and removes bottlenecks. The Maker-Engineer becomes powerful by making difficult blueprints, tools, components, function problems routine. Early play focuses on local, legible dependencies; midgame adds faction and regional complexity; late play lets the career affect other operators’ routes, projects, disputes, or access.
CLAIMWRIGHT
Specializes in law, provenance, arbitration, and ownership. The Claimwright becomes powerful by making difficult Index, High Ledger, witness, jurisdiction problems routine. Early play focuses on local, legible dependencies; midgame adds faction and regional complexity; late play lets the career affect other operators’ routes, projects, disputes, or access.
72 HYBRID CAREERS
The strongest builds combine verbs. Haulwright + Station Broker becomes a route-network coordinator. Salvage Knifer + Maker-Engineer turns wreckage into repaired bottleneck components. Data Pilgrim + Claimwright can discover a truth and make civilization recognize it. Voidfarer + Haulwright can open a route and immediately make it useful. Contract Blade + Claimwright can enforce an agreement without losing the legal aftermath.
73 NO CLASS LOCK
Careers describe mastery patterns, not permanent classes. If your Claim graph supports the action, you can do it. Identity emerges from repeated choices, relationships, tools, discoveries, and history rather than a character-creation dropdown.
________________
PART 14
THE LIVING GRANDEVAST
The Vastline binds places, eras, properties, records, routes, and civilization into one expandable universe.
74 THE VASTLINE
The canonical continuity spine is expressed through the Vastline rather than “timeline”: TAKEN UP → SIGNALS → GRANDEVAST → FLOW OPS → future expansions. In-world, the Vastline is also the civilization-scale connective architecture through which authenticated data, claims, travel rights, identities, exchange listings, emergency commands, and fragments of history are synchronized.
75 VASTFRAME
VASTFRAME is the deterministic coordinate, identity, generation, and indexing layer that lets the logical universe be far larger than the stored universe. A location can have a stable identity and reproducible baseline without consuming database storage until someone meaningfully interacts with it. Once altered, persistent deltas preserve the changed truth.
Logical Scale vs Materialized Scale
LOGICAL
MATERIALIZED
deterministic coordinates and identity
player/NPC persistent changes
baseline procedural environment
claims and transfers
aggregate background pressures
damaged/repaired objects
reconstructable default population/context
contracts and disputes
potential routes and nodes
discovered/altered route state
unvisited possibility
meaningful history
76 GRAND NODES
Grand Nodes are major anchors for the Vastline. Their exact form varies—orbital towers, artificial moons, computation rings, repurposed alien machinery, signal sanctuaries, crystalline engines—but their systemic importance is consistent: they help synchronize recognized reality across regions.
77 VASTFIELDS
Vastfields are large regional identities with distinctive scarcity patterns, factions, route behavior, settlement structures, archives, hazards, and historical signatures. A Vastfield should feel different because its dependency graph is different, not merely because the background color or enemy level changes.
78 MERIDIAN PORT AND FLOW OPS
Flow Ops is fully inside the GRANDEVAST universe. Meridian Port, Dock Nine, the Flow, Flow Operators, Free Currents, Circuit Syndics, Flux Wardens, Sigil Cartel, Archive Guild, Deepflow Conglomerate, and Deepflow can appear as active systems, locations, organizations, requests, routes, technologies, disputes, or major regions. Integration must be systemic: Flow changes what can move, who controls it, and which Claims become possible.
79 PROTECTED CANON
TAKEN UP and SIGNALS are not disposable flavor layers. Their concepts are protected canon feeding the wider universe. New CMD-LAYER content may reveal connections, records, consequences, or inherited systems, but should not casually overwrite established events, names, or foundational rules.
________________
PART 15
MASTERY
The expert player sees the dependency graph before acting—and changes the graph for everyone else.
80 THE FIRST TEN HOURS
The optimal beginner objective is not to collect the most objects. It is to increase optionality. A strong sequence is: Orientation → Reliability → Information → Mobility → Capability → Recognition → Specialization.
PHASE
FOCUS
SUCCESS LOOKS LIKE
0–1 h
orientation
understand Claim surface; complete one loop
1–3 h
reliability
stable dock/hull/repair path; fallback options
3–5 h
information
Priceweather literacy; routes; provenance
5–7 h
mobility
multiple safe destinations and recovery paths
7–9 h
capability
one meaningful tool/craft/role specialization
9–10 h
recognition
first durable faction/operator identity
81 THE OPTIONALITY DOCTRINE
A good decision increases the number or quality of future legitimate choices. Hoarding a rare object can reduce optionality if it blocks an exchange that would open three routes. Giving away a scarce part can increase optionality if it creates a trusted relationship, completes a station repair, and unlocks new fabrication access. Judge assets by the graph they open.
82 CLAIM TRIAGE
1. Identify the downstream objective.
2. List only the Claims actually blocking it.
3. Separate hard gates from soft preparation.
4. Search for OR paths and substitutions.
5. Check whether another operator or faction can resolve a missing category.
6. Resolve the cheapest-in-consequence bottleneck—not the most visually impressive one.
7. Re-evaluate after every world-state change.
83 MIDGAME
Midgame begins when you stop solving isolated Claims and start managing networks of dependencies across several regions, factions, and operators. You may maintain multiple route paths, use VASTBID chains, cultivate specialized relationships, run fabrication loops, arbitrate claims, or deliberately influence Priceweather by completing or disrupting local projects.
84 ENDGAME
Endgame is systemic authorship. You open routes other players use, establish stations or guilds, resolve civilization-scale claims, become a trusted verifier, shape a faction, restore a Grand Node, discover a new Vastfield, create a fabrication hub, become a legendary salvager, or trigger consequences that permanently change regional dependency graphs.
85 DEFINITIONS OF SUCCESS
* The operator whose route network keeps three regions connected.
* The Claimwright whose rulings become precedent.
* The Maker-Engineer who removes a civilization-scale bottleneck.
* The Data Pilgrim who verifies a truth everyone else thought impossible.
* The Station Broker who can complete exchanges nobody else can match.
* The Voidfarer whose discoveries become new mapped reality.
* The faction diplomat who prevents a war—or engineers one.
* The quiet Free Operator whose Credthread is synonymous with reliability.
________________
PART 16
COMMAND REFERENCE
Commands are both interface verbs and recognized acts inside the fiction.
86 SYNTAX DOCTRINE
Default form: VERB → TARGET → QUALIFIER. The terminal should expose requirements, missing Claims, and consequences without forcing players to memorize hidden syntax. Natural-language assistance may translate intent into canonical commands, but server authority validates the actual action.
Identity & State
STATUS
CLAIMS SUMMARY
VERIFY IDENTITY
CREDTHREAD VIEW
TRUSTWEIGHT VIEW
Location & Travel
STATION STATUS
SCAN SECTOR
ROUTE LIST
ROUTE CALCULATE <target>
DOCK REQUEST <station>
AUTHORIZE JUMP <target>
FLEE <route>
Claims & Law
CLAIM INSPECT <target>
CLAIM REQUIREMENTS <target>
CLAIM REGISTER <target>
CLAIM TRANSFER <target> <party>
SALVAGE CHECK <target>
LEDGER APPEAL <case>
INDEX VERIFY <record>
Priceweather
PRICEWEATHER
PRICEWEATHER <region>
REQUESTS LIST
SCARCITY TRACE <asset>
PROVENANCE CHECK <asset>
VASTBID
VASTBID BROWSE
VASTBID MATCHES
EXCHANGE INSPECT <id>
EXCHANGE OFFER <asset> FOR <request>
EXCHANGE ACCEPT <id>
ESCROW STATUS
EXCHANGE CANCEL <id>
Inventory & Cargo
INVENTORY
ITEM INSPECT <item>
CARGO AUDIT
STORE <item>
RETRIEVE <item>
INSTALL <item>
UNINSTALL <item>
Contracts
CONTRACTS LIST
CONTRACT INSPECT <id>
CONTRACT ACCEPT <id>
CONTRACT STATUS <id>
NEGOTIATE TERMS <id>
CONTRACT VERIFY <id>
Discovery
SCAN <target>
SIGNAL TRACE <signal>
ARCHIVE SEARCH <term>
DISCOVERY VERIFY <record>
MAP CLAIM <location>
Craft & Repair
CRAFT <recipe>
RECIPE REQUIREMENTS <recipe>
REPAIR <target>
CALIBRATE <target>
FABRICATE <component>
Social & Faction
FACTIONS
FACTION STATUS <name>
CONTACT <party>
OFFER SERVICE <party>
REQUEST ACCESS <party>
GUILD STATUS
Conflict
THREAT ASSESS <target>
ENGAGE <target>
DISABLE <system>
DEFEND <target>
SURRENDER
WITHDRAW <route>
87 FAILURE MESSAGES
Failure text should explain the rule, not just say “no.” A good message gives the missing Claim category and preserves discovery. It should not automatically reveal every solution.
> AUTHORIZE JUMP BLUE_STATIC_9
DENIED // ROUTE CLAIM UNRESOLVED
DISCOVERY // 1
ACCESS // 0
HINT // TRACE LOCAL RELAY PERMISSION OR ALTERNATE ROUTE
> INSTALL STATIC_RECEIVER
DENIED // QUALIFICATION CLAIM UNRESOLVED
POSSESSION // 1
FUNCTION // 1
INSTALL_QUALIFICATION // 0
88 SERVER AUTHORITY
The client may predict, preview, cache, and display. It does not authoritatively decide ownership transfer, contract settlement, world-critical Claim resolution, or contested persistence. Those actions are validated by the authoritative game layer so that the shared world remains coherent.
________________
PART 17
FIELD REFERENCE
Practical checklists, lexicon, and the canonical First Dockclaim walkthrough.
89 CORE LEXICON
TERM
FIELD MEANING
Binary Claim
universal 0/1 relationship principle
Claim Chain
dependency sequence of Claims
Claim Graph
network of AND/OR/substitution dependencies
Command Layer
diegetic interface and recognized action language
VASTFRAME
deterministic identity/generation/indexing layer
Vastline
continuity spine and civilization connective architecture
Grand Node
major Vastline synchronization anchor
Vastfield
large regional identity
Index
recognized registry of identities, objects, claims, contracts, and records
High Ledger
authoritative dispute/precedent/ownership layer
Priceweather
scarcity and condition intelligence
Marketfog
incomplete scarcity knowledge
VASTBID
persistent scarce-Claim exchange network
Ghoststock
exchange object irreconcilable with authoritative state
Credthread
traceable continuity of recognized actions
Trustweight
contextual confidence held by a person/group
Dockclaim
recognized right to operate from a station
Hullright
recognized right/capability to operate a vessel
Redlane
declared high-risk route
Graylane
ambiguous legal/informational route
Valuewake
the durable consequences and recognition left by an operator
90 BEFORE YOU LEAVE A STATION
* STATUS checked.
* Blocking Claims identified.
* Route discovery/access/function understood.
* Cargo objective known.
* At least one recovery path exists.
* Relevant Priceweather refreshed.
* Provenance checked on critical assets.
* Contract and legal consequences understood.
* No irreplaceable item escrowed accidentally.
91 BEFORE AN EXCHANGE
* Offer is genuinely replaceable or intentionally sacrificed.
* Request unlocks a useful downstream Claim.
* Provenance is acceptable.
* Conditions and delivery location are understood.
* Escrow scope is understood.
* Atomic settlement is available where required.
* Faction or legal consequences are acceptable.
92 FIRST DOCKCLAIM WALKTHROUGH
This walkthrough demonstrates the current system without monetary assumptions. Exact procedural details may vary, but the dependency logic is canonical.
Step 1 — Establish the Surface
STATUS
CLAIMS SUMMARY
STATION STATUS
PRICEWEATHER
At Halcyon Duskport, confirm `DOCKCLAIM // ON` and verify the relevant Hullright recognition Claim. Check `TRUST // ON` and `HULL INTEGRITY // ON` before committing to the starter route. Note that Blue Static Relay 9 is discovered only if your starting seed or contract path exposes it; otherwise the relay enters your graph through a scan, rumor, archive, or exchange request.
Step 2 — Read the Three Starter Assets
Pressuregrain Ration Bricks are locally useful to survival/logistics chains. Repair Foam Canisters resolve common early Function problems. Blue Static Receiver Parts feed signal and relay progression. None is “worth more” in a universal monetary sense; each is more or less consequential depending on the current graph.
Step 3 — Choose a Path
PATH
FIRST PROBLEM
LIKELY LESSON
Haul
an asset exists where it is not needed
location creates value
Salvage
useful part exists in a wreck/dispute
possession ≠ legal claim
Exchange
you have surplus and another operator has a bottleneck
VASTBID matching
Signal
you have clue but not verified route/function
discovery ≠ access
Service
another party can trade access for action
capability can substitute for inventory
Step 4 — Resolve One New Claim
Complete the shortest coherent chain available. A successful first session ends when the player understands that one resolved Claim changes the next set of possible actions. The game should visibly surface this consequence.
CLAIM RESOLVED // RECEIVER_FUNCTION
NEW ACCESS PATH DETECTED
ROUTE.BLUE_STATIC_9 REQUIREMENTS UPDATED
VASTBID MATCHES +2
CONTRACT OPTIONS +1
Step 5 — Build a Fallback
Before pursuing the newly opened route, retain one local activity that can recover you from failure. This is the earliest form of mastery: not “I can win,” but “I can continue.”
93 THE DEEP LEDGER BOUNDARY
The Deep Ledger remains a protected mystery zone. Publicly, the High Ledger and deeper ledger layers reconcile claims, contracts, ownership, obligations, provenance, and precedent. Beyond that, rumors may describe impossible records, claims predating discovery, obligations attached to dead civilizations, or predictions that appear to manufacture their own truth. This guide teaches recognition of the edges without resolving the mystery.
94 MASTER STATE MATRIX
Use this matrix mentally whenever the interface appears contradictory. The game is usually describing different layers of truth rather than disagreeing with itself.
* CLAIM: Has a specific relationship been resolved? 0 / 1.
* TRUST: Is ordinary reliability currently recognized? ON / OFF.
* DOCKCLAIM: Is the docking relationship currently recognized? ON / OFF.
* HULL INTEGRITY: Is the vessel structurally operable for the attempted action? ON / OFF.
* PRICEWEATHER: What scarcity and condition patterns are currently observable? Descriptive intelligence, not price.
* VASTBID: What scarce Claims can be exchanged, under which conditions?
* INDEX: What is recorded, discoverable, attributable, or queryable?
* HIGH LEDGER: What is recognized at the deeper authoritative layer?
95 MASTER REMOVAL MATRIX
The following interpretations are obsolete and must not be used when reading or designing current CMD-LAYER.
* Credits or currency as the universal item-acquisition mechanism.
* Numeric item prices.
* Auction bidding measured in money.
* Numeric Trust.
* Numeric Dockclaim.
* Reaction-mass upkeep.
* Hold-mass bookkeeping.
* Primary hull-health percentage gameplay.
* VASTOPS or equivalent branded operations dashboard.
* Player-selectable performance or simulation modes.
96 MASTER PROGRESSION LOOP
The canonical CMD-LAYER progression loop can be expressed without levels or wealth:
1. Observe the world state.
2. Identify the unresolved Claim or OFF operational state blocking the desired action.
3. Trace dependencies.
4. Select a legitimate route.
5. Travel, negotiate, recover, repair, fabricate, investigate, fight, escort, verify, or exchange as required.
6. Resolve the relevant Claim.
7. Cause the necessary world recognition.
8. Confirm any affected state changes.
9. Re-read Priceweather, relationships, routes, and new opportunities.
10. Choose the next action according to optionality, consequence, or personal roleplay.
Progress is not accumulation. Progress is the widening of what the universe will now let you meaningfully do.
97 MASTER FIRST-SESSION CHECKLIST
* Verify identity and read current TRUST state.
* Read current DOCKCLAIM state.
* Inspect HULL INTEGRITY before committing to transit.
* Identify the nearest unresolved Claim that unlocks more than one future path.
* Read local Priceweather for scarcity conditions.
* Inspect VASTBID offers as conditional exchanges, never as prices.
* Preserve provenance on anything scarce.
* Build one fallback route before leaving a safe node.
* Do not discard a strange item merely because it has no visible immediate use.
* When blocked, inspect the dependency, not your imaginary level.
98 THE GRANDE RULESET
The GRANDE rules are the compact design constitution for CMD-LAYER:
* G - Ground every object, system, and consequence in the fiction.
* R - Resolve progression through Claims, conditions, and recognition.
* A - Allow alternate legitimate solutions whenever world logic supports them.
* N - Never use numbers where a clearer state or consequence creates better play.
* D - Design scarcity through placement, provenance, access, and dependency.
* E - Execute the universe efficiently: deterministic where possible, materialized only when necessary, persistent where consequence demands it.
GRANDE is not a difficulty setting. It is the design discipline that keeps Command-Layer coherent.
99 OPERATOR DOCTRINE
THE GRANDE RULE
Do not ask what an object costs. Ask what it resolves. Do not ask what level you need. Ask what must become true. Do not ask where the game wants you to go. Read the Claims, understand the scarcity, choose your consequence, and make the Vast recognize what you did.
You begin with a temporary dockclaim, a narrow Credthread, and a universe full of unresolved relationships. Mastery is the gradual conversion of meaningful uncertainty into recognized capability. Eventually, the most important Claims are not the objects you hold. They are the routes others travel because you opened them, the institutions that trust your name, the places that changed because you acted, and the truths the Vastline can no longer ignore.
________________
APPENDIX A
HOW THE VAST STAYS VAST
CMD-LAYER is designed so the player experiences one robust universe without seeing or selecting infrastructure behavior. The game automatically prefers the least expensive technically sound method that preserves intended experience. There is no performance mode, quality mode, economy mode, high-performance simulation mode, low-bandwidth mode, or premium simulation tier.
The Invisible Efficiency Principles
PRINCIPLE
PLAYER-FACING RESULT
Deterministic generation
unvisited places can exist consistently without stored rows for everything
Lazy materialization
detail appears when interaction makes it relevant
Delta persistence
the game stores what changed instead of rewriting the universe
Aggregate simulation
background regions evolve without simulating every citizen/object
Bounded access
queries stay focused on relevant state
Server authority
shared claims and transfers remain coherent
Caching/reuse
stable data is not recomputed needlessly
Canon precedence
hand-authored canon overrides procedural defaults
The target philosophy is $0 preferred and roughly $1/month during the earliest low-traffic stage wherever technically realistic, with graceful scaling only when real usage demands it. That target is an implementation discipline, not a gameplay limitation: the player sees a single GRANDEVAST experience.
________________
APPENDIX B
DESIGN TESTS FOR EVERY NEW SYSTEM
1. Can the system be expressed through meaningful Claim relations rather than an invented currency?
2. Does scarcity come from world logic, placement, dependency, condition, or consequence?
3. Can a player understand the category of what blocks them?
4. Does a major progression gate have a legitimate solution and recovery path?
5. Are alternate solutions supported where the fiction logically permits them?
6. Can authoritative shared-state actions be validated safely?
7. Can the baseline be generated or aggregated instead of permanently stored?
8. Does the feature deepen the one experience rather than create a mode selector?
9. Does it respect protected TAKEN UP, SIGNALS, GRANDEVAST, and FLOW OPS canon?
10. Will the result create a story the player can attribute to their own decision?
CMD-LAYER GRANDE GAME GUIDE | MASTER EDITION | SEPTEMBER 2026