Roadmap

The editor becomes the primary authoring tool: script attachment, play/stop mode, scene persistence, and a proper UUID-based asset pipeline.

• — Editor integration and scene persistence #6
• — Asset pipeline #22
• — Mutation pipeline with undo/redo #40
• — Scene format specification #41
• — Scene gizmos and editor top bar #60

Orrin at this stage is missing a lot of features that are required for games to be made. This phase is trying to tackle this.

• — Render graph inspector and one-file frame capture
• — Shader graph and scripting editing.
• — MCP tooling.
• — Asset hot reloading.
• — Skeletal animation, designed into the ECS before more systems assume static meshes
• — A physics decision, realistically integrating Rapier rather than growing the Phase 1 collision system

Cargo's model applied to game content: a package manager over content-addressed assets, self-hostable registries, and a shared import cache. Scheduled before collaboration because it exercises the same server infrastructure at lower protocol risk.

The CRDT scene document behind the existing mutation pipeline, the self-hosted server, presence and asset locks — then hosted convenience once self-hosting is stable.

An alternative render graph over the same scene and materials, benchmarked against the reference tracer that will have been validating the renderer for two years by then.