# Research Method

Use this when updating the editorial skill from public Korean engineering writing.

1. Sample several companies and several technical domains; do not build rules from one writer.
2. Prefer implementation/incident/performance/operations articles over recruiting or marketing posts.
3. Record structural observations: how the problem is introduced, where constraints appear, how measurements are tied to claims, how alternatives and limitations are handled, and when tables/diagrams replace prose.
4. Do not copy distinctive phrases, jokes, metaphors, or signature expressions.
5. Promote a pattern into `editorial-rules.md` only when it appears useful across multiple sources and is compatible with evidence-preserving Tech Log writing.
6. Keep source notes under `./research/korean-tech-writing/`; runtime editing must work even if the websites are unavailable later.