Project model

RC is the only project runtime architecture

RC owns project source, service inference, executions, stable project subdomains, live updates, versions, public routing and runtime lifecycle. Retired hosting terminology is not part of the current product model.

Each RC project has an owner-scoped project record, immutable content hashes for files, inferred or explicit services, an entry service, versions and one stable public project label.

Static, Node, Python, native and WASM services resolve through RC.

A project save updates the RC source revision without exposing internal storage paths.

The public URL is one label directly under packarcade.win.

The RC front door resolves the project hostname, lets RS answer from cache when possible, and only wakes or contacts the runtime when needed.

Browser → RC front door → RS decision → RC execution ↘ RC Storage / visitor state

Project, version, branding and deployment events use the RC live channel. HTML receives the live client after deployment, so source files in the editor remain unchanged.

Branding, RS cache, favicon injection and activity tracking are enhancements. They now fail open so valid creator HTML can still be served even if an auxiliary record is unavailable.