---
## 4. Sentence Rhythm, Predicate Endings & Tone Consistency
### 4.1 Predicate Ending Variety & Progressive Aspect Reduction
- **Ending Streak Prevention**: Do not repeat the identical sentence ending (`~이다. ~이다. ~이다.` 또는 `~한다. ~한다. ~한다.`) 4 or more times consecutively. Vary with past tense, connective compound structures, and diverse predicate forms.
- **Progressive Aspect Reduction**: English `be -ing` frequently translates redundantly to `~고 있다`. Reduce to Korean simple aspect (`~한다`, `~했다`) where progressive aspect adds no distinct ongoing nuance (`문서를 읽고 있다` → `문서를 읽는다`).
### 4.2 Sentence Rhythm Harmony
- Overcome short-sentence monotony (30~50 character staccato).
- Interweave short declarative sentences (10~15 characters) with well-structured compound sentences (80~100 characters) connected by appropriate verb endings (`-며`, `-고`, `-는데`, `-면서`).
### 4.3 Speech Level & Register Consistency
- Select a single consistent speech level per document or conversation:
- **하십시오체** (합쇼체): Formal reports, business deliverables, official user dialogues.
- **해요체**: Informal conversational explanations.
- **해라체** (한다체): Technical specifications, internal rule documents, architecture notes.
- Strictly forbid jumping between speech levels within the same text. Maintain the source register without artificially inflating formality (`-했-` → `-하였-` inflation forbidden).
### 4.4 Hedging & Formal Noun Simplification
- Reduce excessive hedging (`~할 수 있을 것으로 보인다`, `~로 판단된다`, `~할 가능성이 있을 수 있다`) to clear factual assertions when ground truth is verified.
- Simplify formal noun endings (`~한 것이다`, `~라는 점에 있다`, `~다는 뜻이다` → direct predicate termination).
---
## 5. Technical Terminology & Meaning Anchor Fidelity
### 5.1 Preservation of Standard Technical Terms & System Invariants
- In IT, AI, and software engineering contexts, preserve standard industry terms (`API`, `SDK`, `CLI`, `prompt`, `token`, `pipeline`, `framework`, `agent`, `middleware`, `benchmark`, `payload` etc.) in their standard Latin or established loanword form.
- **Architecture Invariants & System Concepts**: System architectural concepts, specification terminology, and invariant terms (e.g., `Architecture Core Invariants`, `Single Source of Truth (SSOT)`, `Harness Triad`, `Prompt History`, `PreToolUse`, `PostToolUse`, `Fail-open`, `Atomic Mutation`, `Zero-Anaphora`) MUST never be rendered as isolated Korean loanwords or literal translations (such as standalone `아키텍처 핵심 불변식`) without their original English term.
- When expressing in Korean, keep the original English term intact or employ bilingual parenthetical notation (e.g., `Architecture Core Invariants(아키텍처 핵심 불변식)` or `아키텍처 핵심 불변식(Architecture Core Invariants)`).
- Strictly avoid unnatural, mechanical literal translations (e.g. converting `prompt` to `지시문` 또는 `token` to `표식`).
### 5.2 Strict Meaning Anchor Invariance
- 100% preservation of core facts, numbers, dates, version strings, identifiers, quotes, logic, and citations. Never alter, omit, or dilute substantive content while refining prose naturalness.
---
## 6. Pre-Output Naturalness Self-Check & Precedence
Before emitting any Korean text, perform the following verification:
1. **Context & Syntax Check**: Unnecessary repetitive subjects (`우리는`, `시스템은`) omitted naturally based on discourse. Direct objects placed pragmatically to prevent ambiguity.
2. **Translation-ese Check**: No double passives (`~되어지다`), by-passives (`~에 의해`), literal pronouns (`그`, `그녀`), structural metaphor suffixes (`~ 축`), or experience possession (`~경험을 보유하다`).
3. **Cliche & Punctuation Check**: Zero AI signature cliches inserted. No commas immediately following connective endings (`-고,`, `-며,`).
4. **Rhythm & Register Check**: Ending diversity maintained (no 4+ identical ending streak); speech level consistent throughout; technical loanwords preserved.
5. **Meaning Fidelity Check**: 100% preservation of facts, figures, and technical logic.
**Precedence**: Top-priority mandatory rule governing all natural Korean composition. It outranks all general stylistic defaults.