9148c358d0
Topic_Agent/Topic_Blog/Topics/Topics_Biz/Topics_Meeting/Topics_Rag의 마크다운 지식 문서를 Topic_General/Topic_Programming/Topic_Graphic/Topic_Business 4개 카테고리로 재분류. - 중복 제거: frontmatter의 status:duplicate/merged + duplicate_of/redirect_to 필드로 자기 자신을 중복으로 선언한 리다이렉트 stub 1032개 제거, 완전 동일 내용 파일 472개 제거, 동일 파일명·다른 내용 충돌 시 더 큰(완전한) 버전만 유지(162개 제거) — 총 1639개 중복 제거. - 분류: 폴더 단위로 명확한 항목(AI_and_ML/Coding/Architecture 등 → Programming, Comfyui/Visual_Effects → Graphic, Topics_Biz/Topics_Meeting/사업 등 → Business, Poetic_Blog_Writing/창의성/Game_Design 등 → General)은 폴더 우선순위로, 나머지 혼재 폴더(Topic_Agent/Topic_Blog/Topics 루트/Thinking & Reasoning/Other/UI_UX_Assets)는 title/tags 키워드 스코어링으로 파일 단위 분류(불명확한 경우 General로 폴백). 원본 폴더명은 "From_*" 서브폴더로 보존해 추적 가능성 유지. - 최종 배치: Programming 2784 / General 1608 / Graphic 285 / Business 249 = 4926개 문서. - 에이전트 운영 상태(.astra/.agent/.obsidian/sessions/memory/_company/docs/lessons/_shared/src)는 지식 콘텐츠가 아니므로 재분류 대상에서 제외하고 원위치 유지. - Topics/Topic_email(상위 보호 폴더 Topic_email과 파일명 100% 중복) 삭제 — 보호 폴더 자체는 미변경. - 완전히 비게 된 Topic_Agent/Topic_Blog/Topics_Biz/Topics_Rag 폴더 제거.
5.4 KiB
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 |
|
none | A | 0.9 | applied |
|
2026-05-10 | pending |
|
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)
- Person vs Person — 매 antagonist clash (Iliad, Breaking Bad).
- Person vs Self — 매 internal moral struggle (Hamlet, Crime and Punishment).
- Person vs Society — 매 institutional pressure (1984, Handmaid's Tale).
- Person vs Nature — 매 survival (The Old Man and the Sea, The Martian).
- Person vs Technology — 매 modern AI/system conflict (Black Mirror, Ex Machina).
- 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)
- Act 1 setup — 매 inciting incident 의 conflict 의 introduce.
- Act 2 confrontation — 매 rising stakes, midpoint reversal.
- Act 3 resolution — 매 climax (peak conflict) → denouement.
매 응용
- Novel/screenplay drafting — 매 each scene 의 micro-conflict 의 require.
- Game narrative — 매 quest design 의 obstacle 의 core.
- Marketing storytelling — 매 customer (hero) vs problem (villain) framing.
- 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 |