Readable before commitment
Verified cause, intended outcome, committed equipment, and worst-case loss are shown before launch.
System mapCONTEXTUAL COMPETITIVE OPERATIONS.
GREYHAVEN SYSTEM BRIEFING
CONTEXTUAL COMPETITIVE OPERATIONS.
CONFLICT NEEDS A REASON.
STAKES NEED A BOUNDARY.
Verified causes create competitive operations with readable preparation, explicit intent, and bounded consequences.
IN-GAME SYSTEM PREVIEW
WATCH CONTEXTUAL COMPETITIVE OPERATIONS CHANGE A REAL DECISION.
CONTEXTUAL PVP OPERATIONAUTO PLAYING
CONTEXTCONTEXT: CONTESTED CARGO
01CONTEXT
Conflict begins with a reason.
Cargo, contracts, rivalries, territory, or a bounty create a server-verified encounter.
CauseRivalry · contract · cargo · bountyPlanPreparation · engagement · exitResponseAsynchronous · live invitation
BUILDSObjectiveRenownCargoInfluenceTerritory
THE PLAYER QUESTION
What can I decide before conflict, and what can I lose?
Nobody appears on an anonymous victim list. A verified cause creates the opening, and every operator can read the intended consequence before commitment.
Permanent progress stays safe
Education, career mastery, identity, and unrelated ownership are not erased by a lost conflict.
Farming is dampened
Repeated conflict against the same opponent reduces reward value and keeps the wider network relevant.
CONNECTED NEXT MOVES
FOLLOW THE CONSEQUENCE.
Need exact rules? Open the field manual.
THE SYSTEMS TEACH EACH OTHER
START WITH ONE MOVE.
You do not need to memorize the machine. Greyhaven shows what an opportunity needs, why an outcome happened, and where its consequence can go next.