Instructor track
Run of show, shared-service contract, publication gates, and module-by-module facilitator notes.
Use this track beside the learner playbook. Each of the eight module pages contains only the four operating sections Timing, Talk track, Common failures, and Reset steps, and names the evidence that proves completion.
Run of show
The facilitated session is 3 hours 45 minutes plus a 15-minute break. Module 00 is 25-45 minutes of prework and should be complete before the live clock starts.
| Module | Budget | Hard gate |
|---|---|---|
| 00 — Enter the room | 25-45 min prework | New workspace and MigrationRoom dashboard are ready |
| 01 — Source baseline | 20 min | Step 1 shows live counts, types, and Databricks-specific features |
| 02 — Review and approve design | 40 min | A human challenge is resolved before DDL approval |
| 03 — Migrate, validate, rewrite | 45 min | Migration and Validation views pass; rewrites are reviewed |
| Break | 15 min | Use only after the migration is visibly progressing or complete |
| 04 — Benchmark | 25 min | UI correctness and timing context precede latency interpretation |
| 05 — Multiple catalogs | 35 min | Unity, REST, and native inputs are queried live through chat |
| 06 — Native hot path | 40 min | One approved native optimization is proved and re-benchmarked |
| 07 — Defend and teardown | 20 min | UI checkpoints are reviewed and participant resources are removed |
Pairs use two roles: the migration operator controls the MigrationRoom dashboard; the design reviewer challenges schema, correctness, and claims. Swap roles after Module 02. Assign one room lead to call hard gates and one support lead to handle credentials and spare resources without seeing participant evidence files.
Shared REST catalog contract
Prepare one instructor-owned, read-only Iceberg REST catalog that ClickHouse Cloud can
reach. Before Module 05, attach both that catalog as rest_catalog_tpch and the
workshop's Unity Catalog as unity_tpch on each participant ClickHouse service. Publish
only the non-secret contract: catalog kind, namespace, table name,
expected row count, deterministic checksum or result hash, refresh timestamp, and the
ClickHouse version/settings used in rehearsal. The canonical exercise expects a nation
reference table compatible with queries/04_attach_rest_catalog.sql.template and
queries/05_hybrid_query.sql.template.
Keep URI, warehouse identifiers, and short-lived credentials in the instructor's secure setup path, not learner chat. Verify separately that each attachment can list catalog metadata and read the underlying objects; either capability alone is insufficient. Keep a reset script or documented fixture rebuild procedure outside participant repositories. Do not destroy the shared REST fixture during learner teardown.
Room readiness
- Keep one pre-provisioned Databricks workspace and SQL warehouse plus one spare ClickHouse Cloud service. Distribute access privately and record who received it.
- Test the selected MigrationRoom LLM provider before doors open. Keep a spend-capped fallback key and confirm the Databricks and ClickHouse tools are visible to the agent.
- Preflight the venue network from ClickHouse Cloud to the REST fixture, not merely from the instructor laptop.
- Keep redacted screenshots of each MigrationRoom step for explanation during an outage. Screenshots are never substitute evidence for an unexecuted learner step.
- Collect the selected run ID, conversation link, redacted UI checkpoints, and decision records through the approved secure channel. Reject tokens, passwords, authorization headers, and signed URLs before collection.
Publication gates not verified locally
This repository does not prove live cloud behavior. Before publishing or marketing a delivery, an instructor must execute and record these gates against the exact delivery versions:
- a live six-step Databricks migration through MigrationRoom;
- successful Terraform apply and destroy for the new-workspace setup path;
- Unity attachment against the delivery ClickHouse Cloud version and settings;
- shared REST catalog reachability and object reads from ClickHouse Cloud;
- all result invariants before and after optimization; and
- a timed two-person rehearsal that fits the 3-hour-45-minute facilitated agenda.
Mark a failed or skipped gate as not executed. Do not convert a demonstration,
screenshot, terraform validate, or local unit test into a claimed live-cloud result.