# PLO — Session 6: Economics and vendor lock

**CLO:** By the end of this session, the student can build a monthly TCO across a three-provider stack, move the catalogue service to a second independent provider, score the move on five portability dimensions, and defend an exit strategy with numbers.

| PLO | Role | Research answer | Lab evidence | Points | Evidence | Rubric |
|---|---|---|---:|---:|---|---|
| PLO1 | primary | 4 | 0 | 4 | An 800–1,200-word answer that defines a portability score, applies it to the S6 move to Linode/Akamai and sets a threshold, with 5–8 sources | Research 4/3/2/1 |
| PLO3 | secondary | 0 | 3 | 3 | The five-line TCO and the Linode column, the weighted portability scorecard, the archive-trap log, the moved-data checksums and the teardown log | Lab 3/2/1/0 |
| **Total** | | **4** | **3** | **7** | | |

**Total: 7 points**

## Four-level descriptors

**Research (4/3/2/1).** 4 = a defined portability score with weights, applied to the move, with a threshold and a named action; independent evidence on egress, identity, managed-service equivalence and data-transfer effort. 3 = a sound score with some application and a threshold. 2 = describes lock-in but does not produce a usable score. 1 = a summary with fewer than five sources. 0 = nothing submitted or misconduct.

**Lab (3/2/1/0).** 3 = the TCO reconciles to a monthly figure and the $80 spine delta is explained line by line, the scorecard is weighted with rationale, the catalogue runs on Linode with S3-backed storage, the archive trap is diagnosed and fixed, the moved data is verified, and teardown and cost are respected. 2 = mostly complete, one check thin. 1 = a partial table, an unscored scorecard, or an incomplete teardown. 0 = nothing submitted, unsafe data, or no teardown.

The full course arithmetic is in `production/baseline.md`; this file is the weekly instance.
