wiki/decisions/ADR-007-merge-storyboard-and-layout-modules.md
ADR-007: Merge Storyboard and Layout Modules
Date: 2026-06-04 Status: Accepted
Context
The per-book factory had separate operational modules for page planning (M8), page specs (M9), page composition (M13), and book assembly (M14). Review showed that M8 and M9 are one storyboard decision surface, while M13 and M14 are one layout/production surface.
Decision
Merge M8+M9 into one Storyboard Plan + Page Specs module, and merge M13+M14 into one Layout + Assemble Book module for pilot operations and founder review.
Rationale
Splitting M8 from M9 repeats context, adds a redundant LLM/review pass, and risks drift between page role, on-page text, and image direction. Splitting M13 from M14 creates an artificial handoff between composed pages and the actual deliverable: the digital PDF and preview. The underlying artifacts (PagePlan, PageSpecs, FinishedPages, Book) may remain for contracts, tests, and migration safety.
Alternatives Considered
| Option | Why rejected |
|---|---|
| Keep all four as separate modules | Too granular for pilot operations; increases gates and repeated context. |
| Delete the folded artifacts entirely | Too disruptive to existing tests, step files, and migration path. |
Consequences
The product spec is now v1.1. Former M9 and M14 are deprecated as separate operations but can remain temporarily as implementation details. The active operating pipeline treats M8 as the storyboard gate and M13 as the layout/book assembly blocker.