archivist-fragile-hotspot-auditor

Auditing fragile state paths involves tracing data from source-of-truth documents, UI state, API contracts, and local persistence to surface data-loss and stale-state conditions. The process collects concrete evidence, reproduces steps, and generates risk severity with remediation guidance.

Cross-tab synchronization risk analysis detects data-loss and state corruption across runtime boundaries by tracing state lifecycle dependencies. It evaluates autosave, editor sessions, workspace tabs, and route identity to surface stale-state conditions and fragile persistence paths.

Identify data-loss risks by tracing data flow from source-of-truth docs and API contracts to local persistence across autosave and editor sessions. Collect concrete evidence, reproduce failure steps, and generate risk severity findings aligned with audit reporting requirements.

Yes, you can audit workspace tabs and route identity without editing code by tracing state paths across runtime boundaries. The evidence-first approach collects concrete findings, reproduces steps, and generates risk severity reports referencing the archivist-audit-report contract.

Structure audit findings by aligning with the archivist-audit-report contract. Generate reports containing concrete evidence, reproduced steps, risk severity levels, and remediation pointers to maintain consistency with existing audit reporting requirements.

Cross-tab state corruption occurs when local persistence and API contracts fall out of sync with source-of-truth docs across runtime boundaries. Tracing data flow through autosave, editor sessions, and route identity surfaces the specific stale-state conditions causing data loss.