c24165b8bc
에이전트 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>
4.2 KiB
4.2 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-bluf-bottom-line-up-front | BLUF (Bottom Line Up Front) | 10_Wiki/Topics | verified | self |
|
none | A | 1.0 | applied |
|
2026-05-10 | pending |
|
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 |