StudioX
All missions
Engineering

Release Verification Sweep

Fixed is not verified. An agent sweeps the release being worked, separates the two, and tells whoever owns it what is actually in the way.

by StudioXNewFreeNeeds setup

What it does

An agent surveys the release currently being worked — establishing which one that is by looking it up — and classifies every issue against it: fixed but not verified, verified, or already escaped into production. Each finding is recorded, a note-writer turns the ones that matter into two sentences, and the verdict is emailed to whoever owns the release. There is no approval step. If your CI pushes a release-cut event, the mission answers it immediately from the last sweep.

How it works

For the release currently being worked, an agent sweeps the tracker and separates what is genuinely verified from what somebody merely marked fixed — plus anything that has already escaped into production against it. It writes the verdict and sends it to whoever owns the release. No approval step: it reports and stops.

How it's wired

TWO watchers and NO decisions. The first has an agent as its sensor — no tool, no fixed query — returning rows the pipeline stores. An aggregate counts what is outstanding from memory, then an act hands the finding to a NAMED second agent and an act emails the result. The second watcher is a webhook: a release cut is answered from what the sweeper already recorded. The Release desk keeps unverified fixes, escapes and verified work apart.

The team

RSRelease Sweeper

Surveys the tracker for the release currently being worked and reports what is outstanding — separating fixed from verified, and flagging anything that has already escaped.

RNRelease Note Writer

Turns a sweep into the two or three sentences a release owner can act on, addressed to a person rather than to a dashboard.

Connects to

Issue Trackerno setup

You supply

  • Who owns the release (the verdict is emailed here)required

What it watches

sweep-the-releaseagentevery 1800s

Every half hour an AGENT surveys the tracker — it works out which release is current and what is outstanding, rather than running a fixed query.

release-cutwebhookevery 120s

Receives a release-cut event pushed by your CI or release tool and answers immediately from the last sweep. Optional: nothing has to be wired to it.

What it already knows (4)

What this mission is forWhy the sensor is an agentThe webhook, and why it reads memoryWhat counts as outstanding

Data it carries

2 tables

What it shows a human

Release desk

Ask it

“Six issues are Resolved against the release and none are Closed. Is it ready to ship?”

“What is the difference between a fixed issue and a verified one, and why does it matter at a release cut?”

“An escape is already logged against the release we are about to ship. What does that change?”

“We have 10 open issues with no fix version. Do they block this release?”

“Write the two sentences you would send a release owner whose release has 6 unverified fixes.”

Before it runs, you'll

  1. 1Confirm the Issue Tracker server at import. It is credential-free and works as-is; replace the URL with your own tracker and nothing else changes — the sweeper only reads.
  2. 2Set the release owner's inbox in Configure. It is the one thing this mission asks for, and the only mission in the set that asks for anything: an email step with no recipient is a step that appears to run and reaches nobody.
  3. 3Enable the sweep observation. Enable the webhook one too if you want release cuts answered — its URL is on the Observations tab, and nothing has to be wired to it for the mission to work.
  4. 4Read the sweeper's release rules on the Knowledge tab. 'Fixed is not verified' is a convention, and if your statuses differ this is where you say so.

Import into StudioX

  1. Download the .sxm file.
  2. In StudioX → Missions → Import, drop the file.
  3. Review, finalize, and it's live — chat to it or enable the observation.

Reviews

No reviews yet. If you’ve run this mission, yours will be the first — what it handled well, and what you had to wire up, is what the next person needs to know.

Sign in to leave a review.