Finalize bounded typed pipeline implementation

docs/policy/architecture.md

@@ -109,6 +109,20 @@ The framework owns orchestration and handoff provenance. Modules return logical
 results and warnings; they do not own CLI reporting, workspace paths, durable
 file placement, checkpoints, or diagnostics.
 
+After pipeline-wide chunking, extraction uses bounded framework concurrency.
+One run-wide worker pool receives chunk-scoped lane jobs in deterministic
+chunk-first, lane-second order. A lane may begin its merge and normalize
+continuation only after all of its extract jobs are terminal; that continuation
+remains serial within the lane, while bounded continuations for different lanes
+may overlap. The framework must not create unbounded goroutines per lane or
+chunk.
+
+Completion timing does not choose public ordering or errors. The coordinator
+orders accepted artifacts, warnings, rejections, checkpoint events, and
+framework errors by stable pipeline scope. Rejections do not cancel unrelated
+work. A framework error cancels derived work, prevents undispatched work from
+starting, waits for started work, and prevents output encoding.
+
 ## Validation
 
 Validation is a framework-managed boundary around outputs from chunk, extract,
@@ -144,6 +158,11 @@ LLM calls and other external operations accept cancellation and respect
 timeouts. Concurrency control belongs in shared runtime plumbing rather than in
 individual modules.
 
+The application-wide LLM scheduler bounds actual provider calls independently
+of framework worker limits. Every LLM-backed module, retry, and validator uses
+the single injected scheduled client, including work performed by overlapping
+lanes.
+
 ## Configuration And Provenance
 
 Configuration loading, precedence, defaults, environment overrides, redaction,