Files
2nd/10_Wiki/Topics/Domain_General/From_Other/Role of Conflict in Narrative.md
T
Antigravity Agent c24165b8bc refactor(topics): 멀티 에이전트용 지식 재편 — _Common(공통 기본기) + Domain_* 구조
에이전트 8종(대화형/프로그래머 C·S/디자이너/설계자/기획자/QA/PD/PM)에게
[공통 기본 능력 + 롤별 Specialty] 2층으로 지식을 주입하기 위한 재분류.
문서 내용·포맷은 무수정, 폴더 이동만 (6,372개 문서 수 보존 확인).

- Topic_Programming → Domain_Programming (내부 구조 보존)
- Topic_Graphic → Domain_Design
- Topic_Business → Domain_Product
- Topic_General → Domain_General
- _Common 신설: Math(구 Topic_Math_Specialty), Reasoning(구 General/From_Thinking & Reasoning),
  Reasoning_Creativity(구 General/From_창의성), Communication(Poetic_Blog_Writing + From_writing)
- 타 도메인의 From_* 폴더는 유지 (출처 표기일 뿐, 이미 도메인에 맞게 분류된 문서)
- 빈 폴더 정리 (memory/procedures)
- 에이전트→폴더 매핑은 workspace의 .astra/agent-knowledge-map.json (9개 에이전트)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-11 11:05:56 +09:00

5.4 KiB

id, title, category, status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, verification_status, tags, raw_sources, last_reinforced, github_commit, tech_stack
id title category status canonical_id aliases duplicate_of source_trust_level confidence_score verification_status tags raw_sources last_reinforced github_commit tech_stack
wiki-2026-0508-role-of-conflict-in-narrative Role of Conflict in Narrative 10_Wiki/Topics verified self
Narrative Conflict
Story Conflict
Dramatic Conflict
none A 0.9 applied
storytelling
writing
narrative
drama
2026-05-10 pending
language framework
english-korean narrative-craft

Role of Conflict in Narrative

매 한 줄

"매 story 의 engine 의 conflict — desire vs obstacle". Aristotle 의 Poetics (335 BCE) 의 agon 의 origin, 매 modern beat-sheet (Save the Cat, Hero's Journey) 의 same axis 의 reuse. 매 conflict 의 absence 의 narrative 의 dead — character change 의 vehicle 의 obstacle 의 friction.

매 핵심

매 Conflict Types (Classical)

  1. Person vs Person — 매 antagonist clash (Iliad, Breaking Bad).
  2. Person vs Self — 매 internal moral struggle (Hamlet, Crime and Punishment).
  3. Person vs Society — 매 institutional pressure (1984, Handmaid's Tale).
  4. Person vs Nature — 매 survival (The Old Man and the Sea, The Martian).
  5. Person vs Technology — 매 modern AI/system conflict (Black Mirror, Ex Machina).
  6. Person vs Fate/Supernatural — 매 destiny challenge (Oedipus, Final Destination).

매 Functional Roles

  • Reveals character — 매 pressure 의 true self.
  • Drives plot — 매 cause-effect chain.
  • Creates stakes — 매 reader 의 emotional investment.
  • Forces choice — 매 character agency 의 demonstrate.

매 Structure (3-act + conflict escalation)

  1. Act 1 setup — 매 inciting incident 의 conflict 의 introduce.
  2. Act 2 confrontation — 매 rising stakes, midpoint reversal.
  3. Act 3 resolution — 매 climax (peak conflict) → denouement.

매 응용

  1. Novel/screenplay drafting — 매 each scene 의 micro-conflict 의 require.
  2. Game narrative — 매 quest design 의 obstacle 의 core.
  3. Marketing storytelling — 매 customer (hero) vs problem (villain) framing.
  4. Therapy / personal narrative — 매 reframing internal conflict.

💻 패턴

Beat sheet template (Markdown)

# Story: <Title>

## Protagonist
- Name, want (external goal), need (internal lack).

## Antagonist / Obstacle
- Force opposing the want.

## Beats
1. Opening Image — status quo.
2. Inciting Incident — conflict introduced (page 10).
3. Plot Point 1 — commit to journey (page 25).
4. Midpoint — false victory or false defeat.
5. Plot Point 2 — all-is-lost moment.
6. Climax — peak conflict resolution.
7. Closing Image — mirror of opening, transformed.

Conflict density check (Python)

import re
def conflict_score(scene_text: str) -> float:
    # crude heuristic: conflict verbs per 100 words
    verbs = re.findall(r"\b(argue|fight|refuse|attack|defy|resist|escape|flee|kill|hate)\b",
                       scene_text, re.I)
    words = len(scene_text.split())
    return len(verbs) / max(words, 1) * 100

print(conflict_score(open("scene_1.txt").read()))

Scene goal-conflict-disaster (template)

**Scene 12 — The Confrontation**
- Goal: Hero wants to retrieve the key.
- Conflict: Antagonist has set a trap.
- Disaster: Hero gets the key but loses ally.

Dialogue subtext (Luau-flavored example for game dev)

-- NPC reaction system
local function reactToPlayer(npc, action)
    if npc.relationship < 30 and action == "ask_favor" then
        npc:say("After what you did? Get out.")  -- conflict surfacing
    elseif npc.relationship > 70 and action == "ask_favor" then
        npc:say("Anything for you.")            -- conflict resolved
    end
end

LLM-assisted conflict generator (Python, Anthropic SDK)

import anthropic
client = anthropic.Anthropic()

resp = client.messages.create(
    model="claude-opus-4-7",
    max_tokens=400,
    messages=[{
        "role": "user",
        "content": "Given a protagonist who fears commitment and an antagonist who is their estranged sibling, generate 3 escalating conflict scenes."
    }]
)
print(resp.content[0].text)

매 결정 기준

상황 Conflict type
Character study Person vs Self
Thriller Person vs Person
Dystopia Person vs Society
Survival Person vs Nature
Tech ethics Person vs Technology
Tragedy Person vs Fate

기본값: 매 layered — 매 external (P vs P) + internal (P vs Self) 의 same character 의 simultaneous.

🔗 Graph

🤖 LLM 활용

언제: scene 의 brainstorm, conflict beat 의 escalate, antagonist motivation 의 deepen. 언제 X: real human conflict 의 mediation — 매 fictional craft 의 tool, not therapy.

안티패턴

  • Manufactured conflict: 매 character 의 act stupidly 의 plot 의 force — reader 의 feel manipulated.
  • No internal conflict: 매 external action 의 only — 매 character 의 flat.
  • Resolved 의 too early: 매 act 2 의 conflict 의 deflate — sustain 의 climax 의 reach.
  • Antagonist 의 motiveless: 매 generic villain — 매 antagonist 의 own internal logic 의 require.

🧪 검증 / 중복

  • Verified (Aristotle Poetics, McKee Story 1997, Snyder Save the Cat 2005).
  • 신뢰도 A.

🕓 Changelog

날짜 변경
2026-05-08 Phase 1
2026-05-10 Manual cleanup — 6 conflict types + beat sheet + scene template