With your permission, we use cookies and similar technologies to understand how this site is used and to improve it. Nothing is measured until you choose, and you can change your mind at any time from the footer. Read the cookie notice
Continuumship
Flow templates
Five complete flows ship with Continuumship. Each is a valid definition you copy into a draft, adapt in the Studio, and publish as your own.
A product team shipping a web service every week.
Shape, design where it is needed, plan, build under the plan, review and release. The build is verified against its contract before review.
The build verified before review; production changes approved with separation of duties.
Teams that let agents triage the intake and build approved plans.
An agent triages what arrives and builds the approved plan step by step. People decide the plan, the design and the review.
Agent runs start only from an approved plan; the build verified before review.
Services where a failed release costs money or trust.
Everything a governed team does, with the security group deciding every build. The deployment is verified in staging before release.
A security decision on every build; staging verified; two approvals before production.
Something is broken in production and needs the shortest safe path.
What is broken, the fix, its verification and the release. Nothing else stands in the way, and every step is still on the record.
The fix verified against its contract; every approval recorded.
Changes an auditor will ask about.
Two people who did not write the change approve its build. The deployment is verified in staging before release.
Two approvers who did not write the change; staging verified; two approvals before production.
How it works
A template is a starting point, not a lock. What you publish is your definition — versioned, and in your repository if you choose.
Choose the flow closest to how your team ships. Every template validates against the same contract the engine runs.
Edit it as a canvas, an outline or code. Replay it over your history to see what it would have required.
Publish it as a new version, or keep it in your repository and let your pipeline sync it.
Start from a template, or from the process your team already follows, discovered from your own history.