Promoting and rolling back

Promoting takes the same version

Promoting does not rebuild, does not reserialize, and does not fold in the draft. It activates in production exactly the version that ran in development.

That is what lets the product state that what was tested is what is in production — not a similar rebuild.

What promotion requires

Requirement	Why
A publishing role	Production is a decision for whoever answers for it
The source being development	Promoting is a path, not a shortcut
The version being unaltered	The definition is rechecked; any divergence refuses it
Evidence of runs	See below

Evidence

Promotion collects a fact: how many runs that version had in development, and how many succeeded. Zero successes blocks the promotion.

This is not bureaucracy: it is the difference between "I published it and I think it works" and "it ran and it worked".

It is possible to promote without evidence when the situation warrants it. That is a conscious, recorded decision: it stays in the history, with who decided and why.

The promotion record

Every promotion records the source, the destination, the version, who promoted it, the reason, which version was active before, and the evidence reference. That is what answers "when did this go to production, and on what basis".

Going back to a previous version

It reactivates an exact previous version. No version is altered, and the history stays complete.

Item	Behavior
The reason is required	A rollback with no reason is an event with no explanation
It reuses the history	The history shows "went back to version X", not "created a copy"
It rebuilds nothing	The target version is still whole

When rolling back is the right tool

Situation	What to do
The new version fails in production	Go back to the previous one and investigate calmly
The result changed unexpectedly	Go back; compare the two definitions
A resource became unavailable	Rolling back does not help — the problem is outside the agent
An input's format changed	Rolling back does not help — fix the agent

What does not happen automatically

• Publishing a new version does not move the triggers. They point to an exact active version; the change happens when you activate the new one.
• Rolling back does not cancel runs in flight. They run with the definition frozen at trigger time.

Next steps

• Triggers
• Following runs
• Spaces and access