Owns the authoritative world
Responsible for world simulation, authoritative WorldState, operation execution, and persistence. Alpha 1.0 verifies real startup, mutation, and recovery.
MACHIVERSE / DEVELOPER
The current state and entry pointfor building the world.
MachiVerse is an agent-based large-scale world simulator developed in C# / .NET 10. The current develop branch contains a reproducible Alpha 1.0 vertical slice connecting Simulation Core, Gateway, General View, and Administration View.
Architecture ARCHITECTURE
Four execution units,
connected by protocols.
MachiVerse treats four top-level components as independent execution, build, and distribution units. Internal implementation types and DLLs are not shared as communication contracts; versioned protocol/schema boundaries are used instead.
Simulation CoreWorldState / Operation / Persistence
GatewayAuth / Cache / Publication
General ViewBrowser / Participation / Prediction
Administration ViewHealth / Config / Operations
The external connection boundary
Handles external connectivity, authentication/authorization, confirmed cache, operation aggregation, and publication. Core, View, and Admin are connected end to end.
Entry point for Divers
The general-user reference and participation UI. Built with Blazor WASM + three.js, with browser E2E and the foundations of prediction/reconciliation connected.
Operations and configuration
Responsible for monitoring, configuration, and operational UI. Alpha 1.0 includes E2E health checks and config read/change flows.
Quick Start QUICK START
Run the Alpha 1.0 loop
on your local machine.
The current README Quick Start targets Windows. With a .NET SDK equivalent to 10.0.400 and the latest develop branch, the startup script builds and launches all four components.
git checkout develop
git pull
start-alpha.batstart-alpha.bat --no-buildEngineering principles PRINCIPLES
Protect the world's contracts
before implementing features.
Preserve determinism
The basic contract is that the same World Seed, configuration, and operations converge to the same result.
Use versioned boundaries
Internal types or shared DTO libraries are not used as communication contracts between components; Protocol/schema is the boundary.
Do not invent unapproved behavior
Related design documents and AGENTS.md are checked before implementation; unapproved behavior is not assumed and implemented as if it were decided.
Keep tunable values in external config
Tunable values are intended to remain configurable through external configuration owned by each component.
Current limitations LIMITATIONS
Alpha 1.0 is not
the finished product.
The current local Alpha profile is loopback-only for development and integration. It is not a substitute for a production security profile.
Development update DEVELOPMENT UPDATE
Keep the current state
of implementation visible.
GitHub and the Roadmap remain the source of truth for work packages after Alpha 1.0, design changes, and implementation progress.
Contributing CONTRIBUTING
From Issue, Discussion, or Pull Request
to implementation in the world.
Normal work branches from the relevant persistent component branch and is integrated through Pull Requests. Protocol changes update the relevant protocol design document before implementation, and design changes are reflected in related documentation.
main stable / release candidate
↑
develop next integrated version
↑
├─ simulation
├─ gateway
├─ view
└─ administration-view
GitHub RepositorySource code and latest README
Alpha 1.0 IntegrationReproduction steps and acceptance
Design DocumentsArchitecture, protocols, and design materials
RoadmapImplementation sequence and next work packages
Contribution GuideHow to use Issues, PRs, and Discussions
GitHub DiscussionsIdeas, Q&A, and design discussions