# Units Generation — Questions

> Fill in each `[Answer]:` tag. Options A-E plus X (Other). The file is the
> authoritative record of your unit-decomposition decisions.

## Q1: Unit boundary strategy

How should the build units be drawn from the three components (Generator, AiDraft, Funnies)?

A) One unit per component: `generator`, `ai-draft`, `funnies` — each is a separately buildable piece (recommended; clean mapping to Domain Design)
B) One single unit containing all three components (coarse — simplest, one deliverable)
C) Split finer: e.g. `layout`, `render`, `content-loader`, `puzzle-gen`, `cartoon` sub-units
X) Other (please specify)

[Answer]: A

## Q2: Unit granularity

How fine-grained should the units be at build time?

A) Coarse — a handful of units corresponding to the components (3 units) (recommended for a small local tool)
B) Fine-grained — split each component into smaller buildable pieces for maximum reuse/testing granularity
X) Other (please specify)

[Answer]: A

## Q3: Integration points / contracts

How should the units share data and integrate (the contracts between them)?

A) A shared internal interface/module boundary per component (Generator calls AiDraft and Funnies via defined entry points; the DraftBundle JSON is the review handoff contract) (recommended)
B) Loose — units communicate only through files on disk, no shared code interface
C) A package-manager-style library dependency (one unit imports another as a package)
X) Other (please specify)

[Answer]: A

## Q4: Deployment model

For this fully-local tool, what deployment shape should the units take?

A) Embedded/static — one `newspaper` command + templates, all bundled; single local deliverable (recommended, matches CLI-first file-only posture)
B) Split executables that each run independently (no benefit here, but if preferred)
C) Library + thin CLI wrapper (the generator logic as a reusable library, plus a thin `newspaper` script) 
X) Other (please specify)

[Answer]: A

## Consolidated Summary Confirmation

> Summary of your four decomposition answers before the unit artifacts are generated:
>
> - Boundary strategy: **one unit per component** — `generator`, `ai-draft`, `funnies` (Q1=A)
> - Granularity: **coarse** — 3 units corresponding to the components (Q2=A)
> - Integration/contracts: **defined internal interface boundaries**; the DraftBundle JSON is the review handoff contract (Q3=A)
> - Deployment: **embedded/static** — one `newspaper` command + templates, single local deliverable (Q4=A)
>
> Plan approval: the human pre-approved the decomposition plan (answers recorded via the file, self-guided mode).

Does this all look correct before I generate the unit artifacts?

- Looks correct
- Request changes

[Answer]: Looks correct