Reversal is part of the release, not a rescue plan.
Rollback availability is itself a gate, confirmed before the release proceeds. The previous verified artifact stays available with its provenance intact, so going back means returning to something certified in its own right rather than rebuilt from memory under pressure. Where a change touches stored data, policy requires a way back before the change is built at all. Reversal is then a decision, not an investigation.
Checked while everything is calm
Rollback is verified during certification, not improvised during an incident. A release with no path back does not pass its gates. The check covers the artifact, its dependencies and any data change that would have to be undone.
The previous artifact keeps its record
Going back means returning to one specific verified artifact, with its Blueprint version, generator version and policy profile still attached. You know what you are returning to, down to the commit in GitHub. Nothing is reassembled from branch history at the worst possible moment.
Data changes carry a way back
Policy classes a change that can destroy existing data as high risk before it is built, and a change that rewrites or removes stored data with no way back is blocked rather than flagged. That rule is what makes rollback meaningful later. Reversibility is designed into the change instead of attempted after the fact.
In this capability
- Rollback as a release gate
- Previous artifact retained
- Way back for data changes
- Reversal without rebuild
Releases
The rest of Releases
Build Certification
Nine steps in fixed order: Blueprint validation, policy, dependency resolution, target resolution, generation, unit tests, integration tests, artifact verification, pull request.
Provenance
Every artifact names what produced it: product, Blueprint version, generator, agents, policy profile and commit.
Release Gates
Blueprint validation, build, policy, code review, security, QA, provenance and rollback — each one explicit, with a stated risk level.
GitHub Flow
Branches, pull requests, reviews, CI and releases stay in GitHub. Foundariq records why each one exists.
Stop managing prompts. Start managing software strategy.
Connect your repositories. Let Foundariq understand what you have already built. Then tell it what your portfolio should build next.
Read-only to start · Your code stays in your GitHub · [email protected]