# C1310 — Register why reversal does not commute with grouping

## Question

How does sourcepartition remainvisible in theinversefamily?

## Inputs

```json
{}
```

## Sources

```json
[
  "C1309",
  "File52c §3",
  "C1058–C1068 inherited"
]
```

## Opened utc

2026-09-28T06:12:27.572695+00:00

## Results

```json
{
  "partition_relation": {
    "path": "model/relation_inverse_partition.json",
    "sha256": "66d109ae0238a81f415ee8847be71eabc366b94683328289ae877a38ffe77ef5",
    "bytes": 602
  },
  "whole_image": 7200,
  "part_total": 10620
}
```

## Finding

Theoriginal2700 reverses to7200, whileits1650|1050 parts reverseto5610|5010,total10620. Thisexistingdifference explainswhy thenamedcuts mustremain in thecommonrepresentation.

## Reassessment

Register theCovenantjoins asdefinedrelations plusoneadditional sourcecondition.

## Checks

```json
{
  "whole7200": true,
  "parts10620": true,
  "different_routes": true
}
```

## Closed utc

2026-09-28T06:12:27.573381+00:00

## Record provenance

Exact record hash: `76d002bf9322d42294939d4e6ce8bdbcbc4fc44dd233339387c98eff47416993`

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