Document ordered pipeline operations and retire sequential examples

docs/internal/state.md

@@ -32,6 +32,17 @@ The serialized
 `workspace_schema_version` identifiers are frozen wire-compatibility fields;
 they do not describe a current public state surface.
 
+Ordered-step lane checkpoints include the step identity in their storage scope.
+When a later lane consumes a generated artifact, its dependency fingerprints
+include the producer's artifact kind, complete schema identity, media type,
+canonical content digest, and size. A producer checkpoint may be decoded through
+the registered codec and handed off without rerunning it. Missing, rejected,
+corrupt, incompatible, or changed producer state produces a bounded
+`dependency_invalidated` decision for every transitive dependent lane; it does
+not permit stale downstream reuse. The CLI's selective recomputation policy
+records `forced_recompute` for the selected step and its dependents while
+requiring compatible predecessor checkpoints.
+
 `internal/core/fileio` provides confined atomic file writes used by state
 collaborators. The chunk-plan store retains its stronger entry validation.
 
@@ -48,6 +59,11 @@ boundaries redact sensitive metadata and credential-shaped bytes while allowing
 application-owned trace material. Debug data is never a checkpoint source or
 cache input.
 
+Generated reference bytes exist only in cloned operation requests and are not
+written as paths into checkpoints, manifests, or debug summaries. Those state
+surfaces retain canonical identities and bounded producer provenance so that a
+resume decision can be explained without copying generated campaign content.
+
 After allocation, one CLI-owned state value accumulates the known report paths,
 pipeline outcome counts, and validation status. A single guarded terminalization
 operation writes the success report, or makes one attempt each to write the