Introduction
The Promote stage exists to move the approved solution into Production under control, and to close the project record behind it. This article explains what has to be true before promotion is allowed, what is actually installed, and what the customer is left with finally.
It is the shortest stage in the lifecycle and the most tightly constrained, because it is the only point at which anything produced by the project reaches a live environment.
The steps, in order
The stage moves through the following steps.
- Confirm that the required gates are green, that the approvals are recorded and that the entitlement is valid. Promotion is not allowed otherwise.
- Start promotion from the project.
- ARVO installs the approved solution app into Production through the Admin Center path.
- If promotion is blocked, read the condition that is shown, resolve it and start again.
- When promotion succeeds, the project record is sealed.
[ Screenshot placeholder — the promotion step on a project, showing the gate conditions and the target Production environment
Important: ARVO Studio installs and runs only in sandbox environments. Production receives only the approved solution app, through gated promotion. ARVO Studio and the test app never enter Production.
Only the approved solution app crosses that line. The test app stays in the sandbox where it was deployed, and ARVO Studio itself is never installed into a Production environment. That boundary is the reason a customer can allow a build platform into their tenant at all, so it is enforced and recommended.
The gate
Promotion is allowed only when the required gates are green, the approvals are recorded and the entitlement is valid. If any of those conditions is not met, promotion is blocked and the condition that still needs to be resolved is shown, so you can see exactly what is standing in the way instead of guessing. This has to be resolved, then promotion process can start again.
Who approves or satisfies it
The decisive approval was given at the previous stage by the approver the customer assigned; promotion carries that decision out rather than reopening it. The entitlement condition is satisfied by an active licence on the environment. The promotion itself is started by the consultant or administrator responsible for the release, and the installation into Production goes through the Admin Center path.
What is added to the project record
When promotion completes, the project record is sealed. The receipt holds the project’s permanent history — the attachments, the generation, the approvals and the promotion, each with who did what and when. The snapshot gives a point in time view of the project as it stood, and the print actions produce the evidence pack.
That record is append only and tamper evident: entries are added as events happen and are not overwritten afterwards, and the record is sealed at the moment promotion completes. It is what allows the pack to stand as evidence rather than as a summary written after the fact.
That pack belongs to the customer. It answers the question every audit eventually asks, which is how this change got into Production, and it answers it without anybody having to reconstruct the story from memory, mailboxes and change logs months afterwards. The value is not that the record is clever; it is that it is complete, and that it was created as the work happened.