SubZeroDev.Platform — Documentation

The reusable application framework and hosting layer for SubZeroDev products. Design stage — no packages have been built.

Read in this order. Each document says what it owns; decisions live in their own records.

#	Document	Holds
1	Platform Identity	Start here. What this repository is, and the collision it settles
2	Platform Specification	The framework — packages, modules, hosting, persistence, identity, billing
3	Game Engine as a Service	The hosted game product — vision, not contract
4	Engine Hosting Contract	What "Platform hosts the engine" means, and the four questions hosting introduces
5	MCP Tool Contract	The engine's tool table — current, built and tested. Lives in `SubZeroDev.ServiceContract`
7	The Minimal Package Set	The six near-term packages: boundaries and done-criteria
8	Second-Consumer Packages	Identity, Tenancy, Billing, Mcp — justified, not scheduled
9	Application Modules	The framework/module split, a third consumer, and the two modules admitted by decision
10	Implementation Plan	The ordered plan, both tracks, with ordering constraints

Supporting specifications, moved from the ecosystem staging tree: Events and Notifications · Tenancy, Billing, Licensing · Observability

Decisions

Reasoning, consequences and rejected alternatives live in the record, never restated elsewhere:

The one rule underneath all of it

              SubZeroDev.Platform
                 ↓            ↓
        SubZeroDev.Automator   Game Engine as a Service
                 ↓
      Plugins / Workflows / Products

Platform never depends on a product, and never on a plugin. A reference from Platform to either is a build failure, not a review comment.

Decisions​

The one rule underneath all of it​

Decisions

The one rule underneath all of it