Root interaction surface
Current time stays public here. Systems, training, research, development, and logs are routed into deeper layers instead of cluttering the chat surface.
Current time stays public here. Systems, training, research, development, and logs are routed into deeper layers instead of cluttering the chat surface.
This layer holds system-facing clocks, tempo domains, capability detection, and the event ledger that should not live in the main user chat surface.
This is the first scaffold for fast internal training. It does not fake backend intelligence. It does expose a domain engine, queued work, speed controls, and persistent local state.
This layer tracks exploratory work and best-practice synthesis without pretending that static front-end code is doing hidden server research.
This layer holds subsystem scaffolds, module status, dynamic world creation, and speed control for build work that belongs below the root surface.
World traversal replaces the visible page with a world-specific surface.