Back

Book companion · editions

Edition lineage: from recovered draft components to the working public edition

The book did not appear as one single final file. DEPTH-09 preserves the lineage: individual chapter sources, first full draft, edited manuscript, formatting copy, public excerpt, designed preview, and the later Full Designed Manuscript Edition v1.0 identity. Each stage means something different.

Component source lineage

Recovered source includes an accepted Opening, a separate Table of Contents, and exact Chapter 1→34 files. These are strong provenance because the chapter order and individual source hashes can be checked without depending on one later composite file.

First Full Draft → Edited → Formatting

The recovered sequence includes First Full Draft Master v0.1, Edited Manuscript v0.1, and Formatting Working Copy v0.1. These should remain distinct. Editing and formatting are later transformations of the manuscript lineage; neither erases the earlier draft.

Public Excerpt v0.1 and Extended Manuscript Preview v0.2

The public-excerpt stage is historical. A later designed Extended Manuscript Preview v0.2 expanded the public framing and explicitly said it was a developing manuscript preview rather than a short final excerpt. DEPTH-09 keeps both in the edition record.

Full Designed Manuscript Edition v1.0 — strongest current reader identity

The recovered parsed Library source identifies a complete designed manuscript edition, typeset across 9 Parts and 34 Chapters, shared as a Working Public Edition for early reading, reflection, and project transparency. It is still not a final printed publication and may be edited, reduced, reordered, or revised.

Raw-byte limitation in this DEPTH-09 run

The v1.0 working-public-edition identity is verified from parsed Library content, but its raw file bytes could not be materialized in this run. DEPTH-09 therefore does not invent a v1.0 SHA-256. Exact raw hashes are recorded only for recovered files that are actually present in the working container.

The 90-chapter institutional Master Document is not this reader edition

A later institutional Master Document lineage reaches a different 90-chapter governance/architecture structure. It must not be merged with the 34-chapter foundational reader. The two documents can cross-reference each other later while retaining separate identity and version control.

Reflection

Questions to sit with

  1. Which exact edition am I reading?
  2. Is a later file a content revision, a formatting transformation, or only a public packaging change?
  3. What earlier edition must remain preserved for provenance?

One safe next action

Check the Edition Lineage JSON before naming any manuscript file 'final'.