E.8:4.2 - Stylistic Principles (S-0 … S-19)

#	Principle	Guideline
S-0	Governing-claim flow	Begin with the recognisable working situation and governing claim or action. Add context, grounding, examples, and a closing line only when they help the reader understand or use that claim.
S-1	Density without Jargon	Short declarative sentences; tool names belong in Pedagogy/Tooling.
S-2	Internal Cohesion	Inline references to Pillars and related patterns.
S-3	Embedded Mini-Definitions	Gloss a new term in parentheses on first appearance.
S-4	Contextualisation	Brief historical or disciplinary lineage references.
S-5	Grounded Clarification	State the pattern’s positive object and move first. Apply the `F.19` plausible-reader guard test; retain a local negative boundary only for a grounded misreading that changes understanding or action.
S-6	Earned closing line	End when the result or boundary is clear. Add a memorable closing line only when it reinforces that result without introducing a new claim or displacing the practical close.
S-7	Generative over Prescriptive	Present rules as enabling constraints, not bureaucracy.
S-8	Grounded transfer examples	Use examples from other fields when the pattern claims transfer breadth and each example changes recognition, application, or a boundary. No fixed example count establishes breadth.
S-9	Physical Grounding Reference	Tie an abstraction to the actual system doing the work and to the holon or physical process it changes. Mention a local transformer system-role classification or an obtaining assignment only when it changes the claim; ordinary transformer may remain readable metonymy for that system.
S-10	Readable blocks	Keep the governing claim with the explanation needed to use it. Split prose or use a list only when that structure makes the reader’s work easier; no sentence or item count is a verdict.
S-11	Narrative Flow	Foreground the governing practitioner claim or action and let the section read as a continuous explanation. Apply `F.19` when coordination, catalogues, or modifiers create bullet soup or delay that message.
S-12	Full claims over tags	Use a clause when a list item carries a claim or action. Labels, values, and locally complete steps need no artificial subject-and-verb expansion; item count and sentence count are not verdicts. Use the `F.19` contribution and list tests.
S-13	SoTA-Echo structure	Name the practice question, selected best-known line, serious alternative or default, defect overcome, exact pattern mutation, source roles and limits, and reopen condition. Assign roles from answer-changing content, not authority, prevalence, freshness, or praise: an official source may be the best-known line if its answer wins; lineage-only and identity/currentness-only material stays outside.
S-14	Didactic-content sufficiency	New and substantially revised patterns carry enough didactic content to be teachable without nearby project notes.
S-15	Worked slices over scenario labels	Transform-like families show at least one concrete source and resulting-publication slice; scenario names alone are not enough.
S-16	Ordinary vs FPF-governed wording realism	Keep ordinary use light, and make heavier review records explicit only for disputed, high-risk, or higher-impact cases.
S-17	Self-contained monolith prose	A merged pattern must explain itself inside the monolith; planning shorthand and review-context dependencies are not admissible in pattern prose.
S-18	Intended-reader discipline	Address the intended framework user. Explain the Methods, their organization, alternatives, costs, and use-changing reasons in the public body. Keep current development, review, evaluation, projection, and landing correspondence in its own carrier under `E.8:4.2.3`.
S-19	Precision before relaxation	Apply the connected `F.19` reading and kind/loss comparison before accepting a plain or didactic rewrite. Route only an unresolved FPF head, qualifier, relation, or admissible-use question to `E.10`, `E.10.ARCH`, or its subject pattern.

Authors use the principles as a scaffold, not a straitjacket: the goal is coherent, engaging insight. Engagement remains subordinate to semantic discipline: hooks, quotable lines, Plain restatements, and didactic images may improve recognition, but any ontological, evidence, causal, assurance, bridge, gate, work, decision, or admissibility claim kind or admissible-use boundary they carry must be recoverable through the governed Tech reading or named neighboring pattern. Ordinary Plain prose without that claim kind or admissible-use boundary stays ordinary prose.

S-0 (Governing-claim flow) — explanation

Open with the recognisable working situation and the claim or action that governs the passage. Add history, related patterns, examples, imagery, or a recall line only when it helps the intended reader understand or use that claim. A prerequisite may come first when the reader needs it to interpret the claim or act safely. Apply F.19 when atmosphere, coordination, or rhetorical scaffolding delays the governing message.