Voice rules

Voice cross-cuts every layer

Voice rules affect how memory is expressed, retrieved, summarized, and applied. The durable preference belongs in identity, but the operational rule touches every writer.

Why this is not just identity

Identity stores the preference. Voice policy tells every layer writer how to express content without weakening retrieval. A procedural runbook, an episodic correction, and a decision record should all follow the same communication constraints while preserving their layer-specific format.

Identity	Stores durable voice preference and collaboration boundaries.
Semantic	Uses clear definitions and avoids performative phrasing.
Episodic	Records what happened without rewriting tone into analysis.
Procedural	Keeps steps direct, testable, and low-fluff.
Decisions	States trade-offs and consequences without rhetorical padding.

Voice rule note

---
type: identity
topic: voice
last_verified: YYYY-MM-DD
---
Prefer direct, concrete engineering prose. Surface assumptions,
trade-offs, and blockers. Avoid cheerleading and filler.

Good voice rule

Use concise, factual prose. Put findings before summary in reviews. Name dates, paths, and assumptions when ambiguity matters.

Poor voice rule

Sound smart and friendly.

This is too vague to enforce and too subjective to validate.