Current Game

The Amber State

Amber State is one deterministic, human-directed universe. The game is the canon core. Manuals, soundtrack, and video exist to make the same system legible from different angles, not to drift into disconnected worldbuilding.

Game is canon core Offline-first, local-first build One release bundle at a time

The Canon Engine

Amber State is a 1-D deterministic colony simulation focused on resource tension, survival logic, and structural constraints. The game is where world rules become real. Other media can interpret the state, but they do not get to silently rewrite it.

One Triangle Before The Factory Sprawls

The current build order is deliberately narrow: one playable loop, one operator manual fragment, and one soundtrack chapter tied back to the same subsystem. Video can test memory and atmosphere, but it cannot outrun the game.

  • World bible and canon registry first
  • Visual doctrine and soundtrack doctrine before volume
  • Human review on canon, style, publishing, and spend
  • Release bundles over random clips
Amber State is a serious systems build, not an AI-content factory. The quality bar is coherence, not throughput.

What Can Cross The Boundary

  • Named operating modes and symbols can cross mediums
  • Simulation rules and deterministic seeds stay game-native
  • Manuals explain the world, they do not replace the loop
  • Soundtrack carries atmosphere, not plot responsibility
  • Video tests memory, pacing, and identity, not canon law

Current Build Shape

  • Control-plane doctrine is now explicit
  • The game lane remains the authority surface
  • Feedback routing is being shaped as a local file bus
  • Public-facing release cadence is being bounded before scale

Development is ongoing by design. The goal is a coherent chapter loop, not a pile of disconnected artifacts.

Next Shipping Unit

  • World bible skeleton and canon registry lock
  • Reactor Room vertical slice brief
  • One operator manual fragment tied to that slice
  • One soundtrack family and one public artifact from the same chapter

What This Demonstrates Professionally

  • Long-horizon roadmap planning
  • Structured iteration cycles
  • Toolchain automation and reliability guardrails
  • Deterministic debugging practices
  • Performance-aware systems modeling
  • Documentation and architecture discipline
© Hubsays Studio