# Execution Plan

## Current Medium Branch

- Branch: internal PPT full-page visual image production.
- Format: 16:9 horizontal.
- Page count: 24 main pages, with possible backup pages later only if requested.
- Production mode: full-page images first; final PPT assembly after page images are ready.
- Prompt ownership: Codex owns final image prompts; GPT intake is source specification, not final prompt.
- Image prompt workflow: `gpt-image-2` Advisor / host-native path only unless the user explicitly changes policy.

## Current Execution Focus

Active focus:

1. P01 / `s01` cover and public-style sample passed user confirmation.
2. P02 / `s02` first content-page sample passed user confirmation.
3. Remaining page image production `s03-s24` completed through production-light child sessions.
4. Next focus is optional PPT assembly, user visual sampling, or append-only page repair.

## Operating Defaults

| Item | Default |
| --- | --- |
| Line | production-light for remaining pages. |
| Worker profile | pending PPT-page-production design; do not blindly reuse MV shot profile. |
| Running mode now | prompt and generate, full-page image-led. |
| Later likely running mode | same. |
| Review mode later | none, unless user asks for sample review / repair. |
| Write policy | append-only; overwrite allowed: no. |
| Source authority | P1-P24 single-page design skeleton. |

## Visual-System Alignment Scope

The visual-system stage must settle:

1. Global palette and atmosphere.
2. Page family taxonomy.
3. Motif rules: ship ticket, route, radar, compass, deck, port, double track, funnel / gate, ladder, training card.
4. Text-in-image tolerance and simplification rules.
5. Which pages should act as visual anchors for the whole deck.

## Sample-Gate Plan

The user approved this process:

| Page | Why |
| --- | --- |
| P01 | Cover and public-style sample: tests the unified dark AI route-map base, ship ticket, route glow, title treatment, and meeting atmosphere. |
| P02 | First content-page sample: tests whether the same base can carry ordinary page structure and meeting-positioning content. |

Decision rule:

- If P01 exposes a common base-style issue, revise `visual-system/`.
- If P01 exposes a cover-only issue, revise P01 only.
- If P02 exposes a content-page readability / structure issue that affects later pages, revise `visual-system/` and the style master.
- If P02 exposes only a page-specific issue, revise P02 only.
- After P01 and P02 pass, enter production for the remaining pages.

## Current Round

- R0: project files initialized.
- R1: visual-system base accepted.
- R2: P01 cover / public-style sample generated and user-confirmed pass.
- R3: P02 content-page sample generated and user-confirmed pass.
- R4: remaining pages formal production completed for `s03-s24`.

## Open Decisions

| Decision | Current Default |
| --- | --- |
| Final deck style | Full-page visual-image-led PPT. |
| Base visual style | Unified deep blue-black AI route operation-map base across all pages; page families vary motifs lightly only. |
| Text treatment | Text may be embedded in images; minor text defects acceptable. |
| People / portraits | Avoid concrete people unless later explicitly needed. Use abstract business-route metaphors. |
| Source charter | Fact-check backup only; not a main compression source. |
| Public visual duplicates | Merge stage 3 / 4 / 5 visual guidance; treat repeats as reinforcement, not conflict. |

## Next Decision

If requested, assemble the completed full-page images into a PPT or run targeted append-only repair for any page the user marks unusable.