Review and release an integration

A green Vise result is ready for human review; it is not a release approval. Start with the lifecycle summary so the reviewer sees the smallest missing action without collapsing independent claims:

vise status . --format human

Ask for a release handoff

Using Vise, prepare this social.plus change for release review. Summarize
what changed, the SDK boundary, evidence, regressions or waivers, and the
decisions a person still needs to make. Do not claim human approval.

If your team has an approved Vise handoff, provide it so the candidate can be compared with that known point.

What the reviewer should receive

What changed? The accepted feature scope, placement, target, source, and dependency changes.
What proves it? Automatic checks, project sensors, attestations, and a source/build/route/target-bound runtime receipt—or clearly disclosed waivers.
What moved? SDK knowledge and fact depth, organization policy, evidence freshness, residual risk, or previously completed behavior that differs from the accepted candidate.
What remains human? Product QA, security review, risk acceptance, and release approval.

An optional Integration Passport packages the candidate’s intent and evidence into verifiable claims so another reviewer can detect changed or stale material. A verified runtime receipt proves that its retained evidence still matches the recorded build and surface; it does not prove visual quality, every SDK behavior, or release approval. Organization Policy Operations likewise identifies accepted, changed, expired, superseded, or revoked policy and routes the exact owner without accepting an update automatically.

Read the decision

Decision	Meaning	Human action
`ready`	No blocking automated regression was found	Complete normal product, security, and release review
`review-required`	Valid evidence contains SDK, policy, lifecycle, or provenance movement	Review the disclosed changes and owners
`blocked`	Required evidence, policy, or trusted provenance is missing	Resolve the named blocker and prepare a new candidate

Vise never records or impersonates human approval.

Advanced release controls and commands

Policy Packs can declare approved SDK ranges and required evidence. Trust envelopes can authenticate a reviewed Passport or Policy Pack across teams or CI systems. A valid signature proves provenance, not integration correctness.

vise policy status . --ci --format human
vise sdk-release . --format human
vise smoke verify . \
  --evidence sp-vise/evidence/runtime-smoke/<surface>.json
vise passport . --write
vise passport verify . --format human
vise passport compare . \
  --from <approved-passport.json> \
  --to <candidate-passport.json> \
  --format human

Policy status exits 0 for ready, 12 for review-required, and 13 for blocked. Accepting a reviewed repository policy source is a separate CLI-only write with vise policy accept; its receipt proves the recording action, not release approval.See the command reference for policy, trust, and CI options.

Keep the candidate Passport and comparison when used, the committed sp-vise/ evidence, CI output, applicable policy files, and the approval recorded by your own release process.

Keep integrations verified in CI

Reproduce the checks in the release pipeline.

How Vise works

Understand result states and their human-review boundary.

​Ask for a release handoff

​What the reviewer should receive

​Read the decision

​Related

Keep integrations verified in CI

How Vise works

Ask for a release handoff

What the reviewer should receive

Read the decision

Related