10 KiB

Raw Permalink Blame History

On The Road Workflow Continuation Handoff

Status

Date: 2026-06-24.
Project: projects/2026-06-23-在路上.
Current branch: master.
Purpose: continuation handoff after style / character cleanup and the S14 reference-capable generation investigation.
This document supersedes the open questions in handoff/2026-06-24-on-the-road-style-reference-handoff.md where those questions have since been answered.

Current context package:

handoff/2026-06-24-on-the-road-workflow-continuation-context/review-context.md
handoff/2026-06-24-on-the-road-workflow-continuation-context/review-file-manifest.json

Compression Self-Check

Because the working session was compressed, do not rely on chat continuity for exact state.

What is safely recoverable from files:

current workspace rules in AGENTS.md and VIDEO_WORKBENCH.md;
project control state in project.md, execution-plan.md, visual-system/visual-system.md, slides/slides.md, and slides/broad-generation-self-audit-v1.md;
active character references in visual-system/characters/character-reference-registry.md;
active style rules in visual-system/style/style-prompt-master.md;
the S14 reference-capable generation investigation and generated test images under investigations/2026-06-24-s14-reference-capable-generation/;
the user decision recorded in investigations/2026-06-24-s14-reference-capable-generation/reviews/summary-and-rule-implications.md.

What is not reliable after compression unless it was written to disk:

exact intermediate chat wording around image judging;
transient host image-generation internal IDs or default output locations;
any unrecorded tool output from the compressed portion of the session;
subjective visual impressions not captured in the review files or the user decision.

Practical consequence:

Treat the files listed in this handoff and its context package as the continuation basis.
Do not reconstruct workflow decisions from memory if a local file gives the current rule.

Must Read First

Read these in order in a new session:

AGENTS.md
- UTF-8 rules.
- gpt-image-2 Skill rule.
- current default host image_gen reference-by-visible-context path.
VIDEO_WORKBENCH.md
- project layout, slides/sNN/sNN-vN-type.ext naming, asset policy, and reference-capable image generation rule.
projects/2026-06-23-在路上/project.md
- project-local status and high-level state.
projects/2026-06-23-在路上/execution-plan.md
- still contains some pre-S14-investigation wording; read it as current project control plus stale open decisions that need cleanup.
projects/2026-06-23-在路上/visual-system/visual-system.md
- accepted visual system, A/B/C/D definitions, and style / character system.
projects/2026-06-23-在路上/visual-system/characters/character-reference-registry.md
- active character references and selection rules.
projects/2026-06-23-在路上/visual-system/style/style-prompt-master.md
- active style modules, active style references, per-shot prompt requirements, and broad-generation repair rule.
projects/2026-06-23-在路上/intake/阶段五-人物一致性单镜.md
- five-shot character-consistency test skeleton for s05, s21, s14, s25, s33.
investigations/2026-06-24-s14-reference-capable-generation/reviews/summary-and-rule-implications.md
- current reference-capable generation conclusion and user decision.
projects/2026-06-23-在路上/slides/broad-generation-self-audit-v1.md

why broad generation is paused and what must be repaired.

Current User Decisions

Reference-Capable Generation

Use this path now and in future Video Workbench image generation:

Generate prompt/spec through gpt-image-2 Skill Advisor workflow.
Load the real reference image into the conversation context before generation.
Generate with host image_gen, naming the loaded image role in the prompt, such as Image 1: identity reference.

Do not use API/Garden for normal Video Workbench image generation unless the user explicitly changes the policy.

Do not reopen "can references work" for ordinary work. Reopen only if the host image tool is unavailable, the image cannot be loaded into context, or the user changes the policy.

Character Reference Selection

Current default:

Shot need	Reference choice
Near / face / half-profile / expression / identity-heavy	matching crop first
Distant / landscape-led / aerial / low identity burden	full character anchor board or project-approved distant reference first
Medium action / back / walking / prop continuity	matching crop, transparent slice, or anchor board by visible direction
Future high-identity close-up-heavy project	consider generating higher-resolution crops through image-to-image from the accepted anchor board before production

For 在路上, most shots are landscape-led, distant, or aerial. The current crop set was cut from the accepted character anchor board and made transparent; this is enough by default for consistency rather than high-fidelity portrait likeness.

Style Reference Selection

The common style phase has been cleaned and centralized into:

projects/2026-06-23-在路上/visual-system/style/style-prompt-master.md

Active style directory now contains:

style-anchor-board-v1.png
style-anchor-c-repair-v1.png
style-prompt-master.md

Process files are under:

projects/2026-06-23-在路上/archive/style/

Do not continue creating common style briefs, board specs, trial plans, HTML board sources, or contactsheets by default. Move to per-shot execution.

Completed Since Previous Handoff

Character directory cleaned.
- Active character references remain in visual-system/characters/.
- Historical/process files are under archive/characters/.
- character-reference-registry.md is the active reference registry.
Style directory cleaned.
- style-prompt-master.md exists and is active.
- Active style assets are only the common style board and repaired C sample.
- Historical/process files are under archive/style/.
Added character-consistency single-shot skeleton:
- projects/2026-06-23-在路上/intake/阶段五-人物一致性单镜.md.
Completed S14 reference-capable investigation:
- investigations/2026-06-24-s14-reference-capable-generation/.
- Generated outputs:
  - outputs/s14-anchor-board-reference-v1.png
  - outputs/s14-side-crop-reference-v1.png
- User decision recorded in reviews/summary-and-rule-implications.md.
Promoted the reference-capable generation rule into:
- AGENTS.md
- VIDEO_WORKBENCH.md

Important Stale Wording To Handle

Some older project files still predate the S14 investigation.

Examples:

execution-plan.md still says the next decision is how to repair broad-generation reference handling.
visual-system/visual-system.md still says the next action is deciding lightweight broad-production flow.
character-identity-lock.md still says later scene prompts have not proven identity preservation.

Interpretation:

These are not blockers for reference-capable feasibility anymore.
They are cues for the next workflow-cleanup pass: update project control files so they point to the new reference-capable rule and the remaining per-shot workflow work.

Current Working Tree Caveat

At the time this handoff was written, there are uncommitted changes from the reference-capable investigation/rule promotion work:

AGENTS.md
VIDEO_WORKBENCH.md
investigations/README.md
investigations/2026-06-24-s14-reference-capable-generation/
handoff/2026-06-24-on-the-road-workflow-continuation-handoff.md
handoff/2026-06-24-on-the-road-workflow-continuation-context/

Do not assume these are committed until git status --short is checked.

Next Recommended Work

The next session should optimize workflow, not restart image-reference research.

Recommended order:

Align stale control docs.
- Update project.md, execution-plan.md, and possibly visual-system/visual-system.md so they reflect:
  - S14 reference-capable path is decided;
  - common style phase is closed;
  - remaining problem is per-shot production workflow and traceability.
Define the repaired per-shot production unit.
- Minimum likely files:
  - slides/sNN/sNN-vN-brief.md
  - slides/sNN/sNN-vN-prompt.md
  - slides/sNN/sNN-vN-image.png
  - slides/sNN/sNN-vN-review.md only when review is actually needed.
- Each prompt must include:
  - style module;
  - active style reference path(s);
  - character reference path(s) or none with reason;
  - reference roles;
  - generation path note;
  - output path.
Decide how to mark old broad-run images.
- s05, s14, s21, s25, and s33 already have broad-run images, but those came from the flawed text-only broad run.
- Do not treat them as accepted finals.
- Decide whether to keep them as rejected candidates, replace them, or use them only as comparison examples.
Use the five-shot character-consistency skeleton as a workflow stress test if generation resumes.
- Recommended order from the intake file:
  - S-05 -> S-21 -> S-14 -> S-25 -> S-33.
- Purpose now:
  - validate per-shot traceability and reference selection under the decided path;
  - not prove again that image references can work.
Only after the repaired workflow is tested, resume wider shot production.

Do Not Do Next

Do not continue broad generation from s35.
Do not treat broad-run generated images as accepted finals.
Do not redo API/Garden research for normal work.
Do not ask whether reference images can work unless the host image tool or reference loading fails.
Do not use archived character/style files as default references.
Do not generate identity-critical shots from text-only character descriptions.
Do not ask GPT V2 for final prompts; Codex owns final prompt construction through the gpt-image-2 Skill workflow.
Do not turn the project into a heavy governance/audit workspace; keep workflow records lightweight and execution-facing.

Verification Artifacts

New context package:

handoff/2026-06-24-on-the-road-workflow-continuation-context/review-context.md
handoff/2026-06-24-on-the-road-workflow-continuation-context/review-file-manifest.json

Lifecycle scan for this handoff:

handoff/2026-06-24-on-the-road-workflow-continuation-context/lifecycle-guard-output/lifecycle-status-guard-scan.md

10 KiB Raw Permalink Blame History