# C1144 — Locate each capacity-loss step in the genealogy

## Question

Why does a shared350 loss affect some rows differently and shrink downstream?

## Inputs

```json
{}
```

## Sources

```json
[
  "C1143",
  "File18 §§2.1.3,3.1"
]
```

## Opened utc

2026-09-28T05:01:19.587532+00:00

## Results

```json
{
  "step_locations": {
    "path": "model/SP_capacity_step_locations.json",
    "sha256": "d66ca2af1e2770ef2b872ecf735a4a81562fedba81a4977961c395fd244f7c70",
    "bytes": 544
  },
  "local_losses": [
    0,
    0,
    0,
    0,
    0,
    100,
    0,
    120,
    130
  ]
}
```

## Finding

The350 loss is the cumulative effect of three located changes100,120,130. Its downstream levels350,250,130 follow their positions, so the complete cap response depends on an ordered source change vector, not just its total.

## Reassessment

Test whether moving a fixed loss to a different source row preserves the cap output.

## Checks

```json
{
  "exact_locations": true,
  "sum350": true
}
```

## Closed utc

2026-09-28T05:01:19.587855+00:00

## Record provenance

Exact record hash: `d7b2958392e95807f694515f8f7cb54498944e3a67e9e7b8703b62576c957078`

Source journal: `Research_Cycles/C1132_C1431_Recovered/journal.json`