Public entry

Platform view

A public snapshot of the deployment envelope, sovereign runtime chain, and the path from browseable site to authenticated workspace.

Architecture Capabilities Access workspace

Platform overview

The platform view is where the full shape of Ionirix becomes easier to see. The public shell, the Worker route layer, the state bus, and the deeper simulation bridge are not independent systems stitched together after the fact. They now behave more like coordinated layers in one runtime model.

This page is therefore less about naming technologies and more about showing how the platform behaves as a whole. Public pages establish context. The Worker governs live access and control. Stateful coordination begins at the session boundary. Deeper authority appears only when the runtime needs a stronger execution model. The result is a platform that can stay legible while becoming more powerful.

Deployment topology

The dashboard exports to static HTML inside the public folder and is served through the Cloudflare Workers assets binding, keeping the public shell lean while preserving global reach.
The Worker now carries the Sovereign runtime edge layer: authenticated APIs, simulation websocket upgrades, and the Durable Object world-state bus that coordinates live session-aware behavior.
Cosmic runs can bridge from the Worker to the authoritative Python world kernel while multiverse runs stay deterministic at the edge, making the platform more explicit about where simulation authority actually sits.
The site stays split cleanly between public briefings and protected operational surfaces, but both now describe the same runtime model rather than behaving like separate products.

Public status signal

Status: Loading
D1: Pending
KV: Pending
Assets: Pending

Deployment

Cloudflare Workers

production · global-edge

Live surface

0 public / 0 workspace

Version 2.0.0

Auth users

Tool runs

Simulation runs

Public runtime posture

The public side of Ionirix now acts as a true briefing surface. It explains what the platform is, how the site is delivered, where state begins to matter, and how a visitor moves from browseable context into authenticated operation. This turns the public shell into part of the platform architecture rather than a thin wrapper around it.

Edge governance

The Worker layer now carries much more than route forwarding. It governs identity boundaries, live API access, simulation stream upgrades, and the public health surface. In practice, this means the edge has become the place where explanation, access, and runtime control begin to converge.

Platform continuity

The platform view matters because it shows that the system is no longer split into unrelated pieces. Public pages, billing and verification paths, state coordination, and deeper simulation execution now read more clearly as parts of one operational model. That continuity is a platform capability in its own right.

Public entry points

The public shell now acts as the Sovereign briefing layer, surfacing runtime architecture, rollout status, and capabilities before the auth boundary. This makes platform understanding part of the initial user experience rather than something hidden behind sign-in.

Worker contract

The edge contract now spans public health, authenticated simulation control, stream upgrades, and session-scoped access to sovereign world state. The Worker is therefore both a routing layer and the first active control boundary for the runtime.

Authoritative kernel path

The sovereign path now runs from public explanation, to Worker edge orchestration, to a Python authoritative kernel for cosmic world-state execution. That layered path gives the platform more depth without forcing every interaction into the same runtime context.

How the platform behaves in practice

In practical terms, the platform now supports a cleaner progression from reading to operation. A visitor can inspect the public surface, understand what the system is trying to do, and then move into a workspace where state, tools, simulations, and identity-sensitive operations become available under the correct boundary conditions.

This matters because platform quality is not just about backend strength or UI polish. It depends on whether the layers fit together in a way that preserves trust. The current architecture makes it easier to see where public explanation ends, where live control begins, and where deeper state authority must take over.

That staged model also makes the platform more adaptable across different classes of workload. Static content can stay globally efficient. Edge logic can stay reactive. Session state can remain scoped. More authoritative simulation execution can be reached only when the task actually requires it. This is the kind of layered behavior that keeps a platform simple at the surface without making it shallow underneath.

Asset delivery

Static public assets still provide the first layer of reach. This keeps the browseable site fast and resilient while allowing the public surface to hold much more explanatory content than before.

Live route intelligence

As soon as a request moves beyond pure public content, the Worker route layer can take over. This introduces live control, authenticated APIs, and runtime-aware behavior only where they are actually needed.

State-aware execution

The platform now supports a clearer path from public surface to session-scoped state and onward into more authoritative simulation handling. That staged progression makes the system easier to trust and easier to reason about.