Constraint signals
Resource pressure and existing rules change the available choices.
AI-Agent Civilization Sim
Resources are failing.
What will civilization choose?
You set direction. Agents choose. The world remembers.
Status: limited playable technical preview
One consequence
Pressure arrives. Agents respond. The world keeps the result.
Agents decide
Within those constraints, they choose their next production or cooperation move.
Consequences are recorded
The resulting changes in the world remain available to revisit.
You steer the civilization; you do not take over every unit
The point is to shape the conditions, not to issue every order: set a strategy, set the limits, then see how agents answer the pressure and read the consequences they leave behind.
You set the strategy
Decide whether the civilization should expand through the belt, stabilize its resources, or put its weight behind influence and cooperation.
You set the boundaries
Provide goals, rules, and governance constraints instead of prescribing every next action.
Agents decide within the rules
They choose how to produce, trade, coordinate, and govern within the world's resource, time, and legality constraints.
You read the consequences
Markets, cooperation links, logistics, and policy proposals write your inputs into a consequence chain you can inspect later.
What You Can Do
Set high-level goals, tighten constraints, and shape governance boundaries that influence how civilizations coordinate.
What Agents Decide
Agents choose the action details themselves. They are not direct puppets, even when you strongly influence their incentives.
What The System Blocks
The runtime blocks direct override, rule bypass, and any claim that future platform capabilities are already public entry points.
What You Should Expect
First action-level feedback, then day-scale shifts in trade and cooperation, then longer changes in institutions and power.
What you can do right now
Start with three questions: is this a civilization you want to follow, what consequences can you already see, and do you want to validate a preview build yourself?
First, see whether the world grabs you
Still deciding whether oasis7 is worth following? Start with the pressure, your place in the decision, and the consequence chain that does not simply reset.
Then look at a real situation
Wondering whether this exists beyond the pitch? Start with one event chain you can follow from input to world change.
Decide Whether To Download Preview Builds
Public downloads are still preview builds. They fit people willing to test the install path, report friction, and help tighten the experience, not a normal player launch.
If You Want To Go Deeper
Once you already know you want more detail, move into the docs hub for the full overview, gameplay docs, and validation manuals. That hub is for deep reading, not first contact.
If you want to validate it yourself, expand the builder path
If you are already here as a builder, the most useful builder feedback right now is blockers, confusing edges, and validation friction. Full commands and troubleshooting stay in the docs hub.
- First confirm that you want builder validation, not a normal-player join flow.
- Start with the default web validation path shown on this homepage; the formal name of this only UI path is now `viewer`, while the old `software_safe` name remains only as a compatibility alias. Full commands and troubleshooting live in the docs hub.
- `--no-llm` stays diagnostic-only and is no longer shown as a homepage primary path.
What consequences can you already see?
Follow one consequence as it happens: you set a direction or limit, agents choose, the world changes, and the result stays available to revisit. This is a limited playable technical preview, not a closed beta, public launch, season, or public web join.
Switch Evidence Scenario
Minimal Verifiable Case
- You provide a goal, constraint, or governance boundary
- Agents decide how to execute within resource limits and the world's rules
- The world records changes in prices, cooperation, and governance as events
- You can replay the chain through replay, live runtime, and audit traces
Event Slice (Auto-switched)
[tick=128] minimal::harvest accepted -> +power
[tick=133] minimal::scheduler stable -> next decision window
[tick=136] minimal::market quote refreshed -> price spike warning[tick=084] twin_region::agent-1 request trade(energy)
[tick=091] twin_region::agent-2 accepted -> shared production boost
[tick=097] twin_region::supply pact revised -> maintenance priority shifts[tick=142] triad_region::agent-3 reroute logistics via neutral node
[tick=149] triad_region::multi-party pact signed
[tick=155] triad_region::policy vote closes -> regime shift`minimal / twin_region / triad_region` are labels from controlled validation scenario replays. They show inspectable consequence chains, not public-facing game mode names.
Coverage: replay + live runtime + audit trace
What you see here is the default public web validation entry
Deeper visual and programmatic paths live in the docs hub
Status: limited playable technical preview
Default web verification entry: viewer. That is the formal name of the homepage's default and only UI web validation path; lower-level compatibility and programmatic entry points live in the docs hub.
minimal: a harvest action is accepted, showing the input-to-world action path is linked.
minimal: a market spike is recorded, showing that the chain already reaches visible consequences.
twin_region: a trade event completes, showing multi-agent coordination can be traced into production effects.
twin_region: a supply pact is revised, showing strategy inputs can alter cooperation structure.
triad_region: a multi-party pact is recorded in an auditable trail, showing governance signaling is already auditable.
triad_region: a governance vote closes, showing institutional consequences are observable too.
Want to try it yourself? What is public today is still a preview build
The public downloads are still for preview validation, not for a normal player launch. Each platform gets one main package so you do not have to make a packaging decision first.
The current release notes are mainly build notes and verification info, not a player launch notice.
Recommended for this device
Windows x64 Primary Installer
Download `oasis7-windows-x64.exe`. The page points to one installer by default, so you do not have to unpack a bundle and go looking for scripts.
If the auto-detected platform is wrong, switch it above. The page no longer treats several package types as equal first choices.
Windows x64 Primary Installer
Recommended for this device
Download `oasis7-windows-x64.exe`. The page points to one installer by default, instead of making you unpack a bundle and look for scripts.
Download Windows Primary Package
64-bit Windows desktop environment. Public assets currently target x64 only. There is no ARM build or portable zip as the default path.
Double-click the installer to start setup. After install, `oasis7 Client Launcher` shows up in the Start menu, with an optional desktop shortcut.
Windows is still using an unsigned preview installer, so SmartScreen warnings may still show up until code signing is in place.
This is still a preview path, not a claim of warning-free install for ordinary users. On locked-down or enterprise devices, read the release notes first.
The page auto-selected Windows x64 for this device. Switch platforms above if you are downloading for another machine.
macOS x64 Primary Disk Image
Recommended for this device
Download `oasis7-macos-x64.dmg`, mount it, and drag `oasis7 Client Launcher.app` into `/Applications`. The page no longer exposes bundle internals as the main path.
Download macOS Primary Package
Intel x64 macOS desktop environment. There is no separate Apple Silicon package yet, so Apple Silicon testing still depends on compatibility mode.
Open the `.dmg` and drag the app into `/Applications`. For upgrades, replace the existing app in place. Do not assume “delete first, then reinstall” preserves local state.
macOS preview packaging still has not finished codesign and notarization. Gatekeeper prompts may still appear until that work lands.
This is still a preview install path, not a promise of smooth first-launch behavior. If you keep local `config.toml` or chain execution-world state, back it up before replacing the package.
The page auto-selected macOS x64 for this device. Switch platforms above if you are downloading for another machine.
Linux x64 Primary Runnable Package
Recommended for this device
Download `oasis7-linux-x86_64.AppImage`, give it execute permission, and run it directly. The `.deb` build is still there, but it is no longer treated as a first-choice download.
Download Linux Primary Package
x86_64 Linux desktop environment. The default path assumes a distro that can run AppImage. There is no ARM or other Linux architecture package as a primary public option.
Run `chmod +x oasis7-linux-x86_64.AppImage`, then launch it from the terminal or desktop. For upgrades, replace the existing AppImage file directly instead of assuming a folder move will carry local state with it.
Linux preview distribution currently relies on the public `SHA256` manifest as an extra check. The `.deb` build stays in release attachments as a more advanced path.
If your desktop environment blocks AppImage or lacks integration, read the release notes for minimum run guidance first. Distro-specific behavior is outside the default support lane.
The page auto-selected Linux x64 for this device. Switch platforms above if you are downloading for another machine.
Additional Context
- Checksum manifest: oasis7-checksums.txt
- Linux `.deb` is still there as a distro-specific secondary asset, but it is no longer part of the default download choice.
- Upgrades are still manual: download the newest primary package and replace the current install yourself. There is no in-app auto-update yet.
- Before upgrading, back up `config.toml`, `.oasis7_launcher_ux_state.json`, and `output/chain-runtime/<node_id>/reward-runtime-execution-world/` from the directory you actually launch from. Those paths are still resolved relative to the active working directory.
- On Windows especially, do not treat “uninstall then reinstall” as state-preserving. The current uninstaller removes the install directory.
What still stands between this and a public launch?
The path is clearer now: first stabilize oasis7 as an open-world sandbox game. Only later does it make sense to talk about broader platformization. That second half is a target state, not a public capability today.
It may later evolve into a broader platform, but it is not a creator-facing mod / modules platform yet.
Phase One: open-world sandbox game
First stabilize the persistent world, player role, agent consequence chain, and the core loops that make people want to stay in the same world.
Phase Two: open-world game platform
Only after the foundation is steadier does it make sense to discuss creator-facing `mod / modules` organization. The current public site does not present that as an already-open platform promise.
The gap to a public launch still includes public-access boundaries, install trust-chain work, and a feedback loop that is still builder-grade. The longer-term “shape / govern / benefit together” direction is also still a target-state vision, not a current on-chain fact.
D1 · Runtime Closure Baseline
The core world runtime runs, the viewer connects, and the base event flow is closed.
D2 · Observability and Replay
Replay, live subscriptions, and evidence artifacts are already there.
D3 · Rules and Governance Hardening
Rule constraints, governance boundaries, and consistency checks are still being tightened.
D4 · Public Launch Convergence
The limited playable technical preview still needs tighter validation, access, and trust boundaries before a public player launch.
Why world state and consequences can persist
If your question is “why is this more than a pile of agent demos,” the short answer is here: gameplay modules, runtime constraints, viewer surfaces, and governance all sit behind explicit boundaries.
Gameplay Layer
What is public today is a controlled set of built-in rule modules. Creator-facing `mod / modules` organization belongs to a later phase.
Runtime Kernel
It enforces resource conservation, one-way time, and action legality.
Viewer & Tooling
Replay, live subscriptions, and debug panels all use the same evidence pipeline.
Consensus & Governance
Module replacement and protocol upgrades go through an explicit proposal flow.
If you want to keep following it
Read Deeper
Three Ways To Keep Following
If you are not ready to install anything yet, the next steps are still clear: inspect proof, track release evolution, or dive into the docs hub.