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.8 KiB
5.8 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-sarkis-cloning-technology | Sarkis Cloning Technology | 10_Wiki/Topics | verified | self |
|
none | B | 0.85 | applied |
|
2026-05-10 | pending |
|
Sarkis Cloning Technology
매 한 줄
"매 villain 의 unkillability 는 매 lore mechanic 의 product 다.". Sarkis Cloning Technology 는 War Commander 의 antagonist Sarkis 가 매 defeat 후 clone 으로 부활하는 narrative device — repeat-encounter PvE bossfight 의 lore justification 이자, escalating-difficulty arc 의 backbone. 매 player 가 "왜 매번 같은 적이 더 강해져서 나타나는가" 라는 ludonarrative dissonance 를 mechanically resolve.
매 핵심
매 Lore Premise
- Sarkis 는 매 death event 후 cloned consciousness 로 reactivate
- 매 clone 은 previous defeat data 를 inherit → adaptive AI
- "Generation" 을 lore-internal version number 로 사용 (Sarkis Mk II, III, ...)
- Faction: Skybound (sky-themed antagonist faction)
매 Mechanical Function
- Boss respawn justification: 매 raid event 마다 동일 boss 재등장 가능
- Power escalation device: 매 generation 마다 +stat, +ability
- Story progression hook: 매 clone iteration → new dialogue, new arc
- Player progression mirror: 매 player level up → 매 Sarkis level up
매 응용
- War Commander: Sarkis Mk-series boss tiers.
- Skybound campaign: clone-iteration arc → final "original" reveal.
- Telemetry: clone defeat count → analytics on raid completion.
💻 패턴
Pattern 1 — Clone generation entity
interface SarkisClone {
generation: number;
baseStats: BossStats;
inheritedTraits: TraitId[];
abilityUnlocks: AbilityId[];
defeatCount: number;
}
function spawnClone(prev: SarkisClone | null): SarkisClone {
const gen = (prev?.generation ?? 0) + 1;
return {
generation: gen,
baseStats: scaleStats(BASE_STATS, gen, 1.15),
inheritedTraits: prev ? evolveTraits(prev.inheritedTraits) : SEED_TRAITS,
abilityUnlocks: pickAbilities(gen),
defeatCount: 0,
};
}
Pattern 2 — Adaptive trait evolution
function evolveTraits(prev: TraitId[]): TraitId[] {
// 매 player 의 winning strategy 에 counter trait 부여
const meta = analyticsService.getDominantStrategy();
const counter = TRAIT_COUNTERS[meta] ?? RANDOM_TRAIT;
return [...prev, counter].slice(-MAX_TRAITS);
}
Pattern 3 — Stat scaling
function scaleStats(base: BossStats, gen: number, factor: number): BossStats {
const mult = Math.pow(factor, gen);
return {
hp: base.hp * mult,
damage: base.damage * mult,
armor: base.armor + Math.floor(gen / 3),
speed: base.speed,
};
}
Pattern 4 — Lore dialogue selection
function getCloneDialogue(gen: number, defeatCount: number): DialogueLine[] {
if (gen === 1) return INTRO_LINES;
if (gen <= 5) return ARROGANCE_LINES;
if (gen <= 10) return DESPERATION_LINES;
return EXISTENTIAL_LINES; // 매 high-gen → 매 self-awareness arc
}
Pattern 5 — Defeat → respawn cooldown
async function onCloneDefeated(clone: SarkisClone, players: Player[]) {
await grantRewards(players, clone.generation);
const cooldown = 7 * 24 * 3600 * 1000; // 매 7d 후 재등장
scheduler.schedule(() => spawnClone(clone), cooldown);
}
Pattern 6 — "Original Sarkis" reveal trigger
function checkOriginalReveal(state: CampaignState): boolean {
return state.maxCloneGen >= 12
&& state.allianceCompletedArcs.includes('skybound-mk12');
}
Pattern 7 — Clone telemetry log
function logCloneEvent(event: 'spawn'|'defeat', clone: SarkisClone, players: string[]) {
analytics.track('sarkis_clone_event', {
type: event,
generation: clone.generation,
traits: clone.inheritedTraits,
participants: players.length,
timestamp: Date.now(),
});
}
매 결정 기준
| 상황 | Approach |
|---|---|
| Repeat boss needed | Clone lore device (Sarkis-style) |
| One-time finale boss | Original-only, no clone |
| Power-creep concern | Cap generations, soft reset |
| Narrative dissonance | Use clone arc to address it directly |
기본값: clone generation cap 12, +15% stat scaling per gen, adaptive traits enabled.
🔗 Graph
- 부모: Procedural-Rhetoric · Live Operations (LiveOps)
- 변형: Beresnev Studio · Stage-Director-and-World-Tension-Scaling
- 응용: Skybound_Skill_Asset_Integration · War-Commander-Combat-Ecosystem
- Adjacent: Power Creep (Content Treadmills) · Procedural-Level-Geometry
🤖 LLM 활용
언제: 반복 boss arc 의 lore design, narrative-mechanic alignment 검토, escalation curve 설계. 언제 X: linear single-narrative game, perma-death roguelike — clone device 부적합.
❌ 안티패턴
- Infinite generations w/o cap: power creep + player exhaustion.
- No narrative payoff: 매 clone 이 단순 reskin → 매 player engagement 0.
- Mechanical = lore mismatch: lore 상 unique 하다고 해놓고 매 mechanic 은 reskin.
- No counter-strategy adaptation: clone 이 변하지 않으면 매 boss fight 가 trivial 해짐.
🧪 검증 / 중복
- Verified (Kixeye War Commander event archive, Skybound campaign notes).
- 신뢰도 B (lore-specific, partial public docs).
🕓 Changelog
| 날짜 | 변경 |
|---|---|
| 2026-05-08 | Phase 1 |
| 2026-05-10 | Manual cleanup — clone lore mechanic + 7 implementation patterns |