#Controlled Semantic Coarsening

A.6.3.CSC · Stable · Architectural (A) · Normative unless marked informative · Part A - Kernel Architecture Cluster

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a fpf-memory product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Placement. Controlled Semantic Coarsening is a specialization under A.6.3 U.EpistemicViewing for deliberate same-lineage weakening from stronger source-bearing material into a narrower-use rendering.

Builds on. A.6.3, A.6.3.CR, A.6.3.RT, E.17.EFP, A.6.P, E.8, E.10, E.19, and F.18.

Coordinates with. E.17.ID.CR, F.9, F.9.1, A.15, A.6.4, A.20, and A.21.

Use this pattern when a summary, briefing, redaction, dashboard tile, lookup handle, didactic compression, or other readable target intentionally weakens distinctions, recoverability, reliability transport, or supported-use strength from a stronger source-bearing material.

#Keywords

• controlled semantic coarsening
• stronger source
• weaker rendering
• narrower supported use
• unsupported heavier use
• reopen trigger
• redaction
• dashboard tile
• lookup handle
• state-representation shortcut.

#Relations

#Content

#Problem frame

Use this pattern when a summary, briefing, redaction, dashboard tile, lookup handle, didactic compression, or other readable target intentionally weakens distinctions, recoverability, reliability transport, or supported-use strength from a stronger source-bearing material.

Controlled Semantic Coarsening governs one weaker rendering that remains useful only because a stronger source stays identifiable, the supported use is narrower, heavier use is unsupported, and escalation reopens the stronger source. It is the FPF owner for that source/rendering relation. It is not a tag, token, U.* kind, publication face, carrier, bridge card, stance overlay, work plan, approval, or gate.

Start here when. Your first honest artifact is a small controlled-coarsening card: stronger source, weaker rendering, narrower supported use, main weakening, unsupported heavier use, and reopen trigger.

Typical next owners. Ordinary same-entity wording routes to A.6.3.CR; representation-scheme change routes to A.6.3.RT; explanation-facing class discipline routes to E.17.EFP; bounded comparison routes to E.17.ID.CR; bridge or substitution use routes to F.9 / F.9.1; changed object-of-talk routes to A.6.4; work authority routes to A.15; gate or adjudication authority routes to A.20 / A.21.

What goes wrong if missed. A helpful weak rendering starts acting like the stronger source: a summary becomes evidence, a redaction becomes accountability closure, a dashboard tile becomes a causal verdict, a comparison note starts supporting bridge/substitution use, or a briefing becomes work authority.

What this buys. FPF users get a cheap lawful way to publish weakened renderings without hiding loss, overclaiming authority, or forcing every ordinary summary through a full assurance record.

Not this pattern when. Not this pattern when the primary question is ordinary same-entity wording, representation-medium change, explanation fidelity, comparison, bridge/substitution use, changed object-of-talk, work authority, approval, adjudication, or gate authority. Use the neighboring owner that governs that primary question.

#Problem

FPF often needs a weaker form of stronger material: a manager summary, a redacted disclosure note, a dashboard tile, a lookup surrogate, a workshop simplification, or a didactic compression. The weaker form can be valuable, but it becomes dangerous when readers forget that its authority is narrower than the source.

The core failure is not ordinary omission by itself. The failure appears when the weaker rendering stays honest only under a supported-use card like this:

• the stronger source remains governing;
• the target is weaker or less recoverable;
• the target supports only narrower use;
• heavier uptake is unsupported;
• heavier use reopens the stronger source or reroutes to a more honest owner.

Without a named pattern for that relation, neighboring patterns repeat partial coarsening rules locally. The repetition hides the shared burden and makes it too easy for weak renderings to travel as if they were the stronger source.

#Forces

#Solution

Controlled Semantic Coarsening governs one source/rendering relation.

• Stronger source means the source-bearing material that still carries the stronger claim, distinction, evidence, trace, or authority.
• Weaker rendering means the target readable form that intentionally carries less detail, less recoverability, weaker reliability transport, or narrower supported use.
• Narrower supported use means the practical use the weaker rendering can still support, such as orientation, retrieval, bounded disclosure, workshop framing, or preliminary triage.
• Unsupported heavier use means the use the weaker rendering cannot support alone, such as approval, audit closure, release gate, work plan, equivalence, bridge/substitution use, accountability finding, or canonical technical claim.
• Reopen trigger means the condition that requires return to the stronger source, re-expansion in the current rendering or publication, or reroute to another pattern owner.
• Load-bearing case means a coarsening case that will be cited, disputed, externally relied on, policy-bearing, bridge-adjacent, gate-adjacent, work-adjacent, privacy-sensitive, or assurance-facing.

#Ordinary mini-card

For ordinary use, publish only the smallest card that keeps the weaker rendering honest.

The card may live inline. Inherited source pins count when the surrounding publication already makes the stronger source visible.

#First check

Before using this pattern, ask five questions:

1. Is there a stronger source-bearing material?
2. Is the target deliberately weaker?
3. Does the target support only narrower use?
4. Is heavier use explicitly unsupported?
5. Is the stronger-source reopen or reroute trigger visible?

If any answer is no, do not polish a coarsening story. Use the ordinary host pattern or reroute to the more honest owner.

#Ordinary vs load-bearing

Ordinary cases should remain light. A short orientation summary, redacted partner note, workshop simplification, or lookup handle does not need the full assurance record if the six-row card is recoverable.

Load-bearing cases add only the fields that matter for the live pressure. This list is not a daily gate for ordinary summaries, briefings, redactions, or lookup handles:

• sourceLane and targetLane when authored unit, publication face, PublicationSurface, InteropSurface, or carrier could be confused;
• targetAuthoredUnitIfAny when the weaker rendering is carried by one authored-readable unit that is distinct from the publication, disclosure note, dashboard tile, or InteropSurface on which it appears;
• governingSourceRef or one privileged reopen path, so a weak target cannot reset its own provenance;
• branchReading and supportedUseClass as separate axes;
• lossClass and recoverabilityAfterCoarsening when the loss affects claim support, accountability, supported-use posture, or later citation;
• at least one kept claim/distinction bundle, one weakened or dropped bundle, and one reopen-only bundle when the case is disputed or later-cited;
• sourceSupportPosture when source-pointer-present, source-faithful, source-used, claim-supported, and supported-for-this-use could diverge;
• uncertainty or abstention posture when branch reading, preserved distinctions, source pin, or supported use cannot yet be stated stably;
• independent-verification question when downstream testing, assurance, gate, or external reliance appears;
• audienceOverReadRisk, plus a light uptake or user-evidence check when material readers may mistake the weaker rendering for heavier authority;
• whether local re-expansion is enough to repair the current rendering or whether heavier use still needs return to the stronger governing source.

#Branch and supported-use discipline

branchReading answers what sort of coarsening case this is. supportedUseClass answers which use of the weaker rendering remains supported. Do not infer one from the other.

Ordinary supported use covers aggregation, quotient-like orientation, didactic or report summaries, and briefings only for the named narrower use. Source-pinned-only use covers surrogate, index, retrieval-hint, lookup, and handle forms; these may help find or orient to the source but do not become semantic authority.

Privacy or redaction weakening is lawful here only when the card names the sharing boundary, what was withheld or weakened, the main re-identification or accountability risk being reduced, the stronger-source review path, and the accountability or gate uses that remain unsupported.

Exceptional interop-facing simplification is not ordinary coarsening. It is lawful here only when it stays source-tethered and names the operative relation kind, such as bounded contrast, broader/narrower, partial overlap, proxy, lossy normalization, or context-bounded match. If the weak rendering makes bounded contrast across contexts or materials primary, use E.17.ID.CR. If it implies equivalence, substitution, projection, or bridge/substitution use, use F.9 or F.9.1.

#Loss, recoverability, and anti-drift

The card must name the live loss class before a coarsened rendering is treated as lawful.

Recoverability and supported use are separate. A recoverable weak rendering is not automatically supported for heavier use, and an unsupported use is not repaired merely by saying the source could be found.

A weak-to-weaker chain may not silently reset provenance. If one coarsened rendering is reused to make another, the same stronger governing source must stay explicit, the earlier loss envelope and uncertainty posture must remain visible, and the new rendering must declare only the added loss delta. If that cannot be stated cleanly, reopen the stronger source rather than extending the chain.

Aggregation or quotient-like coarsening remains inside this pattern only while the weak rendering keeps one bounded described set, slice, case bundle, or alternative bundle explicit as the object of talk. If several entities, alternatives, or slices become one new class target or proxy target, exit to A.6.4.

#Neighbor exits

Neighboring owners may point here when a weaker rendering relation becomes primary. They do not own the shared coarsening relation by local repetition.

#Well-formedness constraints

Well-formedness constraint CSC-WF-1 (source/rendering relation). A controlled-coarsening case is well formed only when it contains exactly one stronger-source side, at least one weaker-rendering side, one declared narrower supported use, one unsupported heavier use, and one visible reopen or reroute condition.

Well-formedness constraint CSC-WF-2 (no authority upgrade). A weaker rendering does not gain evidence, bridge, work, approval, gate, or adjudication authority by repetition, fluency, audience convenience, citation, or publication on a more visible surface.

Well-formedness constraint CSC-WF-3 (source path continuity). A weak-to-weaker chain remains well formed only while the same stronger governing source, prior loss envelope, uncertainty posture, and added loss delta remain recoverable.

#Archetypal Grounding

Tell. Controlled semantic coarsening is the disciplined act of making a weaker rendering useful while keeping the stronger source and the unsupported stronger uses visible. It is not simplification as style. It is simplification under a source, use, loss, and reopen card.

Show (System). A service team has an incident review with trace details, confidence bands, and alternative branches. A manager dashboard tile says: Cache failover evidence is the leading concern; details remain in IR-42. The tile may orient planning, but it may not approve release, close audit, prove causality, or trigger work without reopening IR-42.

Show (Episteme). A research review bundle is given the lookup handle cache-failover risk. The handle is lawful for retrieval and orientation only. Any claim-bearing use reopens the review bundle because the handle does not carry the evidence, alternatives, or source support.

#Worked slices

Manager orientation summary. The stronger source is incident review IR-42 with trace details, confidence bands, and alternative branches. The weaker rendering is Cache failover evidence is the leading concern; details remain in IR-42. Its narrower supported use is orientation for planning conversation. Its unsupported heavier uses are approval, audit closure, release gate, causal proof, and work order.

Redacted partner note. The stronger source is a full incident record with actor identity, trace path, and recovery evidence. The weaker rendering is a partner-facing redacted note that withholds actor identity and trace path. Its narrower supported use is bounded disclosure and coordination. Accountability, legal, audit, readiness, and gate uses reopen the full incident record or exit to the relevant authority owner.

Exceptional interop-facing simplification. The stronger source is two pinned context notes plus their bridge or comparison basis. The weaker rendering is: For this exchange only, Field A is treated as broader than Field B; see source notes for exceptions. The rendering may orient the exchange, but any equivalence, substitution, projection, bridge-row, or approval use exits to F.9 / F.9.1 or reopens the stronger source basis.

Bad fit: hidden work authority. Deployment may proceed; see summary S-3. This is not a lawful controlled coarsening card. The sentence tries to convert a weak summary into execution or gate authority. Reroute to A.15, A.20, or A.21, and reopen the stronger source before any work or approval claim proceeds.

#Bias-Annotation

Lenses tested: Gov, Arch, Onto/Epist, Prag, Did. Scope: Universal for source/rendering relations that claim controlled semantic coarsening inside FPF.

This pattern favors Prag and Did by allowing useful weak renderings to remain cheap and readable. It also favors Gov and Arch by requiring unsupported heavier use, source reopen, and neighboring-owner exits when authority pressure appears. The mitigation for over-governance is the ordinary mini-card: ordinary cases stay light, and only live pressure adds load-bearing fields.

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

#Rationale

Controlled coarsening is useful because FPF work often needs cheap readable forms. It is risky because cheap readable forms often travel farther than their lawful use. The pattern therefore does not ban weakened renderings; it makes the weaker-source relation explicit enough that later users know when to stop, reopen, or reroute.

This pattern is narrower than a general simplification pattern. It applies only when the weaker target remains tied to stronger source-bearing material and carries a narrower-use card.

The core memory aid is simple: a weak rendering may help reading, but it must not become the source it weakened.

#SoTA-Echoing

Purpose. This section justifies the pattern's safeguards. It is not an additional operational checklist. The Solution, Conformance Checklist, worked slices, and Relations above carry the live pattern law.

The practical implication is the same across these traditions: weak readable surfaces are valuable, but their supported use depends on source support, relation kind, validation burden, audience, and reopen path. The worked slices in A.6.3.CSC:5.1 are the nearest recovery anchors for those SoTA rows.

#Relations

• Specializes: A.6.3 U.EpistemicViewing for deliberate weakening across a source/rendering relation.
• Coordinates with: A.6.3.CR, A.6.3.RT, E.17.EFP, E.17.ID.CR, F.9, F.9.1, A.15, A.6.4, A.20, and A.21.
• Does not replace: conservative retextualization, representation transduction, explanation profiling, bounded comparative reading, bridge-card discipline, stance overlay, changed-object discipline, work authority, gate authority, or adjudication authority.
• Entry relation: neighboring patterns may route here when a weaker rendering's narrower-use, unsupported-use, and reopen card becomes the primary question.
• Host relation wording: this pattern is a specialization under A.6.3, not a bundle, suite, profile, overlay, or review pack. Its shared owner role is limited to the controlled-coarsening relation itself.

#Boundary with quantum-like state-representation coarsening

Use CSC first when a fuller material is deliberately made less detailed for a narrower use: summary, dashboard row, orientation note, partner-safe version, simplified diagram, or coarse working description. Ordinary controlled simplification remains CSC even when it is lossy.

Action path:

1. Name the fuller source and the less detailed version.
2. State the use scope of the less detailed version before stating what it means.
3. State the lost distinctions, evidence paths, comparability, uncertainty, state dimensions, or alternatives.
4. State supported use and unsupported use in practical terms.
5. State when to reopen the fuller source.
6. If the weaker rendering claims to preserve action, intervention, manipulation, explanation, or cross-level structure, state the causal-abstraction or approximate-causal-abstraction mapping before treating the shortcut as QL coarsening.
7. Ask whether the shortcut depends on a QL cue such as incompatible probes, contextual probability, instrument-like update, open-information-system update whose update law, probe frame, or export lawfulness is part of the modeling burden, or no faithful-enough export of the represented state for the intended use. If not, stay in CSC.
8. If yes, coordinate with the C.26 state-representation coarsening support section while leaving CSC as the controlled-use boundary for the weakened version.

For ordinary use, start with the standard shortcut mini-form:

Use a fuller CSC/C.26 coarsening boundary record only when the weaker state representation will be reused, formalized, empirically compared, used in a high-stakes decision, or tied to a comparative performance claim:

Useful outputs:

• a CSC mini-form when the issue is controlled simplification;
• a fuller C.26 coarsening support record only when a QL cue remains and the claim is reusable, formal, empirical, high-stakes, or comparative-performance-bearing;
• no QL wording when the case is only summary, anonymization, diagramming, audience adaptation, or ordinary coarsening.

#A.6.3.CSC:End