Christopher M. Punches
298f4d5afe
The overview had been restructured around a named three-layer model — user, developer, filesystem — that was never part of the design. The underlying point stands: a reader must be able to tell whether a given statement applies to them, and a code-level symbol must never appear in prose without saying whose vantage point it belongs to. Sections are now named for the reader they address rather than for a tier: "Running the dpm binary", "Writing a program against libdpm-core", "What DPM reads and writes on disk". The remaining uses of "layer" are the capability-growth layers the design already defines. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
