oasis7

AI-Agent Civilization Sim

Lead an AI-agent civilization in a fractured asteroid belt

You guide the civilization from above: decide whether it races for ore, stabilizes its routes, or turns fragile cooperation into auditable agreements. Agents handle harvesting, production, trade, coordination, and governance under hard limits, so prices, blocs, and policy shifts leave consequences behind in the same persistent world. What is public today is still a gameplay preview.

See The Core Loop In 30 Seconds See One Event Chain Open Project Overview
World: fractured asteroid-belt civilization Player role: outside civilization strategist Loop: expansion / trade / cooperation / governance Status: technical preview, not playable yet
0 Three pressure lines pulling at once: industry / economy / governance
0 The same world keeps producing, trading, and coordinating after you leave instead of resetting to zero

Picture the kind of session that unfolds

What makes this kind of game hard to leave is not the button-clicking. It is the feeling of watching a mess slowly turn into an order that can run on its own. One strained mining belt can shake an entire production chain, one renegotiated cooperation can change the whole board, and every judgment you make keeps rewriting the expansion, risk, and tempo that come next.

Resources Tighten First

When one mining line breaks, prices rise, production slips, and neighbors who were tolerable a minute ago start hoarding, rerouting supply, or racing you to the same belt.

Cooperation Negotiates Before It Changes

Groups trade, stall, and cut temporary deals until pressure forces new terms, new responsibilities, or a different allocation.

The World Keeps The Ledger

Governance and supply decisions do not end as one-off messages. Routes get rearranged, prices keep drifting, and policy changes continue to reshape the same world when you come back.

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

oasis7 In 30 Seconds

In one sentence, oasis7 is a persistent civilization sim set in a fractured asteroid belt. You push the strategic direction from outside the world and watch a group of agents carry expansion, production, cooperation, and governance forward under real constraints.

What It Is

It puts industry, economy, and governance inside one asteroid-belt world that keeps running instead of resetting after a short demo.

Who You Are

You are closer to a civilization director shaping momentum from above than a player issuing unit-by-unit orders.

Why The World Changes

Agents act under limits on power, compute, storage, bandwidth, time, and law, so trade, cooperation, governance, and policy shifts all leave real effects behind.

What Is Unusual About It

It is trying to build a world that keeps moving on its own and still leaves enough evidence behind for you to inspect prices, blocs, policy, and production outcomes later.

You set civilization direction, but you do not take over every unit

What matters is the division of responsibility: you set strategy and constraints, agents execute inside the world's rules, and the system keeps the boundaries intact.

01

You Set Strategy

Decide whether the civilization should expand through the belt, stabilize production, or earn influence through governance and cooperation.

02

You Set Boundaries

You provide goals, rules, and governance constraints instead of manually prescribing every next action.

03

Agents Decide Inside Runtime Rules

They choose how to produce, trade, coordinate, and govern within resource, time, and legality constraints.

04

You Read Consequences

Markets, cooperation links, logistics, and policy proposals turn 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

This page should help you answer three things first: whether this is a game world you want to keep tracking, how much of it can already be proven, and whether you want to install a preview build yourself.

First Decide Whether The World Hooks You

If you are still deciding whether oasis7 is worth following, go back to the gameplay framing, the player role, and the persistent-consequence loop first.

Revisit The Core Loop

Then Look At A Real Situation Slice

If your real question is “does any of this already exist beyond the pitch,” start with one inspectable event chain instead of access-mode terminology.

See Proof Chain

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.

See Preview Builds

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.

Open Docs Hub Open HTML Deck
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.

  1. First confirm that you want builder validation, not a normal-player join flow.
  2. 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.
  3. `--no-llm` stays diagnostic-only and is no longer shown as a homepage primary path.
Open Docs Hub Open HTML Deck Open Overview

What can already be checked today

This section does not claim public playability. It shows that inputs, agent decisions, and world-side effects already leave a consequence chain you can inspect.

Switch Evidence Scenario

Minimal Verifiable Case

  1. You provide a goal, constraint, or governance boundary
  2. Agents decide how to execute within runtime legality and resource limits
  3. The world records prices, cooperation, and governance outcomes as events
  4. You can replay the chain through replay, live runtime, and audit traces
Back To Public Entry Options

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: testable, not playable

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.

Tick 128

minimal: a harvest action is accepted, showing the input-to-world action path is linked.

Tick 136

minimal: a market spike is recorded, showing that the chain already reaches visible consequences.

Tick 91

twin_region: a trade event completes, showing multi-agent coordination can be traced into production effects.

Tick 97

twin_region: a supply pact is revised, showing strategy inputs can alter cooperation structure.

Tick 149

triad_region: a multi-party pact lands on-chain, showing governance signaling is already auditable.

Tick 155

triad_region: a governance vote closes, showing institutional consequences are observable too.

If you want to try it yourself, what is public today is still just preview builds

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.

Check whether this path is for you

  • Good fit: builders who want to validate preview builds and report blockers or install friction.
  • Not for: people expecting a hosted web join or a public player launch experience.
  • Current boundary: this is not a hosted web join or a public player launch, and formal announcement is still pending.

Current version: latest publish time pending 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.

Download Windows Primary Package View checksums

If the auto-detected platform is wrong, switch it above. The page no longer treats several package types as equal first choices.

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.

Why it is still not playable

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.

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 playable build still includes unstable public-access boundaries, incomplete 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.

Done

D1 · Runtime Closure Baseline

The core world runtime runs, the viewer connects, and the base event flow is closed.

Done

D2 · Observability and Replay

Replay, live subscriptions, and evidence artifacts are already there.

Active

D3 · Rules and Governance Hardening

Rule constraints, governance boundaries, and consistency checks are still being tightened.

Next

D4 · Playable Release Convergence

Only after that gets steadier does it make sense to move toward a public playable build.

Why the world can keep running

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.

oasis7 engine architecture flow
Gameplay Layer -> Runtime Kernel -> Viewer/Tooling -> Governance. Extensions stay possible, but not unconstrained.

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