DOC-ID: KL-RUNBOOK-2026-R1 PACKABLOCK LLC · SEATTLE, WA

Developer Diligence & Offboarding Specification

This specification outlines the technical, financial, and legal workflow for sunsetting an application through Keelout without transferring legacy source repositories or exposing customer PII prior to definitive execution.

1. Zero-PII Discovery & Synthetic Schema Audit

During Phase 1 diligence, Keelout inspects only aggregate telemetry (30/60/90-day active session counts, route frequency, and database table schemas). Our local CLI sanitizer generates a deterministic synthetic fixture of your schema so potential category acquirers can build their ingestion mapper without touching raw customer records.

2. Segregated Reserve & Milestone Disbursement Structure (70 / 30)

3. The Dynamic Edge Bridge (Web & Mobile Apps)

Developers do not build bespoke migration UIs. For web applications, you embed a single script tag (<script src="https://cdn.keelout.com/v1/bridge.js"></script>) in your application header. For native mobile apps (iOS & Android), Keelout provides a lightweight hosted WebView modal or JSON config endpoint that displays the same accessible, co-branded transition notice. Users receive 1-click GDPR Article 20 data portability, workspace export downloads, and frictionless opt-in switcher onboarding to the successor platform.

4. NIST SP 800-88 Sanitization & 60-Day Domain ROFR

At T-Zero, production volumes, replicas, and automated snapshots are cryptographically purged in accordance with NIST SP 800-88 Rev. 1 guidelines, and a signed SHA-256 attestation certificate is issued to the developer. If a domain is included in the transition, it is bound by the Keelout Anti-Slop Covenant and a perpetual 60-day Right of First Refusal (ROFR) at $0 reclamation cost.

Return to keelout.com