# Lecture Architecture

Use this to convert rough ideas into a seminar-ready HTML document.

## Core Principle

The page should make the lecturer's argument easier to teach and the audience's next action easier to take.

Do not merely summarize the user's notes. Rebuild them into a teachable flow.

## Default Section Blueprint

### Hero

Purpose:

- state the promise/thesis clearly
- identify audience and desired outcome
- make the first viewport feel like a finished seminar document

Include:

- badge/pill with seminar name
- strong H1
- 1-2 sentence lead
- metadata chips
- optional `要点まとめ` card
- large hero image soon after

### Section 01: Why This Matters

Show the pain, misconception, or strategic contrast.

Good patterns:

- "hard route vs easier route"
- "what most people do vs what works locally"
- "online competition vs offline whitespace"
- "abstract learning vs visible demo"

Use a 2-column or 3-card comparison plus table.

### Section 02: Positioning / Permission

Give the audience permission to act.

For teaching/business seminars, this often means:

- you do not need to be world-class
- you only need to be one step ahead of the beginner
- trust and proximity matter
- the local context changes the game

Use a ladder, map, or level illustration.

### Section 03: Concrete Target

Answer "who is this for?"

Good patterns:

- existing relationships
- customer avatars
- proximity map
- stakeholder table
- first 20-person list

Make the target feel reachable.

### Section 04: Demonstration Menu

Answer "what exactly do I show?"

This section usually needs:

- tabbed demo cards
- one large overview visual
- individual visuals for each tab
- table mapping menu -> what to show -> who it helps

If using tabs, put controls close to the content they control.

### Section 05: Delivery Structure

Answer "how would I run the session?"

Good patterns:

- 30/60/90-minute agenda
- timeline
- checklist
- first meeting script
- pricing ladder or next-step ladder

### Section 06: Work / Action

Give the audience something to fill out or copy.

Good patterns:

- worksheet inputs
- generated outreach text
- prompt box with copy button
- checklist
- first-contact DM template

This makes the HTML more useful than a slide deck.

### Section 07: Fact-Check / Safe Wording

Use this when the topic includes:

- money-making claims
- AI product capabilities
- tool names/models
- legal/medical/financial risk
- platform limits or pricing

Format:

| Risky phrasing | Safer phrasing | Why |

### Homework

End with concrete action:

- today
- this week
- before next session

Avoid ending only with inspiration.

### Conclusion

Use a dark conclusion box with 3 decisive points.

The conclusion should be short enough that a presenter can read it aloud.

### Sources Footer

Include official sources when facts may change.

Use:

- product docs
- official help pages
- official pricing pages
- source articles supplied by the user

## Transforming Rough Notes

When the user gives a long spoken explanation:

1. extract claims
2. group into 7-9 sections
3. remove repetition
4. convert examples into tables/cards
5. convert abstract ideas into diagrams
6. add an action worksheet
7. add safe wording and sources

## Voice And Copy

Use Japanese-first, plain and concrete language.

Good:

- "まずは1人に教える"
- "目の前で見せる"
- "相手の仕事に置き換える"
- "今日中にやること"

Avoid:

- excessive buzzwords
- English labels where Japanese is clearer
- academic explanations without action
- thin motivational copy

## Claims About Money

When discussing monetization:

- frame examples as possibilities, not guarantees
- show prerequisites and context
- include a note that results vary
- focus on concrete first action

Safer examples:

- "数万円の講座や相談は十分狙える"
- "相手、内容、信頼関係次第"
- "まずは無料/ご飯/少額で0→1を作る"

Unsafe examples:

- "誰でも月10万円"
- "必ず5万円取れる"
- "これだけで稼げる"
