oasis7

AI-Agent Civilization Sim

Resources are running out.
What will the civilization choose?

You set the direction. Agents make the choices.

You can influence a civilization, but you cannot decide every step for its Agents.

Set goals and constraints, then watch choices move through the asteroid belt and leave consequences you can revisit.

Status: limited playable technical preview

A civilization crisis

Resource pressure tightens. What will the Agents choose?

Production, trade, and cooperation have less room to move. Agents choose within the current constraints, and the world keeps the result.

An illustrative replay based on current controlled test scenarios; not live world telemetry or a public game mode.

Switch crisis scenario

Controlled single-front Viewer capture showing observable world state in the asteroid belt
Single-front: illustrative controlled replay capture, not a concept image or public game mode.
Controlled dual-region Viewer capture showing two regions and their observable world state
Dual-region: illustrative controlled replay capture, not a concept image or public game mode.
Controlled three-party governance Viewer capture showing multiple regions and observable world state
Three-party: illustrative controlled replay capture, not a concept image or public game mode.

Single-front · causal trace

How this crisis leaves a trace

  1. 01
    Pressure arrives

    Resources, goals, or existing rules narrow the available choices.

  2. 02
    Agents respond

    They choose production, trade, or cooperation within the current constraints.

  3. 03
    Consequences remain

    World changes can enter events, replays, and audit-readable traces.

Get the Preview Build

Default web verification entry: viewer. Deeper visual and programmatic paths live in the docs hub.

Expand the corresponding event log samples (illustrative evidence)
[sample tick=128] minimal::harvest accepted -> +power
[sample tick=133] minimal::scheduler stable -> next decision window
[sample tick=136] minimal::market quote refreshed -> price spike warning
[sample tick=084] twin_region::agent-1 request trade(energy)
[sample tick=091] twin_region::agent-2 accepted -> shared production boost
[sample tick=097] twin_region::supply pact revised -> maintenance priority shifts
[sample tick=142] triad_region::agent-3 reroute logistics via neutral node
[sample tick=149] triad_region::multi-party pact signed
[sample tick=155] triad_region::policy vote closes -> regime shift
Tick 128 · sample

Illustrative minimal sample: a harvest action is accepted, showing how an input-to-world action path could be linked.

Tick 136 · sample

Illustrative minimal sample: a market spike is recorded, showing how a chain could reach a visible consequence.

Tick 91 · sample

Illustrative dual-region sample: a trade event completes, showing how coordination could be traced into production effects.

Tick 97 · sample

Illustrative dual-region sample: a supply pact is revised, showing how strategy inputs could alter cooperation structure.

Tick 149 · sample

Illustrative three-party sample: a multi-party pact is recorded in an auditable trail, showing how governance signaling could be audited.

Tick 155 · sample

Illustrative three-party sample: a governance vote closes, showing how institutional consequences could be observed.

World laws · player boundaries

This world has only a few laws that cannot be broken.

They explain what players can influence, and why the Viewer must make evidence and unknown states explicit.

01 · persistent timeline

Time only moves forward

The same world advances along one persistent, authoritative timeline; a refresh cannot erase changes that already happened.

02 · resource cost

Nothing appears from nowhere

Every resource has a source, cost, and owner; a preview or recommendation cannot mint a settled result.

03 · indirect agency

You cannot choose for them

You shape goals and conditions. The civilization acts for itself and carries the consequences.

04 · auditable consequences

Consequences can be revisited

Changes leave a trace. Unknown states stay visibly unknown instead of pretending success.

Ordinary browsing and refreshes do not erase changes that already happened; governed recovery follows a separate audited process. Every resource has a source and a cost. Unknown states stay visibly unknown instead of pretending success. See the World Rules & Core Gameplay PRD (doc/product/world-rules-core-gameplay/prd.md).

Observe and influence

Do not issue every Agent order; learn to read a world that is changing.

The current Viewer shows regions, events, and state changes inside controlled scenarios. You see pressure move through the world, then revisit how Agents coordinate, trade, or adjust within its constraints.

STATIC CARTOGRAPHY Source: controlled validation scenario NO LIVE DATA FEED
Current Viewer controlled three-party governance scenario showing regions and observable world state
Current controlled-scenario Viewer capture: for observation and validation, not public web joining or an opened game mode.
01

Observe

Read the current world state and changes between regions.

02

Influence

Set direction and constraints from outside the civilization without taking over each action.

03

Revisit

Place recorded events and consequences back into an inspectable trail.

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.

Current version: 2026-06-03_v2 Published: 2026-06-03 Release notes

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.

Compatibility and trust boundary before install
System / architecture
64-bit Windows desktop environment. Public assets currently target x64 only. There is no ARM build or portable zip as the default path.
Install path
Double-click the installer to start setup. After install, `oasis7 Client Launcher` shows up in the Start menu, with an optional desktop shortcut.
Trust-chain status
These are still preview packages: Windows is not code-signed yet, macOS is not notarized yet, and checksums are only an extra check, not a platform trust chain.
Support boundary
This page is for preview validation, not a player-ready launch. If your device blocks unknown publishers, check the release notes before downloading.

Check whether this path is for you

The public entry is for technical-preview validation only, not a public web player entry.

  • Good fit: builders who want to validate preview builds and report blockers or install friction.
  • Not for: people expecting a public web player entry or a public player launch experience.
  • Current boundary: this is not a public web player entry or a public player launch, and formal announcement is still pending.
Additional verification and upgrade context
  • Checksum manifest: oasis7-checksums.txt
  • Linux uses `.deb` as its default primary package; operator recovery tools are shipped separately as `oasis7-linux-x64-ops-tools.tar.gz` with manifest/checksum coverage.
  • 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.

If you want to keep following it

If you want to go deeper, expand the builder and future boundary

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.

It may later evolve into a broader platform, but it is not a creator-facing mod / modules platform yet.

  1. First confirm that you want builder validation, not a normal-player join flow.
  2. The only UI web validation path shown by default is formally named viewer; the old software_safe name remains only as a compatibility alias.
  3. --no-llm is diagnostic-only, not the homepage's formal playability path.