# C1075 — Manuscript: Why the cap cannot identify the ancestral ledger

## Question

Does this section accurately connect its complete source family to the shared explanation?

## Inputs

```json
{
  "draft_sha256": "8e445426a955b7c62729cf55f9655ec1bf882b7d2a9c0c9cd08897355b525bae",
  "module_index": 3
}
```

## Sources

```json
[
  "C1071",
  "prep/manuscript_sp.json"
]
```

## Opened utc

2026-09-28T04:14:01.107960+00:00

## Results

```json
{
  "section": {
    "path": "deliverables/sections/04_sp_4.md",
    "sha256": "8f97be1b3ece6328c7fbf438a2b7a09df19629ffc816fa850fe654d5e1185318",
    "bytes": 1490
  },
  "body_words": 204,
  "source_references": 2
}
```

## Finding

The information-loss section explains why the same SP result cannot choose between MT and main LXX ancestral baselines, and separates a cap from an invertible translation.

## Reassessment

Reassess the next explanatory section against its source roles and the sealed calculations.

## Checks

```json
{
  "baseline_difference": true,
  "both_main_values": true,
  "history_limit": true
}
```

## Closed utc

2026-09-28T04:14:01.108582+00:00

## Record provenance

Exact record hash: `f36f34e26202324ebbd23d8dde946c50037a27eec6599fa5d605bbb163692f92`

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