AI Control Protocol

Sektor's defining feature is that an AI collaborator is a first-class client of the engine — not a bolted-on afterthought. It works through the exact same command boundary the editor uses.

How it works

The editor talks to the engine over a local control protocol (sektor.control/v1). Over 100 validated operations cover projects, scenes, entities, transforms, hierarchy, layers, world partition, prefabs, materials, terrain, components, events, runtime/play, input, and rendering captures.

An AI assistant connects to the same protocol. This means it can:

• Inspect your scene through structured snapshots, diagnostics, and capability metadata — no screen scraping.
• Change the world through the same validated, transactional commands you use.
• See results through revision-tagged render captures — the AI reviews the same pixels you do.

Guarantees

Because every mutation flows through the engine's single transaction boundary:

• Every AI edit is validated — malformed or illegal requests are rejected with structured errors.
• Every AI edit is undoable — it lands as a normal entry in your history.
• Every AI edit is attributable and observable — it shows up in the activity log and diagnostics.

The AI is a first-class client, but never a privileged bypass. It cannot do anything you couldn't do — and cannot do it silently.

Machine-readable registries

The engine publishes its own component registry, event registry, and expression registry — with field types, constraints, asset-reference kinds, and authoring commands. Automated clients read these to discover what's possible rather than guessing, so the protocol and the tools that use it stay in lockstep with the engine.