Safe automatic defaults

Historical preservation stays out of the live request path

SARCH captures page evidence, resources, network exchanges and replay metadata for historical inspection, but automatic preservation is rate-limited so it cannot outrank running projects.

Automatic capture is conservative: startup capture is off, scheduled capture is spaced by hours, and hard hourly page/screenshot budgets limit background work.

Snapshots can preserve DOM, screenshots, resource bodies, network/API exchanges and WebSocket transcripts so older versions remain inspectable beyond a flat image.

The Three.js inspector reconstructs captured component geometry and links UI regions to archived endpoints/resources with English metadata for deeper inspection.

Deep or forensic capture is an explicit/manual choice. SARCH scheduling and backup work run separately from the RC project serving critical path.

/schx/docs/behind-the-scenes-current