Migration-pack certification
Repeatedly prove six executable source packs without overstating live-source, client, or production readiness.
Migration-pack certification
Run one recurring suite across the SQL Server, Snowflake, Redshift, Oracle, Teradata, and Hadoop packs:
pnpm certify:migration-packsThe runner uses credential-free fixtures and local adapters. It writes a report and an
evaluator input for each source under reports/. These artifacts prove repeatable
product behavior for the bound build and fixture; they are not client acceptance or
production evidence.
Required stages
| Stage | Required behavior |
|---|---|
| manifest | validate source, variant, inventory, dependencies, and hard-case labels |
| native inventory | retain SQL, procedural, orchestration, utility, policy, and consumer objects |
| dependency compilation | produce a stable order and fail closed on missing nodes or cycles |
| routing | classify every object as deterministic, bounded-agent repair, or human remediation |
| CLI and governed API | preserve schemas, exit behavior, tenant scope, identity, artifact digest, and idempotency |
| App workbench | expose all six packs, required hard cases, commands, and proof boundaries |
| transfer | prove snapshot, catch-up, checkpoint, restart, late data, deletion, and reconciliation behavior |
| validation and deployment | require Experiments evidence and Runway-owned immutable deployment inputs |
| cutover | retain approval, denial, expiry, replay, uncertain-result, compensation, and rollback controls |
| scale | compile a 10,000-object estate for every source without scope or target-map loss |
Source-specific corpus
| Source | Examples that must remain covered |
|---|---|
| Microsoft SQL | collation, identity, temporary tables, dynamic SQL, SQL Agent, SSIS, SSRS, linked servers |
| Snowflake | VARIANT, timezone, scripting, tasks and streams, stages and pipes, Snowpark, sharing |
| Redshift | distribution and sort behavior, SUPER, Spectrum, COPY/UNLOAD, WLM, S3 restart manifests |
| Oracle | NUMBER and DATE/null semantics, PL/SQL packages, exceptions, database links, scheduler, SCN catch-up |
| Teradata | SET/MULTISET, primary index, QUALIFY, BTEQ, load utilities, volatile tables, utility restart |
| Hadoop | Hive and Impala, metastore, partitions and files, Oozie, Pig, Sqoop, Spark/MapReduce, UDF/SerDe, Ranger/Sentry |
Removing a required case blocks hermetic certification even when every command exits successfully.
Proof boundary
hermetic_proven is the account-independent ceiling. It covers the compiler, routing,
transfer simulation, integration contracts, governed paths, UI, scale, and failure
behavior for the bound fixtures.
workspace_proven additionally requires immutable evidence from real workspace
inventory, target materialization, Experiments validation, Runway promotion, and a
cutover rehearsal. An App deployment alone does not satisfy workspace proof.
The evaluator structurally rejects client_proven and production_certified. Those
levels require representative source behavior, client acceptance, current rollback
evidence, production authority, and a certified effector.
Every admitted stage records a reference, digest, build reference, dataset reference, tool version, completion time, and assertions. Store reports in an immutable CI artifact store; do not derive client-readiness or time-savings claims from fixture evidence.