Deployment decision records
Review the action returned from supplied release checks.
Provide security status, smoke status, approval, rollback revision, and release identifiers. ReleaseQuill returns a decision, the first failed check, or a pending-canary record.
First in handA public preview URL for your own project
Sign in and you go straight back to the ReleaseQuill conversation. Work happens in chat. This page never asks for your card details or email address.
FIRST REAL RESULT
A public preview URL for your own project
Each published URL is on our shared preview address and scoped to your own workspace. Promotion beyond the preview environment requires separate authorization.
ORDERED DECISION TABLE
Security failure first, then smoke, then approval.
A failed security check returns abort. A failed smoke check returns rollback only when a rollback revision is supplied; otherwise it returns stop and escalate.
- 01abort
A failed security check returns abort.
- 02rollback
A failed smoke check returns rollback only when a rollback revision is supplied.
- 03stop and escalate
Otherwise a failed smoke check returns stop and escalate.
- 04promote
Promote for approval after passed checks.
- 05hold
Missing approval holds.
WHAT YOU BRING TO THE CONSOLE
The table only runs on the checks you supply.
Inputs cover security and smoke status, approval, rollback revision, smoke-check status codes, and release identifiers.
- 01
Security-check and smoke-check results, plus the current approval state
- 02
The rollback revision used when a smoke check fails
- 03
Named smoke checks with actual and expected status codes
- 04
App, environment, image digest, revision, deployment time, and health-check reference
WHAT THE FOIL HOLDS
A decision, the first failed smoke row, or a pending-canary record.
- 01
ReleaseQuill validates the supplied security, smoke, approval, and rollback fields.
- 02
It applies the ordered decision table, with security failure before smoke failure and approval.
- 03
It can inspect smoke rows in order or assemble the supplied immutable release identifiers into a pending-canary record.
An action of abort, rollback, stop and escalate, promote, or hold
The first smoke check whose actual status differs from its expected status
A release record marked deployed pending canary with its rollback revision retained
RANGE SAFETY
This page does not execute the release.
For English-speaking builders who want test deployments, build evidence, and rollback notes handled in one release conversation.
- The bound package is plan-only and requires human approval before any real deployment or cloud mutation.
- The skill requires deploymentExecuted, cloudMutated, and secretsRead false and forbids calling cloud APIs from the package.
- A release record is marked deployed pending canary. Do not report it as a passed canary.
- Executing a deployment or changing cloud resources
- Replacing a missing image digest, revision, health-check reference, or rollback revision with a guess
- Reporting a pending-canary record as a passed canary
- Every app you preview stays in your own workspace, and each published link is one of our shared preview addresses rather than a hostname you control.
- Promotion beyond the preview environment requires separate authorization.
STARTER
Open a test-release conversation.
$19.00 is stated here before you register; card payment runs through Stripe Checkout inside the signed-in workspace.
$19.00 per month
Continue to workspace billingBEFORE YOU FILE A RELEASE
Questions
What can ReleaseQuill decide?
It returns abort for a failed security check, rollback or stop and escalate for a failed smoke check, promote for approval after passed checks, and hold otherwise.
How is a failed smoke check reported?
Smoke rows are checked in their supplied order, and the first row whose status differs from its expected status is returned by name.
What is stored in the release record?
The record contains the app, environment, image digest, revision, deployment time, health-check reference, rollback revision, and a deployed-pending-canary status.
Does this page execute the release?
No. The bound package is plan-only and requires human approval before any real deployment or cloud mutation.