XCP Creative Platform
Create software from an idea, adapt an existing project, or evolve it across new versions. XCP turns the result into a deterministic project, runs it on real Xbox hardware, and returns structured evidence for the next iteration.
XCP Studio
XCP Studio brings creation, source adaptation, project evolution, Xbox playtesting and structured evidence into one coherent development environment.
One authoritative project. Three interfaces onto it.
The lifecycle
Most AI coding tools stop when the files are written. XCP continues through validation, execution, observation, correction, versioning and rollback on real hardware.
The loop closes. What the console reports becomes the input to the next correction, and the correction is machine-readable, so an agent can act on it without a human translating a stack trace first.
Proof of the platform
Software can start as an idea or as an existing codebase. Either way it becomes an ordinary XCP project, and every project takes the same path from there.
Create
An AI-driven, human-directed workflow created an interactive arena shooter from zero and brought it to real execution on Xbox.
Core Siege was an early AI-driven Xbox prototype. XCP now turns that creation path into a repeatable, observable and verifiable lifecycle.
Adapt
XCP observed an existing Godot project, derived its structure and semantics, and produced an ordinary XCP project that completed the Xbox lifecycle.
Adapted from authorized Godot 2 source; completed the Xbox lifecycle as a playable behavioural subset with declared degradation. Full source equivalence is not claimed. Minilens is the work of its authors, used under GPL-3.0-or-later.
Whether created or adapted, an XCP project can continue to evolve across new source revisions and local decisions. See how evolution works.
Proof
XCP does not treat evidence as documentation written after the run. The lifecycle produces the evidence while the work is executed.
Where the work happens
The AI plans, creates and corrects from the PC side. Project files, adaptation, semantic diff and build all happen here, where they can be inspected and re-run.
Xbox executes bounded, validated artifacts through the measured XCP runtime. No model-provider credentials are stored on the console.
A model provider may be remote. The project lifecycle and the Xbox execution are local; the AI itself is not necessarily local, and this page does not claim otherwise.
XCP closes the loop between AI reasoning, deterministic execution and real hardware evidence.