A shadow release turns documentation into evidence by making the incoming owner perform the agreed path while the outgoing maintainer observes without carrying the work.
Choose a safe production-shaped path
Select the next normal release, a staging promotion with equivalent controls, or a reversible production change small enough to observe. Define the candidate revision, environment, change window, approvals, expected checks, rollback target, and stop conditions before starting. Do not invent a high-risk release merely to make the handoff exercise feel realistic.
The incoming owner drives from the written runbook. The departing maintainer may answer questions but should not type commands, supply unrecorded local configuration, or silently fix permissions. Every intervention becomes a gap in the transfer record. This makes the exercise useful even when the release succeeds, because the evidence shows how much hidden assistance the path required.
Capture control and observation evidence
Record who approved the release, which identity ran each action, the revision and artifacts deployed, the observable service checks, monitoring links, and final disposition. Store secret names and custody without exposing values. GitHub recommends least-privilege credentials and notes that organization, repository, and environment secrets have different scopes, which should be reviewed during ownership change.
Exercise the rollback command or a safe rehearsal when the production path cannot be rolled back solely for testing. Verify that the incoming owner can find the previous artifact, understand data or schema constraints, and name the person authorized to decide. A runbook that says only to revert leaves the critical recovery decision implicit.
Accept gaps explicitly
Classify each interruption as missing access, missing instruction, stale command, unavailable dependency, unclear authority, or unexpected system behavior. Give it an owner and a condition for closure. The buyer may accept a known exception, schedule remediation, or hold the transfer. Do not rewrite the receipt to make a partial rehearsal appear complete.
Reality Contact, LLC facilitates the shadow release for Release Custody Record. The buyer remains release authority and can stop the exercise at any time. A successful run shows that the agreed path worked under named conditions; it does not certify the whole application, eliminate incident risk, or prove that every future release can be performed without new information.
Where the service stops
Reality Contact, LLC documents and facilitates a software ownership transfer but does not give legal advice, determine intellectual-property title, warrant the software, certify security or compliance, hold production credentials after the engagement, perform unilateral access revocation, or guarantee a release will be incident-free. The buyer names the authorized incoming owner, secures cooperation from current custodians, approves account and repository changes, performs the shadow release, accepts or rejects exceptions, and directs the relevant providers to revoke or reassign prior access. This operational handoff service does not replace legal, intellectual-property, security, compliance, employment, finance, provider, or incident-response review. The buyer controls every repository, account, credential, release, acceptance, and access decision; private materials wait for secure intake and written deletion terms.
Sources: GitHub Actions secret scope and least-privilege guidance; CISA operational vendor offboarding guidance.