# Mapping Winter Fleet to PDA

The source register remains authoritative. Generated mappings are disposable analytical inputs.

| Source meaning | PDA representation attempted | Boundary |
|---|---|---|
| One commitment with a fixed weekly service window | Project task / structured scenario row | A week is not a witnessed daily start/finish. Do not claim a critical path from a constructed daily order. |
| Vessel and person demand by week | Resource-plan rows | Planned days are source quantities; actual days remain absent. Availability is relative to a declared five-day capacity basis, not a measured productivity rate. |
| Qualification and allowed vessel constraints | Source companion / reference checks | Do not assume free-text notes cause native enforcement. |
| Opening cash, receipts, vessel costs, overhead and minimum cash | Reference cash ledger; native financial tools inspected for coverage | Budget, spend and estimate-at-completion are different quantities. Opening cash is not a cost budget; receipts are not negative costs. |
| Published W05 capacity reduction | Numeric assumption baseline and later source-bound observation | This tests drift retention, not whether PDA discovered the reduction. The baseline is an explicitly identified planning assumption. |
| Additional offered work | Proposed change records and separate candidate scenarios | No automatic approval, invented risk rating or retainer income. Cost impact is calculated outside PDA and attributed to the mapper. |
| Case-defined original obligations and nonfinancial promises | Preserved source IDs and explicit reference checks | Register presence alone does not prove continuing service obligations or legitimate authority. |

If a platform interface cannot express a material source concept, the result is unavailable or a disclosed projection. No empty register will be described as evidence that the fleet is healthy.