video-workbench/projects/2026-06-29-搭上AI这条船/handoff/2026-06-29-ai-ship-formal-p...

6.1 KiB
Raw Blame History

2026-06-29 搭上 AI 这条船 Formal Production Handoff

Status

  • Project: 2026-06-29-搭上AI这条船
  • Handoff purpose: next clean session starts formal production.
  • Current lifecycle phase: formal production setup.
  • Current workflow line: production-light for remaining pages.
  • Running mode: prompt and generate.
  • Review mode: none by default.
  • Write policy: append-only; overwrite allowed: no.

User decision evidence:

  • user_decision: 2026-06-29 user confirmed slides/s01/s01-v1-image.png and slides/s02/s02-v1-image.png both passed.
  • user_decision: 2026-06-29 user requested this handoff and stated the next new session will start formal production.

Next-Session Load Order

Load these files in order:

  1. AGENTS.md
  2. projects/2026-06-29-搭上AI这条船/handoff/2026-06-29-ai-ship-formal-production-handoff.md
  3. projects/2026-06-29-搭上AI这条船/project.md
  4. projects/2026-06-29-搭上AI这条船/execution-plan.md
  5. projects/2026-06-29-搭上AI这条船/slides/slides.md
  6. projects/2026-06-29-搭上AI这条船/visual-system/visual-system.md
  7. projects/2026-06-29-搭上AI这条船/visual-system/style/style-prompt-master.md
  8. projects/2026-06-29-搭上AI这条船/visual-system/motifs/motif-registry.md
  9. projects/2026-06-29-搭上AI这条船/intake/阶段5P1-P24 单页设计骨架.md

Read narrower intake files only if needed:

  • intake/阶段5页面清单骨架.md
  • intake/阶段5全局页面规则.md
  • intake/阶段4通用表达与视觉系统.md
  • intake/阶段3搭上 AI 这条船PPT总纲.md

Backup fact-check source only:

C:\Users\wangq\Documents\Codex\knowledge-vault\work\internal\OPC销售\AI智能化客户经营团队启动会议章程.md

Do not re-compress the charter into the main PPT. Use it only to verify a factual claim when needed.

Production Basis

The user selected:

整页视觉图为主。

User-confirmed common visual base:

每页底板风格完全统一;统一深蓝黑 AI 航线作战图底盘,按页面家族只做轻微母题变化。

User-confirmed samples:

Unit Page Image Status
s01 P01 / 搭上 AI 这条船 slides/s01/s01-v1-image.png user-confirmed pass
s02 P02 / 今天这场会,不是再动员一次 slides/s02/s02-v1-image.png user-confirmed pass

When helpful, use these two images as visual calibration samples. If a future generation prompt needs actual image-reference behavior, load the local sample image into visible context before generation; a path written inside a prompt is traceability only.

Remaining Scope

Remaining pages:

s03-s24

Source authority:

intake/阶段5P1-P24 单页设计骨架.md

Do not reorder pages, rename page titles, or replace the core conclusion unless the user explicitly changes the deck.

Default next package:

s03-s08

Reason:

  • These are the next six pages in source order.
  • PPT pages are text/layout-heavy, so six pages is a conservative first formal package.
  • If the next session judges context and generation flow to be stable, later packages can broaden up to 8 pages.

Suggested package sequence:

  1. s03-s08
  2. s09-s16
  3. s17-s24

Adjust only if the user requests a different scope.

Production Rules For Next Session

Use the lightweight route unless the user changes it:

  • main/new session may directly produce the package;
  • no routine review file;
  • no child session required for this project unless the next session chooses to use project-default batching;
  • no full completeness gate;
  • no external vision review;
  • no Minimax MCP or other external review services;
  • no source-charter expansion;
  • no prompt review pause unless the user asks.

For each page in scope:

  1. Resolve next unused sNN-vN by scanning the page folder.
  2. Write sNN-vN-brief.md.
  3. Write sNN-vN-prompt.md.
  4. Generate sNN-vN-image.png.
  5. Update slides/slides.md.

Review mode stays:

none

Do not write sNN-vN-review.md unless the user explicitly asks for review, repair, or diagnosis.

Prompt / Generation Route

Use gpt-image-2 Skill Advisor / host-native flow.

Mode result in this session:

{
  "mode": "B-or-C",
  "recommendation": "host-or-advisor",
  "garden_mode_enabled": false,
  "has_api_key": false
}

Expected route:

brief -> prompt -> host image generation -> copy image into slides/sNN/ -> update slides.md

Do not use Garden/API paths unless the user explicitly changes policy.

Text Policy

The user accepts minor text, font-size, and typo defects because this is an internal time-constrained meeting deck.

Still follow these defaults:

  • one title;
  • one core judgment;
  • short labels;
  • reduce long lists before image generation;
  • preserve page title and core conclusion from P1-P24 skeleton.

If a page's generated Chinese text is imperfect but the image direction is good, treat that as a possible PPT-layer repair later, not an automatic image failure.

File State At Handoff

Created / active control files:

  • project.md
  • execution-plan.md
  • visual-system/visual-system.md
  • visual-system/style/style-prompt-master.md
  • visual-system/motifs/motif-registry.md
  • slides/slides.md
  • tasks/2026-06-29-visual-system-alignment/task-log.md

Created sample artifacts:

  • slides/s01/s01-v1-design.md
  • slides/s01/s01-v1-brief.md
  • slides/s01/s01-v1-prompt.md
  • slides/s01/s01-v1-image.png
  • slides/s02/s02-v1-design.md
  • slides/s02/s02-v1-brief.md
  • slides/s02/s02-v1-prompt.md
  • slides/s02/s02-v1-image.png

No review files were written for the sample run.

Stop / Escalation Conditions

Stop and ask the user if:

  • generated pages drift away from the accepted P01/P02 style;
  • text becomes too broken for internal meeting use;
  • a page requires a public-style change rather than a page-local repair;
  • generation output suggests the deck is becoming customer proposal / government report / SaaS dashboard / cyberpunk tech poster;
  • there is an artifact collision because a target sNN-vN-* path already exists.

Otherwise continue production under the approved lightweight rules.