Competencies, Evidence, and Remediation
Reach level 2 or better in every competency, pass the lab contracts, complete the capstone and solve a delayed unseen transfer. Do not average a missing invariant into a passing overall score. These levels describe module evidence, not professional rank or an elite-percentile guarantee.
| Competency | Evidence | Critical failure | Repair |
|---|---|---|---|
| C1: ordered invariants | A1, P1–P3, Lab A | Local-only ordering; stale metadata; missing deletion repair | Derive rotation and inspect full structure after every update |
| C2: partition semantics | A2, P5–P7, Lab B | Repeated union changes size; DSU used for unsupported deletion | Independent component oracle and event contract |
| C3: heap ownership | A3, P8–P10, Lab B | Donor aliasing; wrong degree/cardinality; unqualified heap bound | Carry trace, all-live-heap ownership checks, operation mix |
| C4: amortized proof | A4, P11–P14, Lab C | Mixed units; dropped initial potential; mean mistaken for proof | Full cost ledger and telescoping cases |
| C5: range algebra | A5, P17–P18, Lab D | Reversed tags; ignored length; zero assignment lost | Derive action/composition and compare mixed operations |
| C6: historical isolation | A6, P19, Lab D | Old root mutated; branch silently uses latest | Recheck every retained version and sharing |
| C7: filter lifecycle | A7, P16, Lab E | Bloom positive treated as exact; stale negative shortcut | Exact confirmation and safe publication |
| C8: model/transfer | A8, P4/P15/P20, capstone | Expectation claimed deterministic; payload hides storage costs | State probability/resource model and adapt to changed requirements |
Levels
- 0 — invalid or absent: a critical contract or invariant fails.
- 1 — assisted: follows known traces but needs help deriving or repairing.
- 2 — independent: explains contract/invariant, implements required behavior, supplies relevant proof and independent checks, and passes a fresh equivalent task.
- 3 — transfer: adapts to a new requirement with revised invariant, API, resource argument and verification, without copying the original solution.
A clerical error can be repaired with a fresh numeric example if the model is sound. A conceptual error requires a fresh operation sequence and explanation. Use the scoring key after a preserved attempt. Source review checks complexity and independence beyond the finite tests.
Acceptance and remediation
All eight core classes must satisfy public and inspection contracts; importing the reference or delegating the intended structure to a library is not an independent implementation. Test state transitions, not only final outputs. Preserve any real bug, minimal sequence, invariant repair and a successful recheck. There is no arbitrary mistake quota or timed memorization gate.
After 7–14 days, solve a fresh transfer: rollback connectivity, add a shrinking array with hysteresis, a noncommutative segment query, versioned range updates, or a filter rebuild preserving negative safety. Define its additional assumptions before coding. Record assistance and rescore the affected competencies.
Independent review, grading agreement and learner-pilot evidence remain pending; use the instructor guide to record actual outcomes and workload.