---
name: software-release-verification
description: "Verify a software change against its source, build, installed behavior and release evidence. Use when the user requests software release verification. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.1"
---

# Software Release Verification

Verify a software change against its source, build, installed behavior and release evidence.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Change scope
- Build identity
- Test environment
- Acceptance criteria

## Methods

### Pin the tested revision

Identify the exact revision and build under test. Separate repository source, packaged application, installed version and active runtime; evidence from one is not automatically evidence for another.

### Exercise the real flow

Exercise the user-facing flow and read back resulting state. Test migration, rollback and platform parity where the change affects them.

### Isolate test data

Use isolated data for destructive scenarios and record uncertainty when an environment is unavailable. Never change production configuration merely to make a test pass.

### Report release evidence

Deliver reproducible steps, observed results and remaining risks. Passing local QA is not permission to publish, merge or deploy.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.

## Additional operational methods

Read [focused operational guidance](references/parity-and-onboarding.md) for software release verification decisions that require deeper reconciliation.