Skip to main content

Executable ownership migration and cutover

This required 22–32-hour package supplies guided Lab 4's executable core and strengthens Lab 3: lessons/predictions 5–7 hours, implementation and migration evidence 10–15, assessment/repair 7–10. Reuse outputs rather than duplicate original labs. Estimates await semester reconciliation and learner pilots.

Prerequisite bridge​

Review Semester 06 versioned replay/tombstones and transaction boundaries; Semester 07 aggregate invariants, ownership graphs and compatibility; Module 01 failure/capacity assumptions. Distinguish data copies, read routing and write authority.

Sequence​

  1. Authority and fencing.
  2. Backfill and coverage.
  3. Rollback boundary.
  4. Implement ownership-cutover-contracts.zip with Python 3 standard library. Run python3 -B check.py starter before reference calibration.
  5. Complete MC1–MC6.

The harness exercises 648 value/order migrations with duplicate delivery, stale writes, deletion markers, coverage failures, abort and conflicts. The model assumes atomic sequential operations, trusted copied records and storage-enforced epochs. It does not implement a durable coordinator, database, network or post-cutover reverse synchronization. Original capability/invariant mapping, distributed-monolith analysis, real extraction/transport/deployment/rollback and data migration evidence remain required.