# Visual System

## Source State

This file merges the public visual guidance from the accepted intake files. It is an execution control file, not a duplicate of all intake text.

Status:

- Public visual base accepted by user.
- P01 is the first public-style and cover sample.
- P02 is the first content-page sample after P01 acceptance.

Primary source files:

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

Backup fact-check source:

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

## Current Visual Definition

> 深蓝黑商务底 + AI 航线作战图 + 雷达 / 罗盘 / 船票 / 路线图母题 + 青色与金色信号高亮。

Working visual sentence:

> 这不是一份制度文件，而是一张上船前的 AI 作战航线图。

Accepted continuity rule:

> 每页底板风格完全统一；页面家族只更换轻微母题，不改变底板气质。

## Deck Tone

The tone should hold four feelings:

1. 兴奋感：AI 这条船不是口号，已经有船票了。
2. 信心感：参会者不是因为懂技术才被需要，而是因为懂人、懂局、懂客户。
3. 秩序感：兄弟一起开新局，但未来必须公司化、流程化。
4. 行动感：会后不空谈，马上进入第一周训练。

Language direction:

> 自己人口吻 + 公司化骨架 + 战斗前夜的兴奋感。

## Format Rules

- Output page: 16:9 full-page visual image.
- Page text may be embedded in the image.
- Minor typo / font / size issues are acceptable for this internal, time-constrained meeting use.
- Each page should still preserve one clear judgment.
- Best page structure: title + core judgment + one visual model / three short points / one relationship map.
- Do not copy long charter paragraphs into the page image.

## Palette

### Base

- Deep blue-black.
- Dark navy.
- Near-black business background.
- Cool slate gray for secondary structures.

### Signal Colors

- Cyan / blue-green for AI signal, radar, route, and active paths.
- Gold / warm amber for key decisions, ship ticket, commitment, and action emphasis.
- White / pale blue for readable page titles and labels.

### Avoid

- Government-report red / gold heaviness.
- Bright cyberpunk neon.
- Cute cartoon palette.
- Customer-proposal clean white corporate SaaS look.
- Training-course pastel look.

## Motif System

| Motif | Meaning | Use |
| --- | --- | --- |
| 船票 | AI 时代的新机会已经出现 | P01, P09, P10, P24 |
| 上船 / 登船坡道 | 有意愿的人先进入训练和协作 | P01, P10, P12 |
| 航线 | 培训 -> 顾问 -> 系统；从想用 AI 到用好 AI | P01, P13, P14, P23 |
| 雷达 | 客户判断、风险识别、机会发现 | P03, P09, P16, P19 |
| 罗盘 | 方法论、客户适配模型、现实校准 | P16, P20 |
| 航道闸门 | 宽入口、严系统、客户筛选 | P15, P22 |
| 双轨 / 双航道 | 探索价值与工程兑现 | P17 |
| 船舱 / 作战地图 | 团队协作结构 | P18, P19 |
| 阶梯 / 航行资格 | L0-L4 成长路径 | P21 |
| 训练卡 / 船员卡 | 第一周 AI 训练目标 | P23, P24 |

Detailed motif handling lives in:

```text
visual-system/motifs/motif-registry.md
```

## Page Families

### Family A: Opening / Consensus

Pages:

- P01-P03

Function:

- Establish the meeting as a shared opening, not a command or customer report.

Visual pattern:

- Big dark route background.
- Ship-ticket or route-map hero.
- Radar-centered identity map.

### Family B: Pressure / Role Transition

Pages:

- P04-P07

Function:

- Convert anxiety and strong personal dependency into a reason for team upgrade.

Visual pattern:

- Old route vs new AI route.
- Single engine to multi-engine fleet.
- Central pressure node to distributed system.

### Family C: Confidence / Agentic Entry

Pages:

- P08-P12

Function:

- Make old sales experience feel newly valuable in the AI era.

Visual pattern:

- Traditional funnel vs customer journey route.
- Radar reading people / situation / timing.
- Boarding ramp replacing high technical wall.
- Work-loop diagram for using AI before and after meetings.

### Family D: Business Path / Customer Judgment

Pages:

- P13-P17

Function:

- Explain what the team sells and how customers should be filtered.

Visual pattern:

- Route map from "想用 AI" to "用好 AI".
- Three-stage route / stair: training, consulting, system.
- Funnel / lock gate.
- Four-direction compass.
- Double track: exploration then engineering.

### Family E: Team Structure / Boundaries

Pages:

- P18-P22

Function:

- Clarify cooperation, roles, calibration mechanism, growth route, and first bottom lines.

Visual pattern:

- Crew compartments around customer journey.
- Five role icons around boarding path.
- Compass correction / route calibration.
- L0-L4 ladder.
- Three safety gates / seals.

### Family F: Training / Action

Pages:

- P23-P24

Function:

- Move from shared confidence to first-week AI training behavior.

Visual pattern:

- Four-week route map.
- First-week training card / ship-member card.

## Text Rendering Policy

Because the selected route is full-page visual-image-led:

- Let the image carry the main page title and key phrase when possible.
- Keep generated text short, bold, and central.
- Prefer labels of 2-8 Chinese characters over long sentences inside diagrams.
- Long lists should be simplified into fewer phrases before image generation.
- Do not spend production time on pixel-perfect typography unless the user requests repair.

Risk note:

- AI-generated Chinese text may be imperfect. This project accepts minor text defects, but page prompts should still reduce text complexity to avoid severe unreadability.

## Forbidden Drift

Avoid:

- Customer proposal deck style.
- Formal archive charter page.
- Dense training manual.
- Government report.
- Cute ship cartoon.
- Pirate / fantasy ship.
- Generic tech dashboard UI.
- Cyberpunk neon city.
- Random humanoid robots.
- Concrete portraits of attendees.
- Excessive decorative gradients that replace the route / radar / compass logic.

## Page Review Questions

For each generated page image, ask only lightweight fit questions unless the user asks for deeper review:

1. Does the page's first read match its core judgment?
2. Does it feel like an internal kickoff route map, not a customer proposal?
3. Is the AI航线 / 雷达 / 罗盘 / 船票 motif clear enough?
4. Does the page preserve confidence and action instead of becoming a rule lecture?
5. Is the text at least usable for an internal meeting?

## Materialization Log

| Date | Target | Result | Notes |
| --- | --- | --- | --- |
| 2026-06-29 | Extract merged visual system | initialized | Created from accepted intake; no images generated. |

## Sample Adjustment Rule

During P01 / P02 sampling:

- Public style issue: update this file and `visual-system/style/style-prompt-master.md`.
- Page-specific issue: update only the relevant `slides/sNN/sNN-vN-*` artifacts.
- Do not turn one page's local correction into a global rule unless it affects later pages.

## Next Action

Create P01 / `s01` as the cover and public-style sample.