ComparativeReading - bounded comparative reading over comparative review units

E.17.ID.CR · Stable · Part E - The FPF Constitution and Authoring Guides

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.

Status: Stable

Placement. Pattern for bounded comparative reading over comparative review units, coordinated with the neighboring A.6.3.*, F.9.1, and E.17.EFP patterns. Builds on. C.2.2a; A.16.0; F.9; E.14. Coordinates with. A.6.3; A.6.3.CR; A.6.3.RT; F.9.1; E.17.EFP; E.17.AUD.LHR; B.5.2.0; B.5.2; OntologicalReframing; A.6.4; A.15; A.20; A.21. Active governing pattern. ComparativeReading is the governing pattern here under the wider InterpretationDiscipline family. The public pattern name is ComparativeReading, not interpretation-in-general. Citation names. Cite this pattern as E.17.ID.CR, ID.CR, or ComparativeReading. Do not cite it as unqualified ID or CR; use A.6.3.CR when the intended pattern is ConservativeRetextualization. Family-specialization guard. InterpretationDiscipline is a naming-level family label only. It is not a U.* kind, not a SurfaceKind, not a publication face, not a new episteme kind, not an authority-source reference, not a bridge taxonomy, not a second semantic track, and not a governing pattern by itself. The active governing pattern here is ComparativeReading; no artifact cites InterpretationDiscipline, ID, or CR alone as governingPatternRef or authoritySourceRef. Plain-name. Bounded comparative reading over comparative review units. One-line summary. ComparativeReading governs one comparative review unit over already available source epistemes/publications while the shared review frame stays preserved, one bounded contrast or a small set of bounded contrast rows is being made visible, and downstream claim/effect remains outside. The compared alternatives may be distinct entities when they stay under that shared review frame. Governed object in plain terms. The pattern governs the comparative review unit itself - the comparison note, small comparison sheet, or guided review aid that carries one bounded contrast or a small set of bounded contrast rows - not the whole source episteme/publication set and not the wider decision or work process.

Early comparative lens. Read the comparative-reading case through one early formula: one comparative review unit over already available source epistemes/publications keeps the shared review frame visible while making one bounded contrast or a small set of bounded contrast rows inspectable, with downstream claim/effect still left outside. The shared frame may be the same DescribedEntityRef, review target, described situation, decision situation, release candidate, method family, control scope, problem frame, or source-set anchor. Compared alternatives under that frame may be distinct objects. That is the whole early read. It does not govern interpretation in general, the whole source episteme/publication set, or the wider decision or work process.

Use this when. Use this pattern when you need a small comparative review unit, such as a comparison note, comparison sheet, or guided review aid, over already available source epistemes/publications so that a team can inspect one bounded contrast or a small set of bounded contrast rows while still keeping the shared review frame and compared alternatives explicit and without yet claiming equivalence, root cause, redesign, release approval, or another unsupported downstream claim/effect.

First-minute working moment. A team already has two or more source-pinned notes, sheets, views, or review aids on the table and needs one honest comparison unit that keeps the shared review frame visible while making one bounded contrast or a small comparison sheet inspectable. The compared items may be two design options for one release, two methods for one task family, two vendor bulletins for one control scope, or two programme strategies for one initiative. The real job is not yet action selection, approval, ontology repair, or wider work-process control. It is to help reviewers compare without pretending that the comparison note or sheet already became a decision.

First-screen questions.

What source epistemes/publications are being compared?
What one contrast or small set of contrast rows is being made visible?
What shared review frame remains preserved, and what compared alternatives stay distinct under it?
What does this note not decide?
What exit would make it a decision, prompt, bridge, ontology, work/reliance, gate, assurance, or adjudication case?

Working action spine. A comparison note or guided review aid is needed -> separate compared sources, one bounded contrast or small row set, shared review frame, distinct alternatives when present, and undecided downstream claim/effect -> use the unit for bounded review, source-finding, contrast inspection, or planning preparation -> output the seven-row ordinary working card or one compact note/sheet -> exit if decision, bridge, prompt, ontology, work/reliance, gate, assurance, or adjudication pressure begins. Use E.17:5.1c for orientation use, reliance use, operative claim, unsupported downstream use, and reopen trigger; use E.17:5.1d when the primary live question may be same-entity rewrite, representation change, coarsening, explanation, bridge/substitution, work/reliance, gate, evidence, assurance, retargeting, or carrier/front-end work instead of bounded comparative reading.

Primary working reader. The primary first-minute reader is an engineer-manager or programme lead using a bounded comparative review unit in ordinary review work. Architecture reviewers, release or compliance reviewers, research reviewers, and cultural or programme reviewers remain important secondary readers, but the first recognition block should still read engineer-manager-first rather than architecture-first.

Problem-owning practice reading. In ordinary practice, this pattern helps teams write design-review notes, release or compliance comparisons, incident triage comparisons, research review notes, and programme review aids when the real job is to compare already available source epistemes/publications under one shared review frame without yet claiming equivalence, action selection, or decision authority. The job is not to settle the full review or downstream decision process. It is to make one bounded comparative review unit honest enough that reviewers can inspect one contrast or a small set of contrast rows, know what downstream claim/effect stays outside, and stop arguing as if the note had already become a decision.

What goes wrong if you miss this. If this pattern stays unnamed, teams often flip between two bad readings. Either the comparative review unit is dismissed as if it were only harmless prose, or it is over-read as if it already licensed equivalence, action selection, gate pressure, or work/reliance. The practical result is distrust and friction in review work because readers can no longer tell whether they are looking at one bounded comparison aid or at a disguised decision.

What this buys you in practice. Naming the pattern buys one smaller and more usable review unit. A team can compare already available source epistemes/publications, inspect one bounded contrast or a small comparison sheet, and still keep downstream claim/effect outside. In practice that means review conversations move faster with less argument about whether the note already settled equivalence, approval, or the next work/reliance move.

Ordinary use. If the comparison only helps review, source-finding, contrast inspection, or planning preparation, keep one small comparison note or the seven-row ordinary working card; do not thicken it into a decision, bridge, release, or authority record.

Cheap stop after ordinary card. If the comparison note answers the seven-row card and no boundary pressure is live, stop. Do not open E.17.AUD.LHR, E.17.AUD.OOTD, E.17.EFP, A.6.3.CSC, bridge, prompt, work/reliance, gate, assurance, or authority paths.

Assurance-surface boundary. Read E.17.AUD.LHR, E.17.AUD.OOTD, interpretant-side fields, bridge/prompt/authority exits, and the heavier boundary tables as assurance or support material after the seven-row ordinary card, not as the ordinary first screen for one comparison note.

Load-bearing use. Open the fuller comparison-support apparatus only when the comparison will be externally relied on, disputed, cited, used across context, used to affect person/team status, or read as release, gate, bridge/substitution, action-selection, work/reliance, or engineering-justification support.

Stop condition. Stop once the comparison changes no next review, source-finding, contrast-inspection, or planning-preparation move and blocks no concrete overclaim about equivalence, decision, bridge/substitution, work/reliance, gate, or engineering justification.

Supported-use examples.

Supported project use	Source-finding or reversible probe	Unsupported use
A comparison note supports one bounded review discussion by naming the compared sources, shared review frame, compared alternatives when present, one contrast, and what remains undecided.	A comparison suggests the next source, method, or bridge claim to inspect without deciding substitution, method selection, release, or work reliance.	A comparison table is used as equivalence, bridge licence, method-selection decision, release decision, evidence, gate passage, or adjudication authority.

Admissible comparative-unit forms.

Single-contrast note — one bounded contrast with one comparison basis, one shared review frame, unsupported downstream claim/effect, world-contact limit, and exit trigger.
Small comparison sheet — a small set of bounded contrast rows under one shared review frame. Each row states its comparison basis; the sheet has one shared unsupported downstream claim/effect, one world-contact limit, and one exit trigger. It must not add an aggregate recommendation, ranking, or action-selection conclusion unless another governing pattern or project source supplies that support.

When one comparative note is itself lighter or simplified, it remains admissible here only while fuller-source return stays available and heavier bridge, action-selection, or work/reliance claim remains outside.

Not this pattern when. This is not the right pattern when the primary question is:

restating the same thing or shifting its representation rather than adding one bounded contrast under A.6.3.*;
carrying a controlled weaker rendering whose governing relation is fuller-source tether, narrower-use discipline, forbidden downstream claim/effect, and reopen duty rather than bounded comparative reading;
explicating an already-declared bridge stance rather than governing a comparative review unit under F.9.1;
deciding explanation-face use rather than carrying bounded comparative reading under E.17.EFP;
authored-unit described-entity stabilization after local repair;
abductive-prompt or action-selection pressure under B.5.2(.0);
ontology or target change under OntologicalReframing / A.6.4;
or downstream work/reliance, gate, assurance, or adjudication authority under A.15 / A.20 / A.21.

Neighboring-work boundary. If the live work is actually same-thing rewrite, bridge-stance note over an existing Bridge Card, explanation-face use, abductive prompt, ontology change, gate/authority work, or local authored-unit repair, keep the current comparative review unit narrow and use the FPF pattern that governs that outside work (A.6.3.*, F.9.1, E.17.EFP, B.5.2(.0), OntologicalReframing / A.6.4, A.15 / A.20 / A.21, E.17.AUD.LHR, or E.17.AUD.OOTD). The engineer-manager action is to keep the comparison note from carrying that outside work; if the outside work is live, recover the existing project source for that work when available. If no existing source carries the needed load-bearing claim, create only a prospective repair/request/decision/work-plan/source-gap record and otherwise keep the comparison note to inline orientation/source-finding; the new record must not be treated as retroactive evidence, approval, gate passage, performed U.Work, release permission, or assurance.

Ordinary recovery anchor. If the recognition block fits, keep three things recoverable: the governed comparative review unit, the seven-row ordinary working card in E.17.ID.CR:4.3.b.a, and the nearest ordinary worked slices in E.17.ID.CR:5.4.5 through E.17.ID.CR:5.4.6.c. Use E.17.ID.CR:4.1.d only if one pressure term still blocks the working read.

Quick kind-plus-lens reading. InterpretationDiscipline names the wider interpretation family and ComparativeReading names the active governing pattern here. Recover the case through the early comparative lens above: one comparative review unit over already available source epistemes/publications, the shared review frame preserved, one bounded contrast or small row set made visible, and downstream claim/effect still outside. If that read no longer holds, handle the neighboring work under the pattern or project source that governs it rather than widening this pattern into interpretation-in-general.

First-minute term reading. Read the early pressure terms this way. Shared review frame = the review target, described situation, decision situation, release candidate, method family, control scope, problem frame, or source-set anchor preserved across the comparison. Compared alternatives = the distinct options, methods, bulletins, strategies, notes, or source objects kept separate under that frame. Source epistemes/publications and source anchors = already available source epistemes/publications plus the notes, views, or links that keep the comparison checkable. allowedUse and misuseRisk = what this unit honestly supports now and what unsupported downstream reading it may wrongly attract.

Quick working-fit check. Before you read the heavier harness, ask:

Am I governing the comparative review unit itself?
Does the shared review frame stay preserved, with compared alternatives still distinct if they are distinct, while one bounded contrast or small row set is being made visible?
Is the main question still this bounded comparison rather than same-thing rewrite, authored-unit stabilization, or downstream authority?

If yes, stay here and use the ordinary working card. If no, use the neighboring-work boundary above and the fuller boundary table in E.17.ID.CR:4.5.

Worked-slice pointer. If you need one ordinary sentence fast, borrow the nearest admissible example from E.17.ID.CR:5.4.5 through E.17.ID.CR:5.4.6.c and then check it against the seven-row ordinary working card rather than treating the example itself as a second mini-harness.

Anti-fixed-process note. The quick checks, ordinary working card, worked-slice pointer, working order, and worked slices in this pattern are local aids and examples for one comparative review unit. They are not a canonical transduction process for the governed object here, not a mandatory fixed sequence for review work, and not a promise that admissible cases move through one fixed graph in one direction. FPF fixes the local governed object, the local move, the governing-pattern exits, and the inherited dynamic frame; actual work may reopen, back off, loop, or depend on outside observations and downstream constraints. Read the worked-slice bank sideways rather than as one required sequence: one admissible case may finish after a single bounded comparison, another may reopen after a new outside observation, and another may exit immediately once environmental change or downstream constraints make a neighboring pattern the more honest governing move.

Keywords

comparative reading
comparative review unit
bounded comparison
source episteme/publication lane
same described entity
bounded lift
forbidden downstream claim/effect
InterpretationDiscipline specialization.

Relations

E.17.ID.CRbuilds onU.LanguageStateSpace — Language-state chart over U.CharacteristicSpace

E.17.ID.CRbuilds onU.LanguageStateTransductionTrajectory — Optional trajectory-account normal form

E.17.ID.CRbuilds onAlignment & Bridge across Contexts

E.17.ID.CRbuilds onHuman-Centric Working-Model

E.17.ID.CRcoordinates withU.EpistemicViewing — describedEntity-Preserving Morphism

E.17.ID.CRcoordinates withControlled Semantic Coarsening

E.17.ID.CRcoordinates withConservativeRetextualization - same-described-entity textual re-expression

E.17.ID.CRcoordinates withRepresentationTransduction - same-described-entity representation-scheme transition

E.17.ID.CRcoordinates withBridge Stance Overlay

E.17.ID.CRcoordinates withExplanationFaithfulnessProfile - explanation classification over existing MVPK faces

E.17.ID.CRcoordinates withAuthoredUnitDiscipline / Local Head Restoration — repair the pressured local head before the authored unit inherits it

E.17.ID.CRcoordinates withAuthoredUnitDiscipline / AuthoredUnit Primary Described-Entity Discipline — authored-unit stability over one primary described entity and carried move

E.17.ID.CRcoordinates withU.AbductivePrompt

E.17.ID.CRcoordinates withAbductive Loop

E.17.ID.CRcoordinates withU.EpistemicRetargeting — describedEntity-Retargeting Morphism

E.17.ID.CRcoordinates withRole-Method-Work Alignment (Contextual Enactment)

E.17.ID.CRcoordinates withU.Flow.ConstraintValidity — Eulerian

E.17.ID.CRcoordinates withGateProfilization: OperationalGate(profile) (GateFit core)

E.17.ID.CRbuilds onBridge Stance Overlay

E.17.ID.CRbuilds onU.CrossContextSamenessDisambiguation — Repairing cross-context “same / equivalent / align” via explicit Bridges (RPR-XCTX)

E.17.ID.CRbuilds onU.EpistemicViewing — describedEntity-Preserving Morphism

E.17.ID.CRbuilds onExplanationFaithfulnessProfile - explanation classification over existing MVPK faces

E.17.ID.CRbuilds onAuthoredUnitDiscipline / Local Head Restoration — repair the pressured local head before the authored unit inherits it

E.17.ID.CRbuilds onAuthoredUnitDiscipline / AuthoredUnit Primary Described-Entity Discipline — authored-unit stability over one primary described entity and carried move

E.17.ID.CRcoordinates withAlignment & Bridge across Contexts

E.17.ID.CRcoordinates withU.CrossContextSamenessDisambiguation — Repairing cross-context “same / equivalent / align” via explicit Bridges (RPR-XCTX)

E.17.ID.CRcoordinates withWork-Relevant Source Restoration

E.17.ID.CRexplicit referenceU.EpistemicViewing — describedEntity-Preserving Morphism

E.17.ID.CRexplicit referenceBridge Stance Overlay

E.17.ID.CRexplicit referenceExplanationFaithfulnessProfile - explanation classification over existing MVPK faces

E.17.ID.CRexplicit referenceU.LanguageStateSpace — Language-state chart over U.CharacteristicSpace

E.17.ID.CRexplicit referenceU.LanguageStateTransductionTrajectory — Optional trajectory-account normal form

E.17.ID.CRexplicit referenceAlignment & Bridge across Contexts

E.17.ID.CRexplicit referenceHuman-Centric Working-Model

E.17.ID.CRexplicit referenceConservativeRetextualization - same-described-entity textual re-expression

E.17.ID.CRexplicit referenceRepresentationTransduction - same-described-entity representation-scheme transition

E.17.ID.CRexplicit referenceAuthoredUnitDiscipline / Local Head Restoration — repair the pressured local head before the authored unit inherits it

E.17.ID.CRexplicit referenceU.AbductivePrompt

E.17.ID.CRexplicit referenceAbductive Loop

E.17.ID.CRexplicit referenceU.EpistemicRetargeting — describedEntity-Retargeting Morphism

E.17.ID.CRexplicit referenceRole-Method-Work Alignment (Contextual Enactment)

E.17.ID.CRexplicit referenceU.Flow.ConstraintValidity — Eulerian

E.17.ID.CRexplicit referenceGateProfilization: OperationalGate(profile) (GateFit core)

E.17.ID.CRexplicit referenceAuthoredUnitDiscipline / AuthoredUnit Primary Described-Entity Discipline — authored-unit stability over one primary described entity and carried move

E.17.ID.CRexplicit referenceControlled Semantic Coarsening

E.17.ID.CRexplicit referenceU.CrossContextSamenessDisambiguation — Repairing cross-context “same / equivalent / align” via explicit Bridges (RPR-XCTX)

E.17.ID.CRexplicit referenceWork-Relevant Source Restoration

Content

Problem frame

Engineer-managers, programme leads, and research or cultural reviewers repeatedly need to prepare or share a small comparative review unit that helps a team read two already available source epistemes/publications together without overstating what that unit now supports. Typical moments include:

a design-review note that says one already available option write-up foregrounds coupling risk more than another;
a release or compliance comparison that says an internal control sheet and a vendor bulletin are not yet equivalent even though they speak to the same review task;
an operations comparison that says a dashboard view and a maintenance note foreground different operational pressures in the same service episode;
a research-review note that says one available synthesis foregrounds measurement uncertainty more than another without yet declaring a better method;
a program or cultural review note that says one available brief foregrounds participation continuity more than another without yet deciding funding, curation, or program direction.

These review units are useful precisely because they help a review move forward. They become dangerous when a reader starts treating them as if they already established equivalence, root cause, redesign priority, action selection, program choice, or approval.

Problem

Without a named comparative-reading discipline:

a useful comparative review unit is dismissed as if it were only harmless prose;
a cautious review aid is over-read as if it already licensed substitution, interoperability, or equivalence;
a comparative review unit quietly becomes action-selection pressure or hidden hypothesis work while still sounding calm;
same-entity viewing, explanation rendering, and bounded comparative reading collapse into one fuzzy review bucket;
ontology-facing target shift or changed described entity hides inside comparative wording;
a review unit written to support review is mistaken for work/reliance guidance, assurance shorthand, or release authority.

Forces

Force	Tension
Engineer-manager usability vs governance precision	The pattern must start from a recognisable review situation without hiding its neighboring patterns.
Middle-band reality	Some comparative readings are more committed than a bridge-stance overlay over an existing Bridge Card but still below full action selection.
Source tether vs interpretive lift	The case must add a bounded interpretive lift without pretending to create a new free-floating semantics.
Governed object vs surrounding work	The pattern must keep the review unit, the interpretive move, and the larger review process distinct rather than sliding between them by style.
Viewing restraint	Interpretation must not absorb same-entity viewing, conservative rewriting, or representation transduction whose main question is not comparative reading.
Bridge restraint	Interpretation must not become a second bridge taxonomy.
Explanation restraint	Interpretation must not become a shadow face-use discipline system next to `E.17.EFP`.
Abductive restraint	Interpretation must stop before abductive-prompt or action-selection pressure becomes live.
Ontology restraint	Interpretation must not hide same-referent / new-intension pressure or changed `DescribedEntityRef`.
Interpretant-side boundedness	Reader-fit may matter, but it must remain explicit and bounded rather than silently rewriting authority.

Solution - comparative review units with bounded comparative reading, escalation, and exit rules

Engineer-manager-first working use, governed-object distinction, and compact branch definition

The solution opening here follows E.17.ID.CR:4.3's working-model-first discipline. A solution-side reader first meets the engineer-manager working use and the governed-object distinction, then the compact ComparativeReading definition that names the formal comparative read. That order keeps the governing pattern explicit without making the compact definition a substitute for the working review moment.

Engineer-manager-first use

In plain working terms, this pattern is for a review unit that says something like:

this option write-up foregrounds integration pressure more than that one;
these two available source epistemes/publications are useful together, but they are not yet equivalent;
this dashboard view helps triage one contrastive question, but it is not yet a release decision or a root-cause claim;
this research synthesis foregrounds uncertainty more than that one, but it is not yet a method choice;
this program brief foregrounds continuity risk more than that one, but it is not yet a funding decision.

If that sounds like the review unit you need, keep the comparison unit bounded this way. If instead you are mainly restating source epistemes/publications, explaining them, opening a new abductive prompt or action-selection question, changing the described entity, or making a decision, handle that live work under the FPF pattern or project source that governs it before the comparison unit carries the claim.

Pattern, case, and governed-object distinction

This pattern presents the ComparativeReading as the active governing pattern inside the broader InterpretationDiscipline family. The family name marks the wider interpretation zone. The governing pattern here is narrower and more concrete than interpretation-in-general. It governs one comparative review unit and only the bounded comparative reading carried by that unit. The wider review or decision work remains outside the pattern except where neighboring-work boundary or authority limits are needed.

The kind stack should therefore be read explicitly:

family name = InterpretationDiscipline as the wider naming-level family;
family-level move class = bounded interpretation work at that wider level;
governing pattern = ComparativeReading;
governed object = the comparative review unit;
governed move = bounded comparative reading over already available source epistemes/publications;
wider work = the broader review or decision process that still sits outside this pattern.

The family name is only a naming aid for this branch. It is not a U.Kind, SurfaceKind, publication face, authority-source reference, or governing-pattern reference; when a record needs a governing pattern, cite E.17.ID.CR ComparativeReading or the more exact neighboring pattern.

In ordinary use the governed unit may appear as a short comparison note, comparison sheet, guided review aid, or guided comparative UI. Those are admissible unit forms, not rival governed objects.

This distinction matters because the pattern is not governing reading as such in the abstract and it is not governing the whole review or decision work. It is governing a small, reviewable unit that carries one bounded comparative lift over already available source epistemes/publications. The pattern does not create a new practical governed-unit family of its own; it tells when such a comparative review unit can stay modest and when a downstream claim/effect or decision-bearing record already belongs to another governed pattern.

Compact branch definition

ComparativeReading is the active governing pattern inside the InterpretationDiscipline family.

It governs one comparative review unit over already available, source-pinned epistemes/publications and carries one bounded comparative reading, or a small set of bounded contrast rows, over that unit.

It stays admissible only while the case preserves the shared review frame, keeps distinct alternatives distinct unless bridge/substitution support exists elsewhere, keeps the source anchors visible, keeps the added comparative lift bounded, and does not turn into same-entity viewing, bridge claims, explanation-face governance, prompt-bearing abductive work, ontology-facing reframing, retargeting, or downstream work/reliance authority.

Read this blockquote as the compact governing-pattern reminder. It should stay nearby and early, but not stand in front of the engineer-manager-first use block or the governed-object distinction that working readers need first.

Why the comparative-reading branch needs its own discipline

Teams already produce small comparative review units, often as comparison notes, comparison sheets, or guided review aids, that are more committed than a plain bridge-stance overlay over an existing Bridge Card but still below action selection, ontology reframing, retargeting, or approval guidance. Leaving that middle band unnamed creates two opposite failures: one reader dismisses the review unit as harmless prose, while another over-reads it as if it already carried substitution, action-selection pressure, or action authority.

This pattern gives teams a narrow way to prepare, share, and inspect that comparative review unit without smuggling a downstream claim/effect beyond what the source, bridge stance, and bounded use can honestly support.

Local working vocabulary

This pattern uses a small local vocabulary for review.

Comparative review unit = a lightweight review unit such as a short comparison note, small comparison sheet, guided review aid, or guided comparative UI whose explicit job is one bounded comparative reading or a small set of bounded contrast rows under one shared review frame.
Base governing case = the primary source relation, pattern-governed case, or project work question that is already live before bounded comparative reading is added.
Reviewed source episteme/publication = the already pinned or otherwise reviewable episteme/publication being comparatively read; in plain terms, the already available source content under review.
Source anchors = sourceAnchorSet or sourceRefs that make the interpreted source episteme/publication inspectable.
Shared review frame = the review target, described situation, decision situation, release candidate, method family, control scope, problem frame, or source-set anchor that remains preserved while the comparison is made.
Compared alternative = one distinct option, method, bulletin, strategy, note, view, or source object kept separate under the shared review frame.
Same DescribedEntityRef case = the special case where the compared sources describe the same entity. This is common, but it is not required when distinct alternatives remain under one shared review frame.
Interpretive lift = the bounded comparative or asymmetry-bearing reading added on top of already available source epistemes/publications; in a small comparison sheet, each row has its own declared comparison basis while the unit keeps one shared unsupported downstream claim/effect and exit trigger.
Bridge anchor = required bridgeCardRef when the case depends on bridge-mediated correspondence rather than ordinary source reading alone; optional bridgeStanceRef may qualify that bridge only after the bridge card exists.
Allowed use = what this review unit may be used for while it remains only a bounded comparative review unit.
Misuse risk = how the review unit is most likely to be over-read into a bridge, action-selection, ontology, or authority claim that it does not carry.
Prompt exit = the explicit U.AbductivePrompt publication that takes over when abductive-prompt or action-selection pressure becomes live.
Ordinary minimum block = the smallest ordinary record that keeps the review unit honest for working use.
Load-bearing extension = the fuller declaration record used when the case sits close to bridge, explanation, abductive, ontology, or authority boundaries.

These terms are local review aids. They inherit the E.17:5.1e local-field rule: they do not create U.Kind, SurfaceKind, RelationKind, KindBridge, EvidenceKind, GateDecision, SpeechAct, Commitment, U.Work, authority source, publication face, or project source record unless another governing FPF pattern explicitly instantiates that object. They do not replace source notes, bridge cards, explanation renderings, prompt publications, or gate-bearing source forms. Their role is to keep a bounded comparative review unit readable without silently upgrading its authority.

Scope and exclusions

In scope

bounded comparative asymmetry over already declared reviewed source epistemes/publications;
reader-facing interpretive caution that stays source-tethered and preserves the shared review frame;
comparison of distinct alternatives under one shared review target, described situation, release candidate, method family, control scope, problem frame, or source-set anchor;
comparative review units that answer one explicit contrastive question without opening a rival action-selection search;
bounded user-fit when that fit only limits use rather than widening authority.

Out of scope

same-entity restatement, conservative rewrite, or representation shift whose main question stays with A.6.3, A.6.3.CR, or A.6.3.RT;
bridge-stance overlay that only clarifies an already-declared bridge stance over an existing Bridge Card (F.9.1);
explanation-face use discipline, admissibility, or added-link review on existing faces (E.17.EFP);
abductive-prompt or action-selection cases (B.5.2.0 / B.5.2);
ontology-facing reframing or changed described entity (OntologicalReframing / A.6.4);
policy, gate, adjudication, assurance, or work-facing use (A.15 / A.20 / A.21).

Working-fit test

Use this discipline only when all of the following hold:

the reviewed source episteme/publication is already pinned or otherwise reviewable;
the review unit adds one bounded comparative or interpretive lift, or a small set of bounded contrast rows with row-level comparison bases;
the case is still answering a bounded contrastive question rather than selecting an action path;
the shared review frame stays preserved, and compared alternatives remain distinct unless an explicit bridge/substitution source supports equivalence, substitution, or another named relation between them;
the main question is not already better described as same-entity viewing, bridge-stance overlay over an existing Bridge Card, or explanation-face use discipline.

If any of those fail, handle the live work under the neighboring FPF pattern or project source that actually governs it.

Nearest neighboring work

Name the base source relation or work question before adding bounded comparative reading. The nearest neighboring work questions should be separated in this order:

Same-entity rewrite or representation shift. If the project move is still mainly restatement, representation shift, or another same-entity viewing transform, keep it with A.6.3, A.6.3.CR, or A.6.3.RT.
Bridge-stance clarification. If the review unit only makes an already-declared bridge stance more legible, it stays subordinate to F.9.1.
Explanation-face use. If the main question is explanation class, face admissibility, or bounded connective prose on an existing face, it stays with E.17.EFP.
Abductive prompt or action-selection pressure. If open-question pressure or action-selection pursuit becomes live, bounded comparative reading ends and B.5.2.0 / B.5.2 governs that work.
Changed described entity or downstream authority. If continuity witnesses, changed target, or decision-bearing consequence are needed, the case has already left this discipline for OntologicalReframing, A.6.4, A.15, A.20, A.21, or another exact governing source.

Working-model first; plain questions first, ordinary minimum second, full declaration third

Most working users should not have to start with a long declaration block. This pattern therefore follows E.14's working-model-first discipline: the first usable block is a small set of plain questions that helps an engineer-manager keep the review unit bounded to the work it can honestly support. The opening of E.17.ID.CR:4.1 follows that same order by value: engineer-manager working use and governed-object distinction come first, and the compact ComparativeReading definition stays nearby as a recovery anchor rather than a gate before use. The ordinary minimum block comes next for ordinary use. The full declaration block remains available as a load-bearing assurance record.

Five plain working questions

The near-top quick working-fit check is the canonical first working block for this pattern. A working user should be able to answer these same five questions before touching the fuller blocks:

What already available source epistemes/publications am I comparing?
What single contrast or small set of contrast rows am I trying to make visible?
Am I still inside the same shared review frame, with compared alternatives kept distinct when they are distinct, or has the review target already shifted?
What unsupported downstream reading must the team not take from this review unit?
What would force this review unit to leave ComparativeReading for explanation, bridge work, prompt work, ontology work, or decision authority?

If these five answers are not visible, the case is not ready to stay here as a bounded comparative review unit.

Ordinary minimum block

For ordinary bounded comparative review units, it is usually enough that the unit or its surrounding review context keeps explicit:

what reviewed source episteme/publication is being interpreted;
where the source anchors live;
that the shared review frame remains preserved and that distinct alternatives remain distinct unless another source supports bridge/substitution;
what exact bounded comparative lift is being added, or which bounded contrast rows are included and what comparison basis each row uses;
what downstream claim/effect remains unsupported;
that the default worldContactPolicy here is review-only / non-executive;
and what governing-pattern exit becomes mandatory if the pressure intensifies.

If those minimum answers cannot stay stable across the same note, sheet, or review aid without sliding between reviewed source episteme/publication, governed unit, bounded lift, and outside work, stop here. Repair local lexical-head kind pressure through E.17.AUD.LHR (Local Head Restoration); if the whole review unit still has unstable described-entity or carried-move reading after that repair, move to E.17.AUD.OOTD (AuthoredUnit Primary Described-Entity Discipline) before adding more declaration weight.

Ordinary working card

An admissible ordinary comparative review unit should normally let a reader recover these seven rows without opening the heavier fuller declaration:

Row	Plain question	Minimum answer
Reviewed source	What already available source epistemes/publications are being compared?	one pinned source slice or one explicit source pair/set
Source anchors	Where can a reviewer inspect that source content?	visible `sourceAnchorSet` or nearby `sourceRefs`
Shared review frame / alternative identities	What review target, described situation, or source-set anchor is preserved, and what alternatives remain distinct under it?	preserved shared review frame; distinct alternatives are not treated as equivalent or substitutable without bridge support
Bounded lift row(s)	What single contrast or small row set is this unit making visible?	one declared `comparisonBasis` or a small set of row-level `comparisonBasis` statements under one shared unsupported downstream claim/effect and exit trigger
Unsupported downstream claim/effect	What is this unit not yet claiming?	no equivalence, prompt opening, ontology change, or decision authority
World-contact limit	What may the unit not be used to do?	`review-only / non-executive`
Exit trigger	What would end this pattern and require another governing pattern?	one explicit bridge, explanation, prompt, ontology, or authority trigger

This working card may live inline in the comparative review unit or in its immediate review context. Read it as the ordinary recovery anchor for the near-top working-fit check:

if rows 1-4 are still unstable because one pressured local lexical head or qualifier is doing too much work, stop and repair that local lexical-head pressure through E.17.AUD.LHR (Local Head Restoration) before you keep building the comparative review unit here;
if rows 3-7 cannot stay stable because the same review unit still has unstable reviewed-source, comparative-move, or outside-work reading after one honest local repair, move to E.17.AUD.OOTD (AuthoredUnit Primary Described-Entity Discipline);
if rows 1-7 stay recoverable over one pinned source slice or source pair, one preserved shared review frame, distinct alternatives where present, and one bounded contrast or small row set, ComparativeReading remains the honest primary governing pattern.

The nearest stay-here worked slices for this reading are E.17.ID.CR:5.4.5 through E.17.ID.CR:5.4.6.b. The nearest stop-and-reopen worked slice is E.17.ID.CR:5.4.6.c.

Move to the load-bearing extension only when one of the boundary, reader-fit, or misuse conditions in E.17.ID.CR:4.3.c becomes true. ComparativeReading remains primary only while those seven rows stay recoverable and the same review unit is still mainly about one bounded comparative reading, or a small set of bounded contrast rows, over already pinned source epistemes/publications. If the review unit first needs to restabilize what it is about, what move it carries, and what wider work remains outside, use E.17.AUD.OOTD (AuthoredUnit Primary Described-Entity Discipline) to stabilize that authored-unit question before adding more declaration weight here.

Load-bearing extension guidance

A fuller declaration record becomes warranted when:

reader-fit is doing real work;
misuse risk is high;
the review unit sits close to viewing, bridge, explanation, abductive, ontology, or downstream-authority boundaries;
mixed composition with A.6.3.* or E.17.EFP is load-bearing;
the authored unit still has unstable described-entity, carried-move, or outside-work reading after local repair;
or the case would otherwise be too easy to over-read as more committed than a bounded comparative review unit.

The load-bearing extension may inherit already-declared case ids, source pins, and provenance anchors instead of restating them inline. When recorded as a load-bearing review unit, that extension normally captures the ordinary minimum block plus any neighboring-pattern fields that remain load-bearing for the mixed case. Do not answer authored-unit instability by stacking more local fields onto the load-bearing extension. If E.17.AUD.LHR (Local Head Restoration) has already repaired the local lexical-head pressure and the same review unit still has unstable reviewed-source, governed-unit, comparative-move, or outside-work reading, stabilize that authored-unit question with E.17.AUD.OOTD (AuthoredUnit Primary Described-Entity Discipline) before deciding how much declaration weight should stay here.

Load-bearing declaration block

When the heavier declaration weight really stays here, the unit should still make at least these fields recoverable:

sourceSupportPosture using the shared E.17:5.1b vocabulary when the comparison depends on source pointer, source availability/retrieval, source use, source faithfulness, claim support, contradiction, omission, strengthening, added linkage, independent verification, admissible use, forbidden downstream use, or reopen trigger;
sourceAnchorSet or sourceRefs;
comparativeRelationPosture = sameEntityComparisonPosture | sharedFrameDistinctAlternativePosture | readerFitComparativePosture;
comparisonBasis;
addedClaimPolicy;
bridgeStanceVisibility;
required bridgeCardRef plus optional bridgeStanceRef when the case depends on bridge-mediated comparative posture;
targetUserModel when reader-fit is materially shaping the reading;
interactionMode when the review unit is not just one static comparative sentence;
contrastiveQuestion when the case is answering a specific contrast;
allowedUse;
misuseRisk;
promptWorthinessThreshold;
ontologyExitTrigger;
worldContactPolicy;
downstreamAuthorityLimit;
baseCasePattern when the review unit is a mixed case layered over A.6.3.* or E.17.EFP.

sourceSupportPosture is only source-support posture for the local claim/use. comparativeRelationPosture is only the comparative-relation posture of this review unit. Neither field is a RelationKind, KindBridge, Bridge Card, bridge support, bridge stance, semantic identity, equivalence, substitution, evidence relation, authority support, or decision support. The sameEntityComparisonPosture value is a special case for comparisons where the compared sources really describe the same entity; it does not assert semantic identity. When the unit compares distinct alternatives, use sharedFrameDistinctAlternativePosture plus distinct alternative refs, and do not treat the alternatives as equivalent or substitutable without bridge support. readerFitComparativePosture by itself does not open interpretation. Bounded correspondence wording that starts implying bridge support is bridge-mediated comparative posture: it requires an explicit bridgeCardRef, or the case exits to F.9 / F.9.1 before the comparison unit can carry that support. When cross-context bridge semantics are live, the actual bridge kind and Bridge Card remain owned by F.9. If bridge-mediated reading is live, bridgeCardRef is required and any bridgeStanceRef remains optional and subordinate. The main comparison question plus the neighboring pattern boundaries still decide the selected governing pattern or authority source.

Interpretant-side block

The interpretant-side fields above do not turn this zone into a full interactive explanation system or a dialog-management system. Their current role is narrower:

keep bounded comparative reading from pretending it is audience-neutral when it is not;
make the contrastive question, guided review mode, and allowed use visible;
and stop interpretation prose from quietly becoming prompt-bearing guidance, assurance shorthand, or policy pressure.

Static note versus interactive aid

Use two support levels.

Static comparative review note. A static note, sheet, or short review unit normally needs only the reviewed source episteme/publication set, source anchors, E.17:5.1b source-support posture when source support is disputed, comparison basis, bounded lift, unsupported downstream claim/effect, world-contact limit, and exit trigger. Do not import interactive-explanation vocabulary into this ordinary case.
Interactive comparative aid. Add targetUserModel, interactionMode, state/history needed for the live comparison, misuseRisk, and admissible-use boundary only when the aid is actually interactive, stateful, adaptive, or user-model-bearing. These fields still do not authorize prompt/action selection, gate use, work/reliance, or approval; they only keep the interactive comparative aid from being mistaken for audience-neutral static prose.

A comparative review unit may expose or cite source records being compared. It does not become those source records, a bridge card, a gate decision, or a work/reliance source by table layout, fluent contrast, side-by-side placement, or guided-review reuse. If required source support is missing, the repair/request/source-gap record is prospective only; it does not backdate source support into the earlier comparison.

Representation ontology and modeling lens (informative)

The early canonical lens for this pattern is already stated near the top: one comparative review unit over already available, source-pinned epistemes/publications, with the shared review frame preserved, one bounded contrast or small row set made visible, and unsupported downstream claim/effect kept outside.

This informative note only unpacks that same lens. It does not introduce a second one.

This pattern does not model interpretation in general. It models the ComparativeReading as the active governing pattern inside the broader InterpretationDiscipline family. In plain terms, the pattern governs the review unit itself. That unit may appear as a comparison note, comparison sheet, or guided review aid, but it is not the whole review process, it is not the source system, and it is not the hidden act of reading in the abstract. The bounded comparative reading is the interpretive lift carried by that review unit.

The minimum typed lens is a compact record of:

source anchors and source relation;
one declared source-relation posture;
one declared comparison basis and added-claim policy;
one allowed-use boundary, one misuse-risk line, and one worldContactPolicy that remains subordinate to A.20/A.21 when gate or adjudication pressure appears;
the relevant prompt, ontology, and authority exit triggers;
and which neighboring pattern still owns the base case when this remains a mixed overlay.

That lens is intentionally modest. It keeps the main read tied to the review unit and the problem-owning review domain, while leaving source, continuity, and exit discipline under whichever neighboring pattern still governs the base case. This pattern therefore does not create a rival bridge taxonomy, a rival base-case discipline, or an authority-bearing publication of its own.

Working read-out

A working reader should be able to say, in one short paragraph:

what reviewed source episteme/publication is being comparatively read;
what bounded interpretive lift is being added;
what shared review frame remains preserved, and, in the special same-described-entity case, why the same DescribedEntityRef remains preserved;
which higher-commitment neighboring pattern is still not yet active;
and what exit would become mandatory if the case were read as carrying a higher-commitment claim.

If that read-out becomes fuzzy, the review unit is no longer bounded enough to stay here and should weaken, clarify, or move to the governing neighboring pattern.

Branch-discipline summary

This section is the compact governing-rule summary for ComparativeReading inside the Core. It keeps the ComparativeReading governing rule recoverable for ordinary users and engineer-manager-first review. In mixed cases, the neighboring pattern discipline still remains primary where the base case really belongs to A.6.3.*, F.9.1, or E.17.EFP.

Use the fuller solution, exit table, worked slices, and relations section here when exact clause wording, full field set, or full reopen conditions matter. Keep this pattern to these summary rules.

Preserve the shared review frame. Keep the review target, described situation, decision situation, release candidate, method family, control scope, problem frame, or source-set anchor visible; keep distinct alternatives distinct unless bridge/substitution support exists elsewhere; keep source anchors and one declared comparison basis per contrast row visible; keep contrastiveQuestion explicit when it is doing real review work.
Keep the lift bounded and comparative. The review unit may add a bounded comparative or asymmetry-bearing reading, but it may not quietly intensify into higher-commitment theory, bridge licence, prompt-opening pressure, explanation governance, ontology shift, or downstream authority.
Name the base source relation or work question. If the main question is really same-entity rewrite, bridge-stance overlay over an existing Bridge Card, explanation-face work, prompt opening, ontology reframing, retargeting, or downstream authority, this pattern should not stay primary.
Keep higher-commitment neighboring patterns explicit. Bridge-mediated comparative posture still requires explicit bridgeCardRef; optional bridgeStanceRef may qualify only an existing bridge card. Prompt-worthy cases exit as U.AbductivePrompt; ontology pressure exits to OntologicalReframing or A.6.4; higher-commitment action, gate, or adjudication use exits to downstream authority patterns. If the primary question is weaker-source rendering rather than bounded comparison, move to A.6.3.CSC Controlled Semantic Coarsening.
Keep reader-fit bounded. targetUserModel, interactionMode, contrastiveQuestion, allowedUse, and misuseRisk may be stated when they are doing real work, but they do not authorize coaching, prompt/action selection, policy guidance, or an authority claim that the unit does not carry.

Neighboring-work boundary glance

This table is a compact boundary aid for separating the comparative review unit from neighboring project work and source requirements. For a fuller mixed-case read, read this table together with the neighboring pattern discipline.

If the case is really doing this...	It should stay / move here...
one local lexical head or qualifier is still doing too much work, but one honest repair would stabilize the same unit	`E.17.AUD.LHR` (`Local Head Restoration`)
the same note is mostly rewriting, reframing, or re-rendering the same thing with no bounded comparative lift	`A.6.3` / `A.6.3.CR` / `A.6.3.RT`
the real job is only to make an already-declared bridge stance explicit over an existing Bridge Card	`F.9.1`
the note is primarily a weaker source-pinned rendering with narrower-use, unsupported downstream use, and fuller-source reopen discipline	`A.6.3.CSC Controlled Semantic Coarsening`
one review unit already keeps the same object, one bounded comparison, and one outside-work boundary stable	`ComparativeReading` within `InterpretationDiscipline`
the same unit still has unstable reviewed-source, comparative-move, or outside-work reading after local repair	`E.17.AUD.OOTD` (`AuthoredUnit Primary Described-Entity Discipline`)
the real job is explanation-face governance on existing faces	`E.17.EFP`
the comparison is now opening an abductive prompt or action-selection question	`B.5.2.0 / B.5.2`
the target or ontology is changing and now needs continuity witnesses	`OntologicalReframing` / `A.6.4`
the unit is now being used for execution, gate, or adjudication consequence	`A.15 / A.20 / A.21`

For first-minute use, read the four boundary rows around the comparative-reading case itself as a compact mirror of the near-top working-fit check and the ordinary working card:

pressured local lexical head -> E.17.AUD.LHR (Local Head Restoration);
stable same-object comparative review unit -> stay with ComparativeReading;
same unit still unstable after local repair -> E.17.AUD.OOTD (AuthoredUnit Primary Described-Entity Discipline);
higher-commitment neighboring pattern already primary -> move out of this pattern. If the comparison unit is already carrying neighboring work, use the boundary rows first and then read E.17.ID.CR:5.4.7 through E.17.ID.CR:5.4.10 as the nearest worked boundary examples.

Ordinary working order for the card

The shortest ordinary working order is:

name the base source relation or work question if the case is mixed;
pin the reviewed source episteme/publication and make the shared review frame plus any distinct alternatives visible;
state the bounded comparative lift, or the small set of contrast rows and their row-level comparison bases, in compact form;
declare the unsupported downstream claim/effect and the review-only / non-executive world-contact limit;
name the exit trigger that would end interpretation.

That five-step order is not a second ordinary working card, and it is not a canonical review process. It is only one local working aid for this pattern. It is the shortest way to recover the seven-row ordinary working card in E.17.ID.CR:4.3.b.a. In ordinary use, publish the resulting seven-row card in compact form rather than a heavier load-bearing declaration block whenever boundary pressure still stays low. If the seven-row working card still cannot be completed plainly through that order, the review unit is not yet ready to stay here. If the note, sheet, or review aid first has to answer what it is about, what move it is carrying, and what wider work remains outside, stabilize that authored-unit question with E.17.AUD.OOTD (AuthoredUnit Primary Described-Entity Discipline) before continuing comparative-reading work.

Archetypal grounding

Worked-slice status. Read the system case, episteme case, and boundary-bank cases as a heterogeneous example bank, not as one recommended progression. They show different admissible outcomes for the same governing pattern: some cases stay small and stop, some stay mixed with a neighboring pattern, and some reopen or move to another governing pattern when outside observations, environmental change, or downstream constraints change what the comparative review unit can honestly carry.

Tell

ComparativeReading names the bounded middle band where a team needs to prepare one explicit comparative reading over already anchored source epistemes/publications without yet opening prompt/action-selection work, ontology-facing reframing, or downstream authority use. The governed object is the comparative review unit. That review unit must stay modest enough that a reviewer can still see the same DescribedEntityRef, the declared comparison basis, the unsupported downstream claim/effect, and the exit trigger that would end interpretation.

Show (System)

Source slice. Two pinned operating notes describe the same service episode from different operational responsibilities. One note is anchored in the maintenance log, the other in the continuity dashboard for the same declared episode and the same DescribedEntityRef.

Comparative review unit. Under the declared comparison basis, the maintenance note foregrounds operator-induced variance, while the continuity note foregrounds buffer-sensitive drift; each view exposes a blind spot in the other without granting direct substitution.

Why this stays here.

source relation and source anchors are explicit;
the same DescribedEntityRef remains preserved;
one bounded comparative lift is added;
no substitution licence is added;
no rival action-selection question is yet being asked.

Show (Episteme)

Source slice. Two pinned analytic renderings over the same evidence set are already available for review. One rendering is a SourceLinkedExplanationReconstruction on a TechCard face; the other is a compact comparison sheet that preserves the same evidence set and the same described operational episode.

Comparative review unit. For maintenance reviewers, the reconstruction foregrounds operator load more than the comparison sheet, while the comparison sheet foregrounds recovery sequencing more than the reconstruction; this difference is useful for review, but it is not yet a design recommendation or an action-selection claim.

Why this stays here.

the base-case governing patterns remain identifiable;
the comparative lift is explicit and bounded to one reviewer task;
explanation-face governance and same-entity transform discipline remain with their neighboring patterns;
downstream authority and prompt-bearing action-selection pressure remain negative.

Boundary bank

Lower-boundary bridge-stance overlay case

Bridge-stance overlay unit. The existing Bridge Card relates the local maintenance-pressure term to the partner continuity term; this overlay says the relation should be read as asymmetry-explicating rather than substitution-friendly.

Why it stays under F.9.1:

the bridge stance is already declared;
the review unit only makes that stance more legible;
no bounded interpretive lift beyond the bridge-stance overlay is added.

Mixed primary-pattern composition with A.6.3.RT

Base-case rendering. A same-entity comparison sheet retabulates one pinned incident note into columns for trigger, pressure, and recovery.

Comparative review unit. In the retabulated view, the recovery column makes the operator-induced asymmetry easier to inspect than the trigger column, but the table should not be read as establishing a new causal hierarchy.

Why this remains mixed rather than collapsing:

A.6.3.RT still owns the base representation shift;
bounded comparative reading is secondary and only adds a bounded comparative lift;
strongest forbidden-use constraint wins, so no new ontology or gate reading is licensed.

Mixed primary-pattern composition with E.17.EFP

Base-case rendering. A TechCard-face explanation rendering is already classified as SourceLinkedExplanationReconstruction and publishes a bounded connective policy.

Comparative review unit. For maintenance reviewers, this rendering foregrounds the difference between operator load and throughput pressure more than the original prose, but it should not be read as a higher-commitment design-level recommendation.

Why this stays mixed rather than collapsing:

E.17.EFP still owns explanation class and face admissibility;
bounded comparative reading only adds bounded comparative use for one reviewer task;
the review unit still does not own explanation-face governance or downstream authority.

Guided review aid with bounded interaction mode

Source slice. A reviewer UI presents two already pinned source notes side by side for the same described operational episode.

Guided comparative review unit. Question: which note foregrounds variance introduced by operator timing rather than environmental drift? Allowed use: bounded comparative triage only. Misuse risk: do not treat this aid as action selection or release guidance.

Why it stays here:

the interaction mode is explicit but still bounded;
the review unit answers one contrastive question rather than opening prompt/action pursuit;
allowed use and misuse risk are visible instead of being smuggled into interface tone.

Product and design-review comparison case

Source slice. Two already available design-review notes describe the same integration boundary for the same planned release. One note foregrounds coupling and rollback pressure; the other foregrounds delivery simplicity and lower immediate implementation cost.

Comparative review unit. For architecture review, the first note foregrounds coupling risk more than the second, while the second foregrounds delivery speed more than the first; that asymmetry is useful for discussion, but it is not yet a recommendation to choose either option.

Working-boundary reading. This is the ordinary stay-here case: one honest local repair and one authored-unit check would already leave the review unit stable enough that the bounded comparative review move itself stays primary.

Why it stays here:

the same planned release remains the DescribedEntityRef;
one bounded comparative lift is made explicit for a declared review task;
the unit supports design discussion without quietly becoming action selection or approval.

Compliance and release-review comparison case

Source slice. An internal control checklist and a vendor compliance bulletin are already available for the same release candidate and the same declared control scope.

Comparative review unit. For release review, the vendor bulletin foregrounds protocol conformance more than rollback evidence, while the internal checklist foregrounds rollback evidence more than protocol conformance; this comparison helps frame the review, but it is not yet a release gate or equivalence claim.

Working-boundary reading. This is the same stay-here case under a release/compliance load: the comparison unit is already stable enough, so the primary question is the bounded contrast rather than local repair or authored-unit stabilization.

Why it stays here:

the comparison basis is explicit and bounded to one review task;
the source anchors remain visible and the same release candidate stays in view;
the review unit helps an engineer-manager see a review asymmetry without laundering gate authority.

Research-review comparison case

Source slice. Two already available research syntheses discuss the same measured phenomenon and the same declared evidence slice. One synthesis foregrounds variance decomposition limits more; the other foregrounds protocol repeatability more.

Comparative review unit. For method review, the first synthesis foregrounds uncertainty-handling limits more than the second, while the second foregrounds repeatability support more than the first; this asymmetry helps frame the discussion, but it is not yet a method choice or a claim that one synthesis is globally better.

Why it stays here:

the same measured phenomenon remains the DescribedEntityRef;
the comparative lift is bounded to one review task;
the unit supports research discussion without quietly becoming action selection or ontological reframing.

Program and cultural-review comparison case

Source slice. Two already available programme briefs discuss the same continuing initiative and the same declared participation scope. One foregrounds continuity of community engagement more; the other foregrounds short-term event visibility more.

Comparative review unit. For programme review, the first brief foregrounds participation continuity more than the second, while the second foregrounds short-term visibility more than the first; this comparison helps frame the discussion, but it is not yet a funding, curation, or programme-direction decision.

Why it stays here:

the same initiative remains the DescribedEntityRef;
the comparison basis is explicit for one declared review task;
the unit supports programme discussion without laundering decision authority.

Exogenous-change stop-and-reopen case

Source slice. An internal release-review comparison sheet already compares one control checklist and one vendor bulletin for the same declared release candidate and the same control scope. Mid-review, an external incident bulletin arrives and changes the live rollback assumptions for that same candidate.

Initial comparative review unit. Before the new bulletin, the vendor bulletin foregrounds protocol conformance more than rollback evidence, while the internal checklist foregrounds rollback evidence more than protocol conformance; this comparison frames the review, but it is not yet a release gate or equivalence claim.

Working-boundary follow-through. This case begins on the same admissible stay-here case as E.17.ID.CR:5.4.6, but outside observation then changes the declared comparison basis, so the unit must stop and reopen instead of being carried forward by inertia.

Why this must stop and reopen.

the new outside observation changes the declared comparison basis;
the previous bounded comparison may remain traceable, but it cannot continue by inertia as if the same live review conditions still held;
the admissible next move is either to restate a fresh comparative review unit over the new declared basis or to move to a neighboring governing pattern if downstream gate or authority question has now become primary.

Lighter comparison note with source-return discipline

Source episteme/publication set. A release team already has the full internal rollback worksheet, vendor bulletin, and incident-note bundle for one release candidate. A short comparison note is then prepared for the daily review stand-up.

Comparative review unit. For today's review, the vendor bulletin foregrounds protocol conformance more than rollback evidence, while the internal rollback worksheet foregrounds rollback evidence more than protocol conformance; this short note is only a review aid over the same release candidate, and the full source episteme/publication set remains primary for any bridge, release, coarsening, or work/reliance reading.

Why it still stays here:

the governed object is still one bounded comparative review unit, not a replacement for the source episteme/publication set;
the note remains source-pinned through the already available source episteme/publication set and openly forbids bridge, gate, or work/reliance use that it does not carry;
any attempt to treat the short note as enough for equivalence, release approval, execution pressure, or a weaker-use source substitute forces fuller-source return, A.6.3.CSC Controlled Semantic Coarsening, or another neighboring-pattern exit.

Functional versus constructive-description comparison

Source slice. A functional-description publication and a constructive/product-description publication describe the same pumping skid. The functional description foregrounds flow relation and method-selection support; the constructive description foregrounds module composition and installed equipment.

Comparative review unit. For design review, the functional description foregrounds what the skid is supposed to do in the declared flow relation, while the constructive description foregrounds what parts are present. This contrast helps the engineer keep function and construction separate, but it is not a module-equivalence claim, a performed-work record, or a gate decision.

Why it stays here:

both source publications remain anchored and inspectable;
the same pumping skid remains the DescribedEntityRef;
the bounded comparative lift is the function-versus-construction contrast for one review task;
module equivalence, work occurrence, evidence, and gate claims remain unsupported downstream uses.

Method-option comparison without method choice

Source slice. Two method descriptions are already pinned for the same fabrication task. One foregrounds lower setup cost; the other foregrounds tighter result-measurement discipline.

Comparative review unit. For method review, method M-1 foregrounds lower setup cost more, while method M-2 foregrounds result-measurement discipline more. This comparison helps prepare method discussion, but it is not yet the selected method, not a work plan, and not evidence that either method has been performed.

Why it stays here:

the reviewed source epistemes are pinned;
the comparison basis is explicit;
no selected-method, work-plan, performed-work, evidence, or engineering-justification claim is added;
if the team chooses a method or prepares a work plan, record the selected method or work plan as project method/plan/work material governed by A.15.

Nearest neighboring-work examples. The next four cases are the nearest worked boundaries for prompt pressure, same-entity viewing, ontology shift, and gate or authority misuse. Use them when the near-top negative-boundary rows fit and you need one worked cue for keeping the comparison unit from carrying outside work.

Upper-boundary prompt-bearing exit case

Prompt-bearing review unit. This contrast raises the question whether both systems are being constrained by the same hidden gating variable, so we should open a prompt around that shared control possibility.

Why it exits:

abductive-prompt or action-selection pressure has become live;
the review unit is now prompt-bearing rather than only interpretive;
the selected governing target is B.5.2.0 / B.5.2 through explicit U.AbductivePrompt exit.

Same-entity viewing boundary case

Viewing rendering. The source note is retabulated into a compact comparison sheet that preserves the same claims and entity but makes pressure, trigger, and recovery fields easier to inspect.

Why it does not enter interpretation:

the main question is representational reshaping rather than comparative reading;
no bounded asymmetry or interpretive claim is added;
the more precise governing pattern is A.6.3.RT.

Ontology-exit anti-case

Ontology-pressuring review unit. The older maintenance note and the new field-observation note are best read as two observational cuts over the same latent failure mode, so we should recast both under a new operational kind and treat the source labels as legacy labels.

Why it exits:

the case is now asking for a higher-commitment same-referent / new-intension reading;
continuity witnesses would now be needed;
bounded comparative reading is no longer enough, so the case exits toward OntologicalReframing.

Authority and gate misuse anti-case

Authority-pressuring review unit. Because this comparison consistently foregrounds the safer operating posture, reviewers may use the review unit directly as a release gate and do not need the underlying source episteme/publication during triage.

Why it exits:

the review unit is being over-read as gate-facing authority;
the bounded comparative reading has become a substitute for the fuller source episteme/publication;
the selected governing target moves toward downstream authority patterns rather than staying in interpretation.

Invalid publication and repair example

Invalid review unit. These two views are basically the same thing for current operations, so the team can use whichever wording is easier.

Why it is invalid here:

no source anchors are visible;
bridge-mediated comparison is being implied without explicit bridge declaration;
unsupported substitution and authority claims are being smuggled in through soft phrasing.

Minimal repair. Under bridge card BC-12 and the stated comparison basis, both notes foreground the same operator-timing concern for this review task, but they are not substitution-equivalent and the source episteme/publication set remains primary.

What the repair does:

restores the source and bridge anchors;
weakens the claim back to bounded comparative reading;
reasserts the unsupported downstream claim/effect.

Bias-Annotation

Lenses tested: Gov, Arch, Onto/Epist, Prag, Did. Scope: bounded comparative review units governed under the ComparativeReading governing pattern inside InterpretationDiscipline, not a universal claim about all review or publication forms.

This pattern intentionally biases toward bounded comparative reading and away from hidden bridge inflation, explanation laundering, ontology shift, action-selection pressure, or downstream-authority inflation. The main mitigations are explicit primary-governing-pattern naming, visible source anchors, explicit interpretant-side boundedness, explicit unsupported downstream claim/effect, explicit governed-object surfacing, and hard boundaries to bridge, abductive, ontology, retargeting, and downstream-authority patterns. Under the governance lens, the pattern is deliberately conservative: it helps a user prepare or review a bounded comparative review unit without letting that unit quietly become policy, assurance, gate, or action authority.

Conformance Checklist

A conformance check is retained only if it changes the next admissible use of the comparative review unit, blocks a concrete overclaim, or preserves a source/reopen path needed for the declared supported use.

Use ID.CR-Core for ordinary comparison notes. Conditional rows open only when the note touches neighboring-pattern relation, bridge declaration, or reader-fit fields. For fuller mixed-case read, read this checklist together with the neighboring pattern discipline and the exit boundaries gathered in this section.

Assurance recovery note. Read this checklist as a heavier read-back of the already-declared ComparativeReading governing rule, not as a second rule list. If a row cannot be recovered through the ordinary seven-row card, the nearest worked slices, or the practical safeguards already named in the pattern, the case is not yet stable enough to rely on checklist prose alone.

ID.CR-Core ordinary checks

CC-ID-1 - Governed object is explicit. The pattern makes clear that the governed object is a comparative review unit rather than the whole review or decision work or a hidden mental act.
CC-ID-2 - Source anchors and comparison basis are explicit. A reviewer can see what already-fixed source episteme/publication is being read and what declared comparison basis or contrast is carrying the lift.
CC-ID-3 - The lift stays bounded. The pattern keeps the comparative lift visibly weaker than bridge licence, explanation governance, prompt opening, ontology shift, or authority-bearing guidance.
CC-ID-6 - Stronger exits stay visible. Prompt-worthiness, ontology pressure, or downstream authority pressure leads to an explicit governing-pattern exit rather than staying hidden inside comparative prose.
CC-ID-8 - The review unit does not over-claim authority. The unit is still review-only / non-executive and does not present itself as substitution licence, gate guidance, or action authority.

ID.CR-Conditional checks

CC-ID-4 - Base-case governing-pattern relation is explicit. A reviewer can tell why the case does not really belong to A.6.3.*, F.9.1, E.17.EFP, B.5.2(.0), OntologicalReframing, or A.6.4.
CC-ID-5 - Bridge declaration does not hide. If bridge-mediated comparative posture is live, bridgeCardRef is required; optional bridgeStanceRef remains visible and subordinate to that existing bridge card.
CC-ID-7 - Reader-fit stays bounded. targetUserModel, interactionMode, contrastiveQuestion, allowedUse, and misuseRisk are visible when needed, but they do not open an authority claim that the unit does not carry.

Checklist recovery map. If an assurance-side reader needs to cash one checklist row out by value, use the nearest ordinary card row and worked recovery below before treating the checklist as self-sufficient:

Checklist row	Recover through first	Nearest worked or practical recovery
`CC-ID-1`	`E.17.ID.CR:4.3.b.a` rows Reviewed source and Shared review frame / alternative identities	`E.17.ID.CR:5.4.5`, `E.17.ID.CR:5.4.6`, `E.17.ID.CR:5.4.6.a`
`CC-ID-2`	`E.17.ID.CR:4.3.b.a` rows Reviewed source, Source anchors, and Bounded lift	`E.17.ID.CR:5.4.5`, `E.17.ID.CR:5.4.6`, `E.17.ID.CR:5.4.6.a`
`CC-ID-3`	`E.17.ID.CR:4.3.b.a` rows Bounded lift, Unsupported downstream claim/effect, and World-contact limit	`E.17.ID.CR:5.4.6`, `E.17.ID.CR:5.4.10`, `E.17.ID.CR:5.4.11`
`CC-ID-4`	near-top Neighboring-work boundary, Quick working-fit check, and `E.17.ID.CR:4.5 - Neighboring-work boundary glance`	`E.17.ID.CR:5.4.7` through `E.17.ID.CR:5.4.10`
`CC-ID-5`	`E.17.ID.CR:4.3.d` bridge-declaration fields plus `E.17.ID.CR:4.2` neighboring patterns	`E.17.ID.CR:5.4.1`, `E.17.ID.CR:5.4.2`, `E.17.ID.CR:5.4.3`
`CC-ID-6`	`E.17.ID.CR:4.3.b.a` row Exit trigger plus the near-top exit corridor	`E.17.ID.CR:5.4.7` through `E.17.ID.CR:5.4.10`
`CC-ID-7`	`E.17.ID.CR:4.3.d` interpretant-side fields, kept subordinate to the ordinary card and unsupported downstream claim/effect	`E.17.ID.CR:5.4.4`, `E.17.ID.CR:5.4.6`, `E.17.ID.CR:5.4.6.b`
`CC-ID-8`	`E.17.ID.CR:4.3.b.a` rows Unsupported downstream claim/effect and World-contact limit	`E.17.ID.CR:5.4.6`, `E.17.ID.CR:5.4.10`, `E.17.ID.CR:5.4.11`

Common Anti-Patterns and How to Avoid Them

Anti-pattern	Why it is wrong	How to avoid it
Governed-object instability	The text sounds as if it governs a note in one section, a publication artifact in another, a reading move in a third, and a whole review process in a fourth.	Stabilise one governed object early and keep note/sheet/UI/rendering labels explicit as ordinary forms of that object rather than stylistic substitutes.
Bridge gloss inflation	A helpful comparative sentence starts acting like a bridge licence the declared bridge card and stance do not allow.	Keep bridge-mediated comparative posture tied to required `bridgeCardRef`; use optional `bridgeStanceRef` only as a subordinate overlay under `F.9.1`.
Soft prompt smuggling	The review unit is really opening a question or action-selection case, but hides it in gentle prose.	If prompt/action-selection pressure becomes live, publish `U.AbductivePrompt` with explicit `promptSpecies`, `openQuestion`, and cue or action-selection provenance instead of keeping it here.
Viewing capture	Same-entity restatement or representation-shift work is pulled into interpretation just because the result is more readable.	Name the base source relation or representation work first and use comparative reading only when bounded comparative lift is primary.
Explanation-face laundering	Interpretation language is used to avoid explicit `E.17.EFP` class and admissibility review.	If face class or bounded connective prose is primary, stay with `E.17.EFP`.
Gentle-tone advisory overread	A calm explanatory tone makes work/reliance, assurance, or gate guidance sound harmless.	Publish `allowedUse`, `misuseRisk`, `worldContactPolicy`, and `downstreamAuthorityLimit` explicitly.
Described-entity shift	A changed target is mislabeled as interpretation because the prose still sounds comparative.	Exit to `OntologicalReframing` or `A.6.4` once continuity witnesses or changed target become load-bearing.
Interface neutrality fiction	A guided or contrastive aid pretends to be audience-neutral while steering unsupported downstream use.	Make `targetUserModel`, `interactionMode`, and `contrastiveQuestion` explicit and keep the unsupported use forbidden.

Consequences

The middle band between bridge-stance overlay over an existing Bridge Card and prompt-bearing abduction becomes reviewable rather than rhetorical.
Reviewers get a cleaner way to distinguish comparative interpretation from same-entity viewing, explanation rendering, ontology shift, and downstream authority.
Authors pay a small extra declaration weight, but the gain is fewer hidden neighboring-pattern boundary mistakes and less governed-object instability.
Guided comparative review units become easier to prepare honestly because allowed use, misuse risk, and world-contact limits can be declared without pretending that the unit already carries a broader guidance claim than it really does.
Users get an admissible way to keep bounded comparative review units modest: the unit can stay useful while its reading pressure remains below the exit threshold for prompt publication, ontology-facing reframing, or gate-facing guidance.

Rationale

Teams already write small comparative review units, often as comparison notes or sheets, to move a review forward. What they usually lack is a disciplined way to keep that unit useful without letting it silently become an equivalence claim, a hidden hypothesis, a redesign push, or a release decision.

This pattern exists to protect that everyday review move. It keeps a comparative review unit usable by making five things visible enough to inspect: the governed object, the source anchors, the bounded comparative lift, the unsupported downstream claim/effect, and the exit trigger that would end interpretation. The gain is practical: a team can compare available source epistemes/publications honestly without pretending that a helpful review unit already carries more authority than it really does.

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. Assurance recovery note. Read each row here as a heavier confirmation of one already-declared ComparativeReading governing rule. If a row cannot be recovered through the ordinary card, the interpretant-side block, the quick exit corridor, or the nearest worked slices, do not let the citation carry the pattern by itself.

Traditions covered. This pattern binds itself to architecture-description governance, explainable-AI review discipline, and interactive explanation-system practice. These rows are selected because they discipline recurrent review work in the problem-owning domains named in the case bank; they are not a decorative literature collage added after the governing pattern was chosen.

Claim need	Source idea / current source	Current source locus	Local FPF invariant / practical local test	Nearest recovery anchor	Adopted/adapted invariant / rejected shortcut
Comparative review units should stay tied to explicit source, view, and review structure rather than shifting through helpful prose alone.	Architecture-description practice treats views, viewpoints, and comparison units as explicit review objects rather than letting reader-help prose replace structural review.	ISO/IEC/IEEE 42010:2022; source maturity = mature standard	This pattern adopts explicit source anchors, declared comparison basis, and explicit exit rules instead of letting comparative fluency define the case.	`E.17.ID.CR:4.3.b.a` rows Reviewed source, Source anchors, and Bounded lift; `E.17.ID.CR:5.4.5`, `E.17.ID.CR:5.4.6`, `E.17.ID.CR:5.4.6.a`	Adopt.
Interpretation and explanation support are use-sensitive and bounded by reader role and knowledge limits rather than audience-neutral by default.	Explainable-AI guidance distinguishes explanation, meaningfulness for intended users, explanation accuracy, and knowledge limits instead of treating all supportive prose as equally safe.	Phillips et al. (2021), NIST IR 8312, Four Principles of Explainable Artificial Intelligence; source maturity = current government guidance	This pattern adapts that stance into `targetUserModel`, `interactionMode`, `contrastiveQuestion`, `allowedUse`, and `misuseRisk`, while still keeping explanation-face use discipline with `E.17.EFP`.	`E.17.ID.CR:4.3.d` interpretant-side block, kept subordinate to the ordinary card; `E.17.ID.CR:5.4.4`, `E.17.ID.CR:5.4.6`, `E.17.ID.CR:5.4.6.b`	Adopt/Adapt.
Static comparative notes and interactive comparative aids must not carry the same support load.	Static review notes need source anchors, comparison basis, bounded lift, unsupported downstream claim/effect, and exit; interactive explanation-system practice becomes relevant only when the aid is actually interactive, stateful, adaptive, or user-model-bearing.	Labarta et al. (2026), X-SYS: A Reference Architecture for Interactive Explanation Systems, arXiv:2602.12748v3; source maturity = emerging preprint, not settled standard.	This pattern keeps the ordinary seven-row card sufficient for static notes and adds `targetUserModel`, `interactionMode`, state/history, `misuseRisk`, and admissible-use boundary only for actual interactive comparative aids.	`E.17.ID.CR:4.3.b.a` ordinary card; `E.17.ID.CR:4.3.f` static/interactive split; `E.17.ID.CR:5.4.4`, `E.17.ID.CR:5.4.7`	Adapt conditionally. Reject importing XAI architecture into ordinary static notes.
Faithful support is not the same as merely plausible or persuasive prose.	Current interpretation research distinguishes faithful support from attractive but weakly grounded narrative, especially in explanation-like publication.	Jacovi and Goldberg (2020), Towards Faithfully Interpretable NLP Systems; source maturity = research paper supporting evaluation posture	This pattern adopts explicit source anchors, `E.17:5.1b` source-support posture when live, unsupported downstream claim/effect, and bridge-claim visibility so that bounded comparative reading is not over-read as semantic authority it does not carry.	`E.17.ID.CR:4.3.b.a` rows Unsupported downstream claim/effect and World-contact limit; `E.17.ID.CR:5.4.6`, `E.17.ID.CR:5.4.9`, `E.17.ID.CR:5.4.10`, `E.17.ID.CR:5.4.11`	Adopt.

Row 1. The ISO row matters because this pattern is governing reviewable comparative units, not free comparative commentary. The pattern adopts the explicit-structure lesson directly: comparison basis, source anchors, and exit rules must stay visible enough that a reviewer is not forced to infer the real comparison question from tone alone. Ordinary recovery: read the Reviewed source, Source anchors, and Bounded lift rows together before leaning on the citation. Engineer-manager payoff: a comparison note can help a review meeting move faster without being mistaken for a free-form equivalence judgement. Case linkage: see E.17.ID.CR:5.4.5, E.17.ID.CR:5.4.6, and E.17.ID.CR:5.4.6.a.

Row 2. The NIST row matters because this pattern is not really audience-neutral even when the review unit looks small. The pattern therefore adapts user-meaningfulness and knowledge-limit practice into explicit interpretant-side fields, while rejecting any move that would let those fields replace source or pattern discipline. Assurance recovery: keep those fields subordinate to the ordinary card and unsupported downstream claim/effect rather than letting them stand alone. Engineer-manager payoff: the note can be written for a real audience and task without pretending it is safe for every audience and every downstream use. Case linkage: see E.17.ID.CR:5.4.4, E.17.ID.CR:5.4.6, and E.17.ID.CR:5.4.6.b.

Row 3. The interactive-system row matters because bounded comparative aids can become more directive than static prose without crossing into a full new governed pattern of their own. The pattern adapts only the minimal architectural lesson it needs: if interaction mode is load-bearing, that fact must be explicit and must still stop before prompt, ontology, or authority escalation. Assurance recovery: read that pressure through the interaction fields plus the prompt and authority exit rows rather than treating the source citation as a licence for higher-commitment guidance. Engineer-manager payoff: a guided comparative UI can stay useful for review without silently becoming coaching, prompt/action selection, or approval machinery. Case linkage: see E.17.ID.CR:5.4.4 and E.17.ID.CR:5.4.7.

Row 4. The faithfulness row matters because a comparative review unit can sound careful while still smuggling bridge, prompt, or authority claims. The pattern adopts the demand for explicit grounding, but rejects any shortcut where plausible comparative prose is treated as if it were already a semantic or operational licence. Ordinary recovery: use the Unsupported downstream claim/effect and World-contact limit rows before letting polished prose win the argument by tone. Engineer-manager payoff: polished prose is no longer enough to overrule the underlying source episteme/publication set or to sneak in a decision claim. Case linkage: see E.17.ID.CR:5.4.6, E.17.ID.CR:5.4.9, E.17.ID.CR:5.4.10, and E.17.ID.CR:5.4.11.

Relations

Naming-level family: InterpretationDiscipline names the wider interpretation family for this governing pattern.
Governing pattern: ComparativeReading over comparative review units.
Inherited dynamic frame: C.2.2a and A.16.0, where what moves is a lineage of successive governed U.Episteme publications over U.CharacteristicSpace.
Governed-unit / carrier reading: the comparative review unit is one working review unit that may be carried by an admissible PublicationSurface over that inherited frame; it is not the moving lineage itself, not a carrier, and not the whole review or decision work.
Builds on: C.2.2a, A.16.0, F.9, F.9.1, Part F / A.6.9, and E.14.
Mixed-case dependency rule: in mixed cases, this pattern stays subordinate to whichever neighboring pattern still governs the base case (A.6.3.*, F.9 / F.9.1, Part F / A.6.9, or E.17.EFP), including that pattern's source, continuity, bridge, wording-repair, and exit constraints.
Primary rule here: this section carries the summary, checklist, worked slices, and boundary block for ComparativeReading; mixed-case neighboring pattern rule remains primary where the base case still belongs elsewhere.
Repair-only neighbors when local instability is real: use E.17.AUD.LHR (Local Head Restoration) when lexical-head kind or qualifier pressure is still local; use E.17.AUD.OOTD (AuthoredUnit Primary Described-Entity Discipline) when the same review unit still has unstable reviewed-source, governed-unit, comparative-move, or outside-work reading after local repair. These neighboring patterns are not always-on prerequisites for ordinary ComparativeReading use.
Coordinates with: A.6.3, A.6.3.CR, A.6.3.RT, A.6.3.CSC, F.9, F.9.1, Part F / A.6.9, E.17.EFP, B.5.2.0, B.5.2, OntologicalReframing, A.6.4, A.15, A.15.4, A.20, A.21.
Nearest neighboring FPF patterns for outside work: A.6.3.*, F.9 / F.9.1, Part F / A.6.9, E.17.EFP, and B.5.2.0 / B.5.2.
Main exits: sameness, equivalence, alignment, mapping, substitutability, interchangeability, or attribute/entity/profile matching across contexts exits to Part F / A.6.9 and, when bridge support is live, F.9 / F.9.1; abductive-prompt pressure exits to B.5.2.0 / B.5.2; ontology and changed-target pressure exit to OntologicalReframing or A.6.4; downstream work/reliance, gate, assurance, and adjudication pressure exit to A.15.4, A.15, A.20, or A.21.
Boundary notes: same-entity transform rule stays with A.6.3.*; bridge-stance overlay stays with F.9.1 over an existing F.9 Bridge Card; "same / equivalent / align / map" wording repair and attribute/entity/profile mismatch repair stay with Part F / A.6.9; explanation-face governance stays with E.17.EFP; weaker source-pinned renderings with narrower-use / forbidden-use / reopen discipline move to A.6.3.CSC Controlled Semantic Coarsening; bounded comparative reading does not by itself authorize downstream use it does not carry.
Non-goal: this pattern does not create a rival authority-bearing publication, a rival bridge taxonomy, a rival sameness/equivalence repair pattern, or a rival base-case discipline of its own.

E.17.ID.CR:End

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

#ComparativeReading - bounded comparative reading over comparative review units

#About this pattern

#How to use this pattern

#Keywords

#Relations

#Content

#Problem frame

#Problem

#Forces

#Solution - comparative review units with bounded comparative reading, escalation, and exit rules

#Engineer-manager-first working use, governed-object distinction, and compact branch definition

#Engineer-manager-first use

#Pattern, case, and governed-object distinction

#Compact branch definition

#Why the comparative-reading branch needs its own discipline

#Local working vocabulary

#Scope and exclusions

#Working-fit test

#Nearest neighboring work

#Working-model first; plain questions first, ordinary minimum second, full declaration third

#Five plain working questions

#Ordinary minimum block

#Ordinary working card

#Load-bearing extension guidance

#Load-bearing declaration block

#Interpretant-side block

#Static note versus interactive aid

#Representation ontology and modeling lens (informative)

#Working read-out

#Branch-discipline summary

#Neighboring-work boundary glance

#Ordinary working order for the card

#Archetypal grounding

#Tell

#Show (System)

#Show (Episteme)

#Boundary bank

#Lower-boundary bridge-stance overlay case

#Mixed primary-pattern composition with A.6.3.RT

#Mixed primary-pattern composition with E.17.EFP

#Guided review aid with bounded interaction mode

#Product and design-review comparison case

#Compliance and release-review comparison case

#Research-review comparison case

#Program and cultural-review comparison case

#Exogenous-change stop-and-reopen case

#Lighter comparison note with source-return discipline

#Functional versus constructive-description comparison

#Method-option comparison without method choice

#Upper-boundary prompt-bearing exit case

#Same-entity viewing boundary case

#Ontology-exit anti-case

#Authority and gate misuse anti-case

#Invalid publication and repair example

#Bias-Annotation

#Conformance Checklist

#ID.CR-Core ordinary checks

#ID.CR-Conditional checks

#Common Anti-Patterns and How to Avoid Them

#Consequences

#Rationale

#SoTA Alignment: Adopted/Adapted Invariants And Rejected Shortcuts

#Relations

#E.17.ID.CR:End

ComparativeReading - bounded comparative reading over comparative review units

About this pattern

How to use this pattern

Keywords

Relations

Content

Problem frame

Problem

Forces

Solution - comparative review units with bounded comparative reading, escalation, and exit rules

Engineer-manager-first working use, governed-object distinction, and compact branch definition

Engineer-manager-first use

Pattern, case, and governed-object distinction

Compact branch definition

Why the comparative-reading branch needs its own discipline

Local working vocabulary

Scope and exclusions

Working-fit test

Nearest neighboring work

Working-model first; plain questions first, ordinary minimum second, full declaration third

Five plain working questions

Ordinary minimum block

Ordinary working card

Load-bearing extension guidance

Load-bearing declaration block

Interpretant-side block

Static note versus interactive aid

Representation ontology and modeling lens (informative)

Working read-out

Branch-discipline summary

Neighboring-work boundary glance

Ordinary working order for the card

Archetypal grounding

Tell

Show (System)

Show (Episteme)

Boundary bank

Lower-boundary bridge-stance overlay case

Mixed primary-pattern composition with A.6.3.RT

Mixed primary-pattern composition with E.17.EFP

Guided review aid with bounded interaction mode

Product and design-review comparison case

Compliance and release-review comparison case

Research-review comparison case

Program and cultural-review comparison case

Exogenous-change stop-and-reopen case

Lighter comparison note with source-return discipline

Functional versus constructive-description comparison

Method-option comparison without method choice

Upper-boundary prompt-bearing exit case

Same-entity viewing boundary case

Ontology-exit anti-case

Authority and gate misuse anti-case

Invalid publication and repair example

Bias-Annotation

Conformance Checklist

ID.CR-Core ordinary checks

ID.CR-Conditional checks

Common Anti-Patterns and How to Avoid Them

Consequences

Rationale

SoTA Alignment: Adopted/Adapted Invariants And Rejected Shortcuts

Relations

E.17.ID.CR:End