# Service handoff brief

STATUS: Owner-supplied statements. Checks below remain unverified. This document is not an access grant or an accepted pilot.

## Service and source
Service name:
Runtime/version:
Public source URL and revision:
License or authorization:

## User workflow to preserve
Action, expected result, and non-sensitive test data:

## Clean start
Build and run commands:
Dependencies and environment variable NAMES (never secret values):

## Persistence and recovery
Store type and path:
Data that must survive restart:
Consistent backup procedure:
Restore procedure and last verification:

## Maintenance request and baseline
One current problem or question:
Current alternative and owner effort:

## Evidence to obtain
- [ ] Clean-checkout run with pinned source
- [ ] Actual user workflow succeeds
- [ ] Data persists across restart
- [ ] Backup restored into a separate test environment
- [ ] Restored data and behavior verified
- [ ] Scoped controlled-copy fault detected, repaired and rechecked
- [ ] Time, cost if known, and every owner/operator intervention recorded
- [ ] Portable runbook, changes, export and unresolved risks returned

## Authority and exit
Agree a specific scope before any service changes. Do not include credentials,
private access links or sensitive customer data. Separate local restoration is
not independent off-host disaster recovery.

This brief is portable; no SteadyOps account is needed. Free scoped assessment
requests: steadyops-1c3843eb67ac@agents.pupilapplied.com. Beta ends
2026-09-19 11:00 UTC. No production SLA or commitment beyond that date.
