
Credit / board support from retained versions. Local synthetic proof is separate from financial-owner and client IT acceptance.
Quarter review · Board support · Original / replacement example
Training completion requires the associate to repeat this exercise and a named owner to record the date and result. This guide alone is not evidence of completion.
The client owns the data and receives perpetual deployment rights. NSigma support is optional; hosting, database, backups, security updates, identity and third-party services remain operating responsibilities and costs. Perpetual deployment rights do not imply source-code ownership.
Maintain a dedicated client environment and named preparer/reviewer/read-only access. Keep credentials outside source control; restrict exports and backups as client financial data. Back up PostgreSQL, which contains retained uploads and artifacts, and separately preserve deployment configuration and secrets in the client's controlled vault. Keep the administrator's originals as the system of record.
Agree retention, recovery time and recovery point objectives, backup encryption/off-site storage, key rotation, patch ownership and escalation contacts. Before an upgrade, take a backup, rehearse migrations on a disposable copy and verify retained issued downloads. Never reseed a book containing uploads. Exercise recovery before accepting an upgrade or handover.
From the isolated checkout, run node scripts/rehearse-client-recovery.mjs. It accepts no target overrides. It checks practice ownership, takes a consistent read-only snapshot, and restores into a uniquely named new database on the owned local container. It refuses existing destinations and never restores over practice or presentation.
The command reports the private receipt location. Compare its source/destination identities, row counts and content hashes, including retained financial and artifact bytes. Retain the dump and receipt under the client-approved retention policy. The disposable database and private dump remain for inspection; cleanup is a separately controlled operator action.
This proves the exercised local logical recovery only. Client infrastructure, secret recovery, off-site backups, failover, security assessment and client recovery objectives need a separate witnessed rehearsal.
Financial owner: compare the agreed completed quarter with the administrator's source, record differences, accepted scope and sign-off. Client IT: witness restore, access setup, upgrade and incident procedures. Associate: demonstrate upload and correction. Record actual names, dates and evidence in the client acceptance record; blank fields are not approvals.
Live email remains disabled. Form 1031 live-export approval remains gated pending administrator-reviewed historical evidence and accepted edition/license format. Partner capital schedules, dated equity XIRR and the full LP pack remain unavailable pending separately accepted Sprint 4 work.