"매 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.
**[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.