Runtime and ECS
World lifecycle, handles, archetypes, scheduler safety, and deterministic structural changes are treated as production foundations, not optional future work.
A platform architecture built to stay coherent under load.
The technology direction behind Verth Engine spans runtime, renderer, build graph, launcher auth, API-issued launch tickets, and explicit entitlement rules.
Graphics
Validation-first RHI, pipeline caches, offline shader compilation, and render graph discipline define the rendering path.
Build graph
Compile and build are separate but connected. Content baking, network schema, audio graphs, shader variants, and package signing feed the same orchestrator.
Plugins
Plugin SDK surfaces are explicit: interfaces, extension points, ABI contract, permissions, compatibility reports, and evolution policy are already treated as platform primitives.
Launcher and API
Verthsoft Account, Google, GitHub, session persistence, OAuth linking, and signed editor launch tickets live behind the same account model.
Operations
API, database, and future chat services are being structured as separate VPS roles with Cloudflare fronting, PostgreSQL persistence, and Rust services where throughput matters.