Files

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

4.2 KiB

Raw Blame History

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

title

BLUF (Bottom Line Up Front)

매 한 줄

"매 conclusion 을 첫 줄에 — recipient 가 더 못 읽어도 OK 하도록.". US military origin 의 writing convention; 매 incident report, exec memo, PR description, on-call alert 의 표준 — 매 reader 의 cognitive load 를 minimize 하고 fastest decision-making 을 enable.

매 핵심

매 Structure

Line 1: the conclusion / decision needed / status verdict.
Line 2-N: supporting evidence in priority order.
Tail: details, appendices, traces.

매 vs Narrative

Narrative: "We started X, encountered Y, debugged Z, found root cause W, fixed it." — reader waits for punchline.
BLUF: "Outage resolved. Root cause: misconfigured DNS. Restored 14:23 UTC." — punchline first.

매 응용

Incident postmortem TL;DR.
PR description first sentence.
Slack on-call escalation.
Email subject + first line.
Architecture decision record (ADR) summary.

💻 패턴

Incident Slack Alert

**[P1] Checkout API 5xx — DEGRADED**
Impact: 12% of orders failing since 14:05 UTC.
Action: rollback v2.4.1 in progress, ETA 5 min.
Owner: @oncall-payments
Thread: ↓

Postmortem Top

# Postmortem: 2026-05-08 Checkout Outage

**TL;DR**: 47-min P1 outage due to DNS TTL misconfig in v2.4.1 deploy.
- Customer impact: ~3,200 failed orders (~$84k revenue)
- Resolution: rollback at 14:23 UTC
- Action items: 4 (see §6)

## Timeline
...

PR Description

**Adds rate limiting to /api/checkout to prevent abuse.**

- New: `RateLimiter` middleware with Redis token bucket
- Default: 60 req/min per IP, configurable via env
- Tests: integration coverage for 429 path
- Risk: low — feature-flagged behind `RATE_LIMIT_ENABLED`

## Why
Spike on 05-06 saturated DB connections...

Email Template

Subject: [DECISION NEEDED by Fri] Migrate auth to OIDC — recommend Keycloak

Recommendation: adopt Keycloak for SSO; deprecate legacy LDAP by Q3.
Cost: $0 (OSS) + 2 SRE-weeks integration.
Risk: medium (auth migration); mitigated by phased rollout.

Background: ...

ADR Header

# ADR-0042: Use SQLite for local dev DB

**Decision**: SQLite for local; Postgres for staging/prod.
**Status**: accepted (2026-05-10)
**Context**: ... (3 paragraphs below)

On-Call Status Page

🟢 **All systems operational** — last incident 9 days ago.
Recent: deploys 4 (all green) · alerts 0 · SLO budget 99.4%

매 결정 기준

상황	BLUF 적용
Incident alert	YES — line 1 = severity + impact
Postmortem	YES — TL;DR block before timeline
Tutorial / explainer	NO — narrative 적합
Marketing copy	NO — hook 후 reveal
ADR	YES — decision first
Bug report	YES — observed vs expected first

기본값: ops/exec communication 은 BLUF; pedagogical/narrative 은 example-first.

🔗 Graph

부모: Technical Writing
응용: Postmortem · ADR
Adjacent: Pyramid Principle

🤖 LLM 활용

언제: ask LLM to "rewrite as BLUF" — high-quality reflow. 언제 X: storytelling / customer-facing narrative.

❌ 안티패턴

Buried lede: conclusion 을 §3 에 묻기.
Over-summarize: line 1 이 vague ("there was an issue").
No context for novices: BLUF 는 expert reader 가정 — onboarding doc 에는 부적합.
Decision-less BLUF: "We did X" 보다 "Recommend Y" 가 actionable.

🧪 검증 / 중복

Verified (US Army Field Manual, Google SRE Book postmortem chapter).
신뢰도 A.

🕓 Changelog

날짜	변경
2026-05-08	Phase 1
2026-05-10	Manual cleanup — full content with templates for incidents/PRs/ADRs

4.2 KiB Raw Blame History