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.
Guided editing, expert source access and AI agents operate on the same authoritative project.
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.
Create · Adapt · Evolve
Whichever way a project starts, what reaches the console is an ordinary XCP project — validated, versioned and reversible in the same way.
idea → ordinary XCP project
A person or an AI agent can author an ordinary XCP project from zero, validate it, run it on Xbox, observe the result and correct structured failures without using a separate privileged path.
Demonstrated with a game and a utility created by a repository-independent agent.
semantic model → editable XCP project
XCP observes an external project, derives its structure and semantics, reconciles them with the measured Xbox host profile and produces an ordinary, editable XCP project.
Demonstrated with a real Godot 2 project executed through the complete Xbox lifecycle.
new revision → new reversible version
When the original source changes, XCP can compare revisions, reuse unchanged outputs, rebuild affected parts, preserve explicit local decisions and create a new reversible project version.
Demonstrated through an exact update and rollback across two real source revisions.
XCP admits bounded interactive software, not one genre:
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 built an interactive arena shooter from zero and brought it to real execution on retail Xbox hardware in Developer Mode.
The Forge Protocol runtime work is one of the foundations the XCP Creative Host is built on. Core Siege ships as its own signed package; it is not presented here as an XCP creative project.
Adapt
XCP observed an existing Godot project, derived its structure and semantics, and produced an ordinary XCP project that completed the Xbox lifecycle.
Measured as playable with degradation. Full source equivalence is not claimed. Minilens is the work of its authors, used under GPL-3.0-or-later as an adaptation subject.
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.
XCP Studio
Guided editing, expert source editing and external AI agents all operate on the same project authority and pass through the same validation, execution and evidence lifecycle.
Not three systems that agree. One file, three interfaces onto it.
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. The console stores no OpenAI or Codex credentials.
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.
