ingest: Book Co-Author source + 7 new concepts
This commit is contained in:
31
wiki/concepts/NarrativeArchitecture.md
Normal file
31
wiki/concepts/NarrativeArchitecture.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: "Narrative Architecture"
|
||||
type: concept
|
||||
tags: ["writing", "structure", "coherence", "storytelling"]
|
||||
sources: ["marketing-book-co-author"]
|
||||
last_updated: 2026-04-30
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
叙事架构(Narrative Architecture)是指在长篇思想领导力书籍中,维护贯穿全书各章节的"红色主线"(Red Thread),使书籍呈现为连贯论证而非独立散文的堆砌。叙事架构师负责确保每一章都服务于全书的核心论点,各章节之间形成有机递进或呼应关系。
|
||||
|
||||
## Core Principles
|
||||
|
||||
1. **单一主线贯穿**:全书必须围绕一个核心命题展开,所有章节直接或间接服务于该命题
|
||||
2. **章节逻辑递进**:章节之间存在清晰的思想推进路径,而非随机排列
|
||||
3. **开头呼应结尾**:全书开篇提出的问题或张力,应在结尾得到回应
|
||||
4. **避免重复冗余**:每个章节有独特战略功能,不与相邻章节内容重叠
|
||||
5. **叙事锚点设计**:在关键章节设置叙事锚点,强化读者记忆和认同
|
||||
|
||||
## The Red Thread Concept
|
||||
|
||||
"红色主线"(Red Thread)是叙事架构的核心隐喻:
|
||||
- **视觉隐喻**:如同红线贯穿珍珠项链,各章节是珍珠,主线是串联的逻辑
|
||||
- **功能要求**:读者在读完任何章节后,都能自然期待下一章的内容
|
||||
- **检验标准**:如果删除某一章,全书的论证链条是否断裂
|
||||
|
||||
## Related Concepts
|
||||
- [[Thought Leadership Book]] — 思想领导力书籍是叙事架构的主要应用场景
|
||||
- [[Voice Protection]] — 叙事架构不能破坏作者个人声音
|
||||
- [[First-Person Business Writing]] — 叙事架构服务于第一人称叙事
|
||||
Reference in New Issue
Block a user