Test before commitment
A known canary exposes missing relations, history or custom data while the buyer still has leverage.
ExitCanary places a known synthetic CRM dataset inside a SaaS trial, examines the vendor export and produces a reproducible answer about what survived the exit.

ExitCanary checks records, identifiers, relations, timestamps, Unicode, custom fields, history and attachment evidence against a known source pack. GPT-5.6 helps interpret unfamiliar field names; the human confirms the map before deterministic evaluation.
The public demo uses disclosed bundled fixtures and no paid model call. The repository documents the optional live semantic-mapping path separately.
The prototype shifts exit fidelity from contract language to a repeatable piece of product evidence.
A known canary exposes missing relations, history or custom data while the buyer still has leverage.
GPT-5.6 proposes evidence-referenced mappings, but unresolved meaning remains visible and human-confirmed.
The result binds canary, packet, mapping and evaluator versions so a changed export can be tested again.
ExitCanary is not a universal portability auditor, legal compliance guarantee, source attestation or proof that a vendor generated an export honestly. The current normalizer supports a bounded CRM profile and rejects unsupported ambiguity.
ProofLatch governs release evidence, Gatehold governs agent clearance and AccessCrash tests human reachability.