#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 same-lineage weakening from one fuller-source side into a narrower-use rendering, whether the weakening was planned before publication or discovered during review of a target that can be retained only under a weaker-use card. That fuller-source side may be one governed source episteme/publication or one declared source set with a stable source-set identifier and bounded membership; it is not an open corpus.

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 when. A summary, briefing, redaction, dashboard tile, lookup handle, didactic compression, or other readable target weakens distinctions, recoverability, reliability transport, or supported-use posture from one fuller-source side, or when review discovers that the target can be retained only as a weaker rendering.

#Keywords

• controlled semantic coarsening
• fuller source episteme/publication
• weakened rendering
• narrower supported use
• unsupported downstream use
• reopen trigger
• redaction
• dashboard tile
• lookup handle
• state-representation shortcut.

#Relations

#Content

#Problem frame

Use this when. A summary, briefing, redaction, dashboard tile, lookup handle, didactic compression, or other readable target weakens distinctions, recoverability, reliability transport, or supported-use posture from one fuller-source side, or when review discovers that the target can be retained only as a weaker rendering.

Controlled Semantic Coarsening governs one weaker rendering that remains useful only because the fuller-source side stays identifiable, the supported use is narrower, downstream use is unsupported, and escalation reopens that fuller-source side. It is the FPF governing pattern 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: fuller-source side, weakened rendering, narrower supported use, main weakening, unsupported downstream use, and reopen trigger. Read orientation use, reliance use, operative claim, unsupported downstream use, and reopen trigger through the shared E.17:5.1c terms; use E.17:5.1d when the primary live question may be ordinary rewrite, representation change, explanation, comparison, bridge/substitution, work/reliance, gate, evidence, assurance, retargeting, or carrier/front-end work instead of coarsening.

Neighboring project records and governing patterns. Ordinary same-entity wording belongs under A.6.3.CR; representation-scheme change belongs under A.6.3.RT; explanation-facing class discipline belongs under E.17.EFP; bounded comparison belongs under E.17.ID.CR; bridge or substitution use belongs under F.9 / F.9.1; changed described entity belongs under A.6.4; work authority requires A.15-governed project method/work material; gate or adjudication authority requires A.20 / A.21-governed project records.

What goes wrong if missed. A helpful weak rendering starts acting like the fuller-source side: 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 admissible way to publish weakened renderings without hiding loss, overclaiming authority, or forcing every ordinary summary through a full assurance record. This is the positive path for bounded dashboard tiles, redactions, partner notes, lookup handles, workshop simplifications, and didactic compressions that help work without pretending to be the fuller source.

Working action spine. A weaker rendering is useful but cannot carry the fuller source -> separate fuller source, weaker rendering, narrower supported use, main weakening, unsupported downstream use, and reopen trigger -> use the weak rendering for orientation, triage, disclosure, retrieval, comparison, or planning preparation -> output the six-row mini-card -> reopen or hand off if reuse, reliance, citation, dispute, bridge, work, gate, privacy, or engineering-justification pressure appears.

Ordinary use. If the weaker rendering only supports orientation, bounded disclosure, retrieval, workshop framing, preliminary triage, comparison, or planning preparation, use the six-row mini-card and stop there.

Load-bearing use. Open the fuller coarsening record only when the weakened rendering will be externally relied on, disputed, cited, used across context, policy-bearing, bridge-adjacent, work-adjacent, gate-adjacent, privacy-sensitive, or engineering-justification-facing.

Stop condition. Stop at the mini-card when the weakened rendering changes no next admissible work/reliance, disclosure, review, or planning-preparation move and blocks no concrete overclaim beyond its narrower supported use.

Supported-use examples.

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 described entity, work authority, approval, adjudication, or gate authority. Use the neighboring governing pattern or authority source for that primary question.

#Problem

FPF often needs a weaker form of a fuller-source side: 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 fuller-source side remains governing;
• the target is weaker or less recoverable;
• the target supports only narrower use;
• downstream use is unsupported;
• downstream use reopens the fuller-source side or moves to the exact governing pattern or authority source that supports the requested use.

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

#Forces

#Solution

Controlled Semantic Coarsening governs one source/rendering relation.

• Fuller-source side means the governed U.Episteme, governed U.EpistemePublication, or declared source set that still carries the fuller claim, distinction, evidence relation, trace relation, or authority-reference relation. A declared source set must have a stable source-set identifier, bounded membership, and a reopen route; an open corpus, folder, topic area, search-result cluster, or vague document neighborhood is not a fuller-source side.
• Weaker rendering means the target readable form that carries less detail, less recoverability, weaker reliability transport, or narrower supported use than the fuller-source side.
• 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 downstream 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 fuller-source side, re-expansion in the current rendering or publication, or handoff to another governing pattern or authority source.
• 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.

A CSC card makes only the narrower supported use named on the card admissible for the weaker rendering. It never makes the unsupported downstream use admissible; it only tells the reader when and where to reopen the fuller-source side or hand off to the governing pattern that carries that downstream use.

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

If the weaker rendering is used only for local orientation and the fuller-source side remains adjacent, the six-row card may be inline or implicit by immediate context; do not create a durable Controlled Semantic Coarsening object unless reuse, reliance, citation, or dispute appears.

#First check

Before using this pattern, ask five questions:

1. Is there exactly one fuller-source side: one governed source episteme/publication or one declared source set with stable identifier, bounded membership, and reopen route?
2. Is the target weaker than that fuller-source side, or has review shown that it can be retained only as a weaker rendering?
3. Does the target support only narrower use?
4. Is downstream use explicitly unsupported?
5. Is the fuller-source reopen or governing-pattern handoff trigger visible?

If any answer is no, do not polish a coarsening story. Use the ordinary governing pattern or recover the project source record / authority-reference relation that actually supports the requested use. If the required support is missing, create only a prospective repair/request/decision/work-plan/source-gap record; do not treat that record as retroactive support for the weak rendering, earlier claim/effect, work occurrence, evidence, approval, gate passage, release permission, or engineering justification.

#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:

The fields below inherit the E.17:5.1e local-field rule. They are review aids for one weaker-rendering case, not U.Kind, SurfaceKind, RelationKind, KindBridge, EvidenceKind, GateDecision, SpeechAct, Commitment, U.Work, authority source, or project source record unless another governing FPF pattern explicitly instantiates that object.

• 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;
• governingFpfLocusRef, projectSourceRecordRef, or one privileged reopen path, so a weak target cannot reset its own provenance;
• coarseningBranch and supportedUsePosture as separate fields;
• 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 the E.17:5.1b postures could diverge: source pointer, source availability, source retrieval, source use, source faithfulness, claim support, contradiction, plausibility-only, omission, weakening, strengthening, added linkage, independent verification, supported use, forbidden downstream use, or reopen trigger;
• 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 reader-reliance or user-evidence check when readers may mistake the weaker rendering for authority it does not carry;
• whether local re-expansion is enough to repair the current rendering or whether downstream use still needs return to the fuller-source side or named authority source.

#Branch and supported-use discipline

coarseningBranch answers what sort of coarsening case this is. supportedUsePosture 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 provide claim support themselves. Authority-source-reopen-only use covers the exceptional case where the weak rendering names the source whose authority-source relation must be reopened; the weak rendering itself does not become the authority source, evidence source, gate source, or work source.

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

Exceptional interop-facing simplification is not ordinary coarsening. It is admissible 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 source epistemes/publications 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-overread

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

Recoverability and supported use are separate. A recoverable weak rendering is not automatically supported for downstream 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 fuller-source side 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 fuller-source side 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 described entity or described set. If several entities, alternatives, or slices become one new class target or proxy target, exit to A.6.4.

#Neighbor exits

Neighboring governing patterns 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 fuller-source side, at least one weaker-rendering side, one declared narrower supported use, one unsupported downstream use, and one visible fuller-source reopen or governing-pattern handoff condition. The fuller-source side may be one governed source episteme/publication or one declared source set with stable source-set identifier and bounded membership; it must not be an open, vague corpus.

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 publication face or channel.

Well-formedness constraint CSC-WF-3 (source path continuity). A weak-to-weaker chain remains well formed only while the same fuller-source side, 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 fuller source and the unsupported downstream 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 admissible 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 fuller 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 downstream uses are approval, audit closure, release gate, causal proof, and work order.

Redacted partner note. The fuller 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 source.

Redacted functional-description publication. The fuller source is a functional architecture note that names flow relations, method-selection limits, work-plan prerequisites, result-measurement requirements, and two exception cases. The weaker rendering is a partner-facing table that keeps the main flow relation and removes the exception cases and result-measurement details. Its narrower supported use is bounded orientation for coordination. Work planning, gate passage, evidence, engineering justification, control-architecture use, and release permission reopen the fuller source or exit to A.15, A.10, B.3, A.20 / A.21, or B.2.5.

Exceptional interop-facing simplification. The fuller 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 fuller source basis.

Bad fit: hidden work authority. Deployment may proceed; see summary S-3. This is not an admissible controlled coarsening card. The sentence tries to convert a weak summary into execution or gate authority. Use A.15, A.20, or A.21, and reopen the fuller 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 downstream use, source reopen, and neighboring-pattern 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

A conformance check is retained only if it changes the next admissible use of the weaker rendering, blocks a concrete overclaim, or preserves the fuller-source reopen path needed for the declared supported use.

#CSC-Core

#CSC-Conditional

#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 supported use. The pattern therefore does not ban weakened renderings; it makes the source/rendering relation explicit enough that later users know when to stop, reopen, or hand off to another governing pattern or authority source.

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

The core memory aid is simple: a weak rendering may help reading, but it must not become the fuller-source side it was derived from. It may expose or cite the fuller-source side or a project source record; that exposed source remains the support, not the weaker rendering's readable face. If support is missing, a repair/gap/reopen record may guide only future repair or return to source; it does not backdate the weak rendering into source support.

#SoTA Alignment: Adopted/Adapted Invariants And Rejected Shortcuts

SoTA alignment rule. Read each row here as source idea -> local FPF invariant -> practical local test -> popular shortcut rejected. A source citation governs nothing by reputation; it counts only when the cited idea is translated into the Solution, conformance checks, boundary rules, worked slices, and Relations of this pattern.

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 discipline.

Positive SoTA role. Use CSC when a weaker readable rendering is still worth using in project work, but only for a narrower supported use and without pretending that the rendering carries the fuller-source side's support.

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

Semantic-web boundary. In the W3C row, Data on the Web, SHACL, and DCAT support publication metadata, provenance, validation, cataloging, and interoperability. They do not by themselves support work occurrence, gate passage, bridge/substitution use, equivalence, release permission, or project claim support; those uses require the governing pattern or project source record that carries that claim.

#Relations

• Specializes: A.6.3 U.EpistemicViewing for same-lineage 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 hand off here when a weaker rendering's narrower-use, unsupported-use, and reopen card becomes the primary question.
• Governing-pattern relation wording: this pattern is a specialization under A.6.3, not a bundle, suite, profile, overlay, or review pack. Its governing role is limited to the controlled-coarsening relation itself.

#Boundary with quantum-like state-representation coarsening

Use CSC first when one fuller-source side, model, state representation, or evidence set is made less detailed for a narrower use, or when review discovers that a target already in circulation can be retained only under a weaker-use card: 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-abstraction 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 rule, probe frame, or export admissibility is part of the modeling requirement, or no faithful-enough export of the represented state for the supported 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

---

Last Updated: 2026-05-12 — this section last modified in upstream FPF commit f73766dd (github.com/ailev/FPF)