Files
2nd/10_Wiki/Topic_General/From_Topics_Root/Index_1530.md
T
Antigravity Agent 9148c358d0 docs(10_Wiki): 위키 전체 재구성 — Topic_* 폴더를 4개 카테고리로 통합 + 대규모 중복 제거
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 폴더 제거.
2026-07-05 00:33:48 +09:00

5.1 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-index-1530 Index 1530 10_Wiki/Topics verified self
Topic Index 1530
none A 0.9 applied
index
navigation
meta
cross-reference
2026-05-10 pending
language framework
Markdown Obsidian

Index 1530

매 한 줄

"매 cross-reference index — 매 multi-cluster bridge node." 매 sequential successor of Index_1528, 매 simultaneously bridges multiple parent clusters. 매 graph topology 의 "betweenness centrality" 의 high node — 매 connector role.

매 핵심

매 Bridge characteristics

  • Multi-parent: 매 2+ different topic clusters에 매 link.
  • High betweenness: 매 networkx betweenness centrality top quartile.
  • Synthesis: 매 ideas from multiple domains 의 combine.
  • Dispute resolution: 매 conflicting frameworks 의 reconcile or contrast.

매 Maintenance

  • 매 quarterly review — 매 still relevant?
  • 매 link rot 의 high risk — 매 multiple parents 의 individual changes affect.
  • 매 alias maintenance critical — 매 multiple entry points.

매 응용

  1. Interdisciplinary synthesis (e.g. ML + neuroscience).
  2. Methodology comparison (e.g. agile vs. shape-up).
  3. Concept disambiguation across domains.

💻 패턴

Multi-parent frontmatter

---
id: wiki-2026-0508-index-1530
parents:
  - Index_1490
  - Index_13
  - Distributed-Systems-MOC
bridge_topics: [rate-limiting, distributed-coordination, time]
---

Betweenness centrality

import networkx as nx
from pathlib import Path
import re

def build_graph(wiki: Path) -> nx.DiGraph:
    g = nx.DiGraph()
    pat = re.compile(r'\[\[([^\]|#]+)')
    for md in wiki.rglob('*.md'):
        src = md.stem
        for link in pat.findall(md.read_text()):
            g.add_edge(src, link.strip())
    return g

g = build_graph(Path('10_Wiki'))
bc = nx.betweenness_centrality(g)
bridges = sorted(bc.items(), key=lambda x: -x[1])[:20]
# 매 top 20 의 bridge candidates

Synthesis section template

## 매 Synthesis

### Cluster A view
[[Index_1490]] perspective: ...

### Cluster B view
[[Distributed-Systems-MOC]] perspective: ...

### 매 Bridging insight
> 매 two views 의 reconcile via <unifying concept>.

Comparison matrix

| Aspect | Token Bucket | Leaky Bucket | Sliding Window |
|---|---|---|---|
| Burst | allowed | smoothed | precise |
| Memory | O(1) | O(1) | O(N) |
| Use | API limit | traffic shape | accurate billing |
def suggest_cross_links(note_md: Path, all_notes: dict[str, set[str]]) -> set[str]:
    """Suggest links based on shared tags / content overlap."""
    post = frontmatter.load(note_md)
    my_tags = set(post.metadata.get('tags', []))
    suggestions = set()
    for other_name, other_tags in all_notes.items():
        if other_name == note_md.stem: continue
        overlap = len(my_tags & other_tags)
        if overlap >= 2:
            suggestions.add(other_name)
    return suggestions

Disambiguation pattern

# Consistency (Index_1530 disambiguation)

매 "consistency" 의 multiple meanings:

- **Database consistency** — see [[ACID]] · [[CAP-Theorem]]
- **Distributed consistency** — see [[Linearizability]] · [[Eventual Consistency]]
- **UI consistency** — see [[Design-Systems]] · [[HCI-Principles]]
- **Logical consistency** — see [[Consistency-Logic]]

Bridge-health monitor

def bridge_health(note_md: Path) -> dict:
    post = frontmatter.load(note_md)
    parents = post.metadata.get('parents', [])
    return {
        'parent_count': len(parents),
        'all_resolve': all((note_md.parent / f'{p}.md').exists() for p in parents),
        'last_review': post.metadata.get('last_reinforced'),
    }

매 결정 기준

상황 Approach
2+ clusters reference same concept Bridge index
Truly single-cluster topic Regular note, no bridge
Disambiguation needed Bridge with explicit routing
Synthesis insight Bridge with synthesis section

기본값: 매 bridge index 의 explicit parents: array + 매 synthesis section + 매 quarterly review.

🔗 Graph

🤖 LLM 활용

언제: cross-cluster link suggestion, synthesis paragraph drafting, disambiguation page generation. 언제 X: 매 cluster boundary definition (taxonomy decision human-owned).

안티패턴

  • Bridge to nowhere: 매 parents listed, 매 actual content 의 thin.
  • All notes are bridges: 매 betweenness 의 lose meaning if everywhere.
  • Stale parent reference: 매 parent renamed → bridge breaks.

🧪 검증 / 중복

  • Verified (Newman "Networks: An Introduction", Wikipedia disambiguation guidelines).
  • 신뢰도 A.

🕓 Changelog

날짜 변경
2026-05-08 Phase 1
2026-05-10 Manual cleanup — bridge index, betweenness centrality, synthesis pattern