Alpha 1.0 can run today.
But “runs locally” and “production-ready” are different claims.
SYSTEM DEVELOPMENT
01 / BEFORE START
Separate “on-prem testing”
from production operation.
The current local Alpha profile is loopback-only and intended for development and integration. It is suitable for experiencing the present state of MachiVerse on a PC or managed test machine, but it is not a production security profile.
Production OIDC / TLS deployment acceptance is still a later work package. Adding your own authentication or TLS layer does not, by itself, make the current profile an accepted production deployment.
02 / QUICK START — WINDOWS
Three lines
to startup.
The current Quick Start in the main repository targets Windows and assumes a .NET SDK 10.0.400-equivalent environment plus the latest develop.
git checkout develop
git pull
start-alpha.batIf you have already built the components, subsequent runs can skip the build.
start-alpha.bat --no-build03 / WHAT STARTS
The world engine,
the gateway, and two Views.
The standard Alpha 1.0 startup connects these four components.
04 / PERSISTENCE & RECOVERY
Not just startup.
Test restart too.
Alpha 1.0 connects Core / Gateway persistence, shutdown, restart, recovery, and resynchronization. You can inspect more than a one-shot demo path.
NEXT STEP
From running the world
to understanding it.
The main repository's Alpha 1.0 Integration Runbook is the source of truth for manual startup, Linux / macOS-equivalent commands, the Golden Demo, and known limitations. For the system model, continue to Architecture & Design.
