Launch operations and reliability readiness

Problem

The inspect-profiler runs database profiling, semantic typing, and generates inspector reports for analysts, but has no operational readiness for production use. There is no telemetry on profiling job durations, failure rates by warehouse type, or semantic type detection accuracy. If a profiling run times out against a large Snowflake warehouse or produces incorrect type classifications, nothing alerts the team. Support ownership for analyst-facing inspector issues — stale profiles, wrong column types, failed report generation — is unassigned. Without an incident playbook, profiling failures at launch would leave analysts with missing or misleading data quality insights and no escalation path.

Context

• Public launch for warehouse profiling, semantic inference, and analyst-facing inspect/context artifacts needs more than feature completeness; it also needs clear ownership, monitoring, support routing, and a practiced response to failures.
• Without explicit launch operations, the team will discover gaps in alerts, escalation, rollback, or user communication during the most visible part of the release.
• Expected touchpoints include dataface/core/inspect/, schema-context consumers, inspect docs, and core tests, runbooks, monitoring or review surfaces, and any launch-day coordination artifacts.

Possible Solutions

• A - Handle launch ops informally through the people closest to the code: workable for small releases, but too fragile for public launch.
• B - Recommended: define an explicit launch operations package: owners, dashboards/checks, escalation paths, rollback steps, and user/support communication rules.
• C - Delay launch until a broader platform-operations program exists: safest, but likely more process than this specific launch needs.

Plan

1. List the launch-day risks for warehouse profiling, semantic inference, and analyst-facing inspect/context artifacts, including failure modes, ownership gaps, and dependencies on adjacent teams or systems.
2. Write the required runbooks and operating checklists covering monitoring, escalation, rollback, and communication.
3. Confirm the launch support model with named owners and the minimal dashboards, logs, or review artifacts they need to do the job.
4. Run a tabletop or rehearsal pass and update the plan anywhere the team still relies on tribal knowledge instead of written procedure.

Implementation Progress

Review Feedback

• [ ] Review cleared