#InterpretationDiscipline / ComparativeReading — bounded comparative reading over comparative review units

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

Placement. Pattern for bounded comparative reading over comparative review units, coordinated with the neighboring A.6.3.*, F.9.1, and E.17.EFP seams. 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. Plain-name. Bounded comparative reading over comparative review units. One-line summary. ComparativeReading governs one comparative review unit over already available, source-pinned material while the same object of talk (DescribedEntityRef) stays preserved, one bounded contrast is being made visible, and stronger uptake still stays outside. Governed object in plain terms. The pattern governs the comparative review unit itself - the comparison note, comparison sheet, or guided review aid that carries one bounded contrast - not the whole source packet and not the wider decision workflow.

Early comparative lens. Read the branch through one early formula: one comparative review unit over already available, source-pinned material keeps the same object of talk visible while making one bounded contrast inspectable, with stronger uptake still left outside. That is the whole early read. It does not govern interpretation in general, the whole source packet, or the wider decision workflow.

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 material so that a team can inspect one bounded contrast while still keeping the same object of talk and without yet claiming equivalence, root cause, redesign, release approval, or another stronger decision.

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 same object of talk visible while making one bounded contrast inspectable. The real job is not yet route choice, approval, ontology repair, or workflow takeover. It is to help reviewers compare without pretending that the comparison note already became a decision.

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 surface should still read 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 material over the same object without yet claiming equivalence, route choice, or decision authority. The job is not to settle the full review or downstream decision workflow. It is to make one bounded comparative review unit honest enough that reviewers can inspect one contrast, know what stronger uptake 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, route choice, gate pressure, or action. 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 material, inspect one bounded contrast, and still keep stronger uptake outside. In practice that means review conversations move faster with less argument about whether the note already settled equivalence, approval, or next action.

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

• restating the same thing or shifting its representation rather than adding one bounded contrast under A.6.3.*;
• explicating an already-declared bridge stance rather than governing a comparative review unit under F.9.1;
• classifying or governing explanation faces rather than carrying bounded comparative reading under E.17.EFP;
• authored-unit object-of-talk stabilization after local repair;
• rival-route or prompt pressure under B.5.2(.0);
• ontology or target change under OntologicalReframing / A.6.4;
• or downstream action, gate, assurance, or adjudication authority under A.15 / A.20 / A.21.

Quick exit route. If this is really same-thing rewrite, bridge explication, explanation-face governance, prompt pressure, ontology change, or gate/authority work, reroute before you open the heavier branch stack. If the main debt is still only local head repair or authored-unit object-of-talk stabilization, use E.17.AUD.LHR (Local Head Restoration) or E.17.AUD.OOTD (AuthoredUnit Object-of-Talk Discipline) first and only then return here. Those neighboring patterns are not part of the ordinary branch burden unless that repair trigger is actually live. For the nearest worked exit bank, move to E.17.ID.CR:5.4.7 through E.17.ID.CR:5.4.10.

Quick recovery route. If the recognition surface fits, recover the branch in this order: 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 read.

Quick kind-plus-lens reading. InterpretationDiscipline names the umbrella and ComparativeReading names the active branch here. Recover the branch through the early comparative lens above: one comparative review unit over already available, source-pinned material, the same DescribedEntityRef preserved, one bounded contrast made visible, and stronger uptake still outside. If that read no longer holds, reroute rather than widening this branch into interpretation-in-general.

First-minute term reading. Read the early pressure terms this way. DescribedEntityRef = the same thing still being discussed across the comparison. Source-pinned material and source anchors = already available material plus the notes, views, or links that keep the comparison checkable. allowedUptake and misuseRisk = what this unit honestly supports now and what stronger reading it may wrongly attract.

Quick first check. Before you read the heavier harness, ask:

1. Am I governing the comparative review unit itself?
2. Does the same object of talk stay preserved while one bounded contrast is being made visible?
3. Is the main burden 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 quick exit route above and the fuller reroute table in E.17.ID.CR:4.5.

Worked-slice pointer. If you need one ordinary sentence fast, borrow the nearest lawful 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-workflow 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 workflow for the governed object here, not a mandatory lifecycle for review work, and not a promise that lawful cases move through one fixed graph in one direction. FPF fixes the local governed object, the local move, the reroutes, and the inherited dynamic frame; actual motion may branch, 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 lawful case may finish after a single bounded comparison, another may reopen after a new outside observation, and another may exit immediately once environmental drift or downstream constraints make a neighboring pattern the more honest governing move.

#Keywords

• comparative reading
• comparative review unit
• bounded comparison
• source-pinned material
• same object of talk
• bounded lift
• forbidden stronger uptake.

#Relations

#Content

#Problem frame

Anti-workflow 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 workflow for the governed object here, not a mandatory lifecycle for review work, and not a promise that lawful cases move through one fixed graph in one direction. FPF fixes the local governed object, the local move, the reroutes, and the inherited dynamic frame; actual motion may branch, 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 lawful case may finish after a single bounded comparison, another may reopen after a new outside observation, and another may exit immediately once environmental drift or downstream constraints make a neighboring pattern the more honest governing move.

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 materials together without overstating what that unit now authorizes. Typical moments include:

• a design-review note that says one already available option write-up foregrounds coupling risk more strongly 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 burdens in the same service episode;
• a research-review note that says one available synthesis foregrounds measurement uncertainty more strongly than another without yet declaring a better method;
• a program or cultural review note that says one available brief foregrounds participation continuity more strongly 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, route selection, program choice, or approval.

#Problem

Without a named comparative-reading discipline:

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

#Forces

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

#Manager-first entry, 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 should first meet the manager-first use surface and the governed-object distinction, and only then the compact branch definition that names the formal comparative burden. That order keeps the branch explicit without making the blockquote definition the first gate into ordinary use.

#Manager-first use

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

• this option write-up foregrounds integration burden more strongly than that one;
• these two available materials 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 strongly than that one, but it is not yet a method choice;
• this program brief foregrounds continuity risk more strongly than that one, but it is not yet a funding decision.

If that sounds like the review unit you need, start here. If instead you are mainly restating source material, explaining it, opening a new route, changing the object of talk, or making a decision, start with the neighboring pattern first.

#Pattern, case, and governed-object distinction

This pattern presents the ComparativeReading branch inside the broader InterpretationDiscipline umbrella. The umbrella names the wider interpretation zone. The branch here is narrower and more concrete. It governs one comparative review unit and only the bounded comparative reading carried by that unit. The wider review or decision workflow remains outside the pattern except where reroute or authority limits are needed.

The kind stack should therefore be read explicitly:

• umbrella = InterpretationDiscipline as the naming-level umbrella;
• umbrella-level move class = bounded interpretation work at that wider level;
• branch = ComparativeReading as the narrowed branch for this pattern;
• governed object = the comparative review unit;
• branch move = bounded comparative reading over already available material;
• wider work = the broader review or decision process that still sits outside this 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 lawful unit forms, not rival governed objects.

This distinction matters because the pattern is not governing reading in the head in the abstract and it is not governing the whole review workflow. It is governing a small, reviewable unit that carries one bounded comparative lift over already available material. 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 stronger burden already belongs to another governed pattern.

#Compact branch definition

ComparativeReading is a branch inside the InterpretationDiscipline umbrella.

It governs one comparative review unit over already available, source-pinned material and carries one bounded comparative reading over that unit.

It stays lawful only while the case preserves the same DescribedEntityRef, keeps the source anchors visible, keeps the added comparative lift bounded, and does not shift its primary burden into same-entity viewing, stronger bridge burden, explanation-face governance, prompt-bearing abductive work, ontology-facing reframing, retargeting, or downstream action authority.

Read this blockquote as the compact branch reminder. It should stay nearby and early, but not stand in front of the manager-first use surface 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 stronger than plain bridge-explication alone but weaker than route 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, route pressure, or action authority.

This pattern gives teams a narrow way to prepare, share, and inspect that comparative review unit without smuggling a stronger burden than the source, bridge stance, and bounded uptake 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, comparison sheet, guided review aid, or guided comparative UI whose explicit burden is one bounded comparative reading.
• Base host classification = baseHostClassification, the primary pattern that still carries the unit before bounded comparative reading is added.
• Reviewed source material = the already pinned or otherwise reviewable material being comparatively read; in plain terms, the already available material under review.
• Source anchors = sourceAnchorSet or sourceRefs that make the interpreted material inspectable.
• Same DescribedEntityRef = the same object of talk remains preserved even while one contrast is being made more visible.
• Interpretive lift = the bounded comparative or asymmetry-bearing reading added on top of already available material.
• Bridge anchor = bridgeCardRef or bridgeStanceRef when the case depends on bridge-mediated correspondence rather than ordinary source reading alone.
• Allowed uptake = what this review unit may legitimately 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 stronger bridge, route, ontology, or authority claim.
• Prompt handoff = the explicit U.AbductivePrompt publication that takes over when rival-route 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 surface used when the case sits close to bridge, explanation, abductive, ontology, or authority seams.

These terms are local review aids. They do not replace source notes, bridge cards, explanation renderings, prompt publications, or gate-bearing materials. 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 material;
• reader-facing interpretive caution that stays source-tethered and preserves the same DescribedEntityRef;
• comparative review units that answer one explicit contrastive question without opening a rival-route search;
• bounded user-fit when that fit only limits uptake rather than widening authority.

Out of scope

• same-entity restatement, conservative rewrite, or representation shift whose main burden stays with A.6.3, A.6.3.CR, or A.6.3.RT;
• pure bridge-explication that only clarifies an already-declared bridge stance (F.9.1);
• explanation-face classification, admissibility, or added-link review on existing faces (E.17.EFP);
• rival-route or prompt-bearing cases (B.5.2.0 / B.5.2);
• ontology-facing reframing or changed object of talk (OntologicalReframing / A.6.4);
• policy, gate, adjudication, assurance, or work-facing use (A.15 / A.20 / A.21).

#Quick entry test

Use this discipline only when all of the following hold:

1. the reviewed source material is already pinned or otherwise reviewable;
2. the review unit adds one bounded comparative or interpretive lift;
3. the case is still answering a bounded contrastive question rather than selecting a route;
4. the same DescribedEntityRef stays preserved;
5. the main burden is not already better described as same-entity viewing, bridge-explication, or explanation-face classification.

If any of those fail, reroute.

#Nearest host seams

Always classify the base host first and open interpretation second. The nearest host seams should be read in this order:

1. A.6.3 / A.6.3.CR / A.6.3.RT first. If the move is still mainly restatement, representation shift, or another same-entity viewing transform, it does not enter interpretation.
2. F.9.1 second. If the review unit only makes an already-declared bridge stance more legible, it stays bridge-subordinate.
3. E.17.EFP third. If the main question is explanation class, face admissibility, or bounded connective prose on an existing face, it stays with explanation governance.
4. B.5.2.0 / B.5.2 fourth. If open-question pressure or route pursuit becomes live, interpretation ends.
5. OntologicalReframing / A.6.4 / downstream authority patterns last. If continuity witnesses, changed target, or decision-bearing consequence are needed, the case has already left this discipline.

#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 surface is a small set of plain questions that helps an engineer-manager decide whether the review unit still belongs here. The opening of E.17.ID.CR:4.1 now follows that same order by value: manager-first use and governed-object distinction come first, and the compact branch definition stays nearby as an early recovery surface rather than the first gate into the branch. The ordinary minimum block comes next for ordinary use. The full declaration block remains available as a load-bearing assurance surface.

#Five plain working questions

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

1. What already available material am I comparing?
2. What single contrast or asymmetry am I trying to make visible?
3. Am I still talking about the same thing, or has the object of talk already shifted?
4. What stronger reading must the team not take from this review unit?
5. What would force me to reroute this review unit into 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 material is being interpreted;
• where the source anchors live;
• that the same DescribedEntityRef remains preserved;
• what exact bounded comparative lift is being added;
• what stronger use remains forbidden;
• that the default worldContactPolicy here is review-only / non-executive;
• and what reroute 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 material, governed unit, bounded lift, and outside workflow, stop here. Repair local head-kind pressure through E.17.AUD.LHR (Local Head Restoration); if the whole review unit still drifts after that repair, hand off to E.17.AUD.OOTD (AuthoredUnit Object-of-Talk Discipline) before adding more declaration weight.

#Ordinary working card

A lawful ordinary comparative review unit should normally let a reader recover these seven rows without opening the heavier declaration harness:

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

• if rows 1-4 are still unstable because one pressured head or qualifier is doing too much work, stop and repair that local 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 slides between reviewed material, comparative move, and outside workflow after one honest local repair, hand off to E.17.AUD.OOTD (AuthoredUnit Object-of-Talk Discipline);
• if rows 1-7 stay recoverable over one pinned source slice or source pair, one preserved DescribedEntityRef, and one bounded contrast, ComparativeReading remains the honest primary lane.

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 seam, 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 over already pinned material. If you first need to restabilize what the review unit is about, what move it is carrying, and what wider workflow remains outside, hand off to E.17.AUD.OOTD (AuthoredUnit Object-of-Talk Discipline) before thickening this card.

#Load-bearing extension guidance

A fuller declaration surface 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 drifts between object, move, and outside work after local repair;
• or the case would otherwise be too easy to over-read as stronger than a bounded comparative review unit.

The load-bearing extension may inherit already-declared host 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 host-owned 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 pressure and the same review unit still drifts between reviewed material, governed unit, comparative move, and outside workflow, hand off to E.17.AUD.OOTD (AuthoredUnit Object-of-Talk Discipline) first and only then decide how much heavier declaration burden should stay here.

#Load-bearing declaration block

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

• sourceRelation;
• sourceAnchorSet or sourceRefs;
• semanticClaimKind = SemanticIdentity | BoundedCorrespondence | AudienceFacingReExpression;
• comparisonBasis;
• addedClaimPolicy;
• bridgeStanceVisibility;
• bridgeCardRef or bridgeStanceRef when the case depends on bridge-mediated reading;
• 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;
• allowedUptake;
• misuseRisk;
• promptWorthinessThreshold;
• ontologyExitTrigger;
• worldContactPolicy;
• downstreamAuthorityLimit;
• baseHostClassification when the review unit is a mixed case layered over A.6.3.* or E.17.EFP.

semanticClaimKind is a sorting aid, not the thing that decides the lawful home. AudienceFacingReExpression by itself does not open interpretation, and BoundedCorrespondence by itself does not remove bridge burden. The main burden plus the neighboring pattern boundaries still decide the lawful home.

#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 uptake visible;
• and stop interpretation prose from quietly becoming prompt-bearing guidance, assurance shorthand, or policy pressure.

#Representation ontology and modeling lens (informative)

The early canonical lens for this branch is already stated near the top: one comparative review unit over already available, source-pinned material, with the same DescribedEntityRef preserved, one bounded contrast made visible, and stronger uptake 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 branch inside the broader InterpretationDiscipline umbrella. 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 semantic-claim kind;
• one declared comparison basis and added-claim policy;
• one allowed uptake boundary, one misuse-risk surface, and one worldContactPolicy;
• 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 inheriting host law plus the shared transduction baseline where those already govern source, continuity, and reroute burden. This branch therefore does not create a rival bridge taxonomy, a rival formal substrate, or a stronger authority surface of its own.

#Working read-out

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

• what reviewed source material is being comparatively read;
• what bounded interpretive lift is being added;
• why the same DescribedEntityRef still remains preserved;
• what stronger host seam is still negative;
• and what reroute or handoff would become mandatory if the case were read more strongly.

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

#Branch-law summary

This section is the compact branch-law summary for ComparativeReading inside the Core. It keeps the branch burden recoverable for ordinary users and manager-first review. For mixed seams, the neighboring host-owner law still remains primary where the base case really belongs to A.6.3.*, F.9.1, or E.17.EFP.

Use the fuller solution, reroute table, worked slices, and relations surfaces here when exact clause wording, full field burden, or full reopen burden matter. Keep the branch to these summary rules.

1. Preserve the same object of talk. Keep the same DescribedEntityRef, visible reviewed source material, visible source anchors, and one declared comparison basis; keep contrastiveQuestion explicit when it is doing real review work.
2. 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 stronger theory, bridge licence, route pressure, explanation governance, ontology shift, or downstream authority.
3. Classify the base case first. If the main burden is really same-entity rewrite, bridge explication, explanation-face work, prompt opening, ontology reframing, retargeting, or downstream authority, this pattern should not stay primary.
4. Keep stronger seams explicit. BoundedCorrespondence still carries explicit bridgeCardRef or bridgeStanceRef; prompt-worthy cases hand off as U.AbductivePrompt; ontology pressure exits to OntologicalReframing or A.6.4; stronger action, gate, or adjudication use exits to downstream authority patterns.
5. Keep reader-fit bounded. targetUserModel, interactionMode, contrastiveQuestion, allowedUptake, and misuseRisk may be surfaced when they are doing real work, but they do not authorize coaching, route selection, policy guidance, or a stronger authority claim.

#Quick reroute glance

This table is a first-pass routing aid only. For fuller mixed-seam burden, read this table together with the neighboring host-owner law.

For first-minute use, read the four routing rows around the branch itself as a compact mirror of the near-top entry check and the ordinary working card:

• local pressured head -> E.17.AUD.LHR (Local Head Restoration);
• stable same-object comparative review unit -> stay with ComparativeReading;
• same unit still drifting after local repair -> E.17.AUD.OOTD (AuthoredUnit Object-of-Talk Discipline);
• stronger host seam already primary -> reroute out of this branch. If you already know you are exiting rather than staying, use the non-branch rows first and then read E.17.ID.CR:5.4.7 through E.17.ID.CR:5.4.10 as the nearest worked exit bank.

#Ordinary working order for the card

The shortest ordinary working order is:

1. classify the base host first if the case is mixed;
2. pin the reviewed source material and make the same DescribedEntityRef visible;
3. state the bounded comparative lift in one sentence;
4. declare the stronger forbidden uptake and the review-only / non-executive world-contact limit;
5. name the reroute trigger that would end interpretation.

That five-step order is not a second ordinary working card, and it is not a canonical review workflow. It is only one local working aid for this branch. 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 burden in compact form rather than a heavier load-bearing declaration block whenever seam 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, reroute to E.17.AUD.OOTD (AuthoredUnit Object-of-Talk 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 lawful outcomes for the same branch: some cases stay small and stop, some stay mixed with a host pattern, and some reopen or reroute when outside observations, environmental drift, 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 material without yet opening route-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 stronger forbidden uptake, and the reroute 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 route is yet being asked for.

#Show (Episteme)

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

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

Why this stays here.

• the base host surfaces remain identifiable;
• the comparative lift is explicit and bounded to one reviewer task;
• explanation-face governance and same-entity transform law remain with their host patterns;
• downstream authority and prompt-bearing route pressure remain negative.

#Boundary bank

#Lower-boundary bridge-explication case

Bridge-explication review unit. The local term tracks maintenance burden, while the partner term tracks service continuity, so the bridge 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 bridge-explication is added.

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

Base host rendering. A same-entity comparison sheet retabulates one pinned incident note into columns for trigger, burden, 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 host rendering. A Tech-face explanation rendering is already classified as SourceLinkedReconstruction and publishes a bounded connective policy.

Comparative review unit. For maintenance reviewers, this rendering foregrounds the difference between operator burden and throughput burden more strongly than the original prose, but it should not be read as a stronger 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 a bounded comparative uptake 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 uptake: bounded comparative triage only. Misuse risk: do not treat this aid as route 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 route pursuit;
• allowed uptake 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 surface for the same planned release. One note foregrounds coupling and rollback burden; the other foregrounds delivery simplicity and lower immediate implementation cost.

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

Entry-triage reading. This is the ordinary stay-here branch: 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 surface remains the DescribedEntityRef;
• one bounded comparative lift is made explicit for a declared review task;
• the unit supports design discussion without quietly becoming route 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 strongly than rollback evidence, while the internal checklist foregrounds rollback evidence more strongly than protocol conformance; this comparison helps frame the review, but it is not yet a release gate or equivalence claim.

Entry-triage reading. This is the same stay-here branch under a release/compliance load: the comparison unit is already stable enough, so the primary burden 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 a 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 strongly; the other foregrounds protocol repeatability more strongly.

Comparative review unit. For method review, the first synthesis foregrounds uncertainty-handling limits more strongly than the second, while the second foregrounds repeatability support more strongly 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 route 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 strongly; the other foregrounds short-term event visibility more strongly.

Comparative review unit. For programme review, the first brief foregrounds participation continuity more strongly than the second, while the second foregrounds short-term visibility more strongly 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-drift 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 strongly than rollback evidence, while the internal checklist foregrounds rollback evidence more strongly than protocol conformance; this comparison frames the review, but it is not yet a release gate or equivalence claim.

Entry-triage follow-through. This case begins on the same lawful stay-here branch 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 lawful next move is either to restate a fresh comparative review unit over the new declared basis or to reroute into a neighboring lane if downstream gate or authority burden has now become primary.

Nearest first-minute exit bank. The next four cases are the nearest worked exits for the quick exit route above: 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 reroute cue before opening the heavier branch stack.

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

• route pressure has become live;
• the review unit is now prompt-bearing rather than only interpretive;
• the lawful home is B.5.2.0 / B.5.2 through explicit U.AbductivePrompt handoff.

#Same-entity viewing boundary case

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

Why it does not enter interpretation:

• the main burden is representational reshaping rather than comparative reading;
• no bounded asymmetry or interpretive claim is added;
• the safer home is A.6.3.RT.

#Ontology-exit anti-case

Ontology-pressuring review unit. The older maintenance note and the new drift 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 surface names.

Why it exits:

• the case is now asking for a stronger same-referent / new-intension reading;
• continuity witnesses would now be needed;
• bounded comparative reading is no longer enough, so the lawful home is 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 packet 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 stronger source-governed material;
• the lawful home 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;
• BoundedCorrespondence is being implied without explicit bridge burden;
• stronger substitution and authority uptake 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 packet remains primary.

What the repair does:

• restores the source and bridge anchors;
• weakens the claim back to bounded comparative reading;
• reasserts forbidden stronger uptake.

#Bias-Annotation

Lenses tested: Gov, Arch, Onto/Epist, Prag, Did. Scope: bounded comparative review units governed under the ComparativeReading branch of 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, route pressure, or downstream-authority inflation. The main mitigations are explicit primary-pattern classification, visible source anchors, explicit interpretant-side boundedness, explicit stronger forbidden uptake, explicit governed-object surfacing, and hard exits 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

Use this as the ordinary checklist for this pattern. For fuller mixed-seam burden, read this checklist together with the neighboring host-owner law and the reroute surfaces gathered in this section.

Assurance recovery note. Read this checklist as a heavier read-back of the already-declared branch burden, 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.

1. 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 workflow or a hidden mental act.
2. CC-ID-2 - Source anchors and comparison basis are explicit. A reviewer can see what already-fixed material is being read and what declared comparison basis or contrast is carrying the lift.
3. CC-ID-3 - The lift stays bounded. The pattern keeps the comparative lift visibly weaker than bridge licence, explanation governance, route opening, ontology shift, or authority-bearing guidance.
4. CC-ID-4 - Host-first routing 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.
5. CC-ID-5 - Bridge burden does not hide. If BoundedCorrespondence is live, bridgeCardRef or bridgeStanceRef remains visible and subordinate.
6. CC-ID-6 - Stronger exits stay visible. Prompt-worthiness, ontology pressure, or downstream authority pressure leads to explicit reroute rather than staying hidden inside comparative prose.
7. CC-ID-7 - Reader-fit stays bounded. targetUserModel, interactionMode, contrastiveQuestion, allowedUptake, and misuseRisk are visible when needed, but they do not open a stronger authority claim.
8. 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.

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

#Common Anti-Patterns and How to Avoid Them

#Consequences

• The middle band between bridge-explication 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 burden, but the gain is fewer hidden host-boundary mistakes and less governed-object drift.
• Guided comparative review units become easier to prepare honestly because allowed uptake, misuse risk, and world-contact limits can be declared without pretending that the unit already carries a broader guidance burden than it really does.
• Users get a lawful way to keep bounded comparative review units modest: the unit can stay useful while its reading pressure remains below the reroute 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 stronger forbidden uptake, and the reroute trigger that would end interpretation. The gain is practical: a team can compare available material honestly without pretending that a helpful review unit already carries more authority than it really does.

#SoTA-Echoing

SoTA note. This section does not mint an independent second rule layer. It is a load-bearing alignment surface: the Solution, Conformance Checklist, boundary rules, and Relations of this pattern must match the stance stated here or explicitly justify any divergence. Assurance recovery note. Read each row here as a heavier confirmation of one already-declared branch burden. 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 branch 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 branch was chosen.

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 reroute laws must stay visible enough that a reviewer is not forced to infer the real burden from tone alone. Ordinary recovery: read the Reviewed material, Source anchors, and Bounded lift rows together before leaning on the citation. 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 stronger forbidden uptake rather than letting them stand alone. 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 stronger 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 burden through the interaction fields plus the prompt and authority exit rows rather than treating the source citation as a licence for stronger guidance. Manager payoff: a guided comparative UI can stay useful for review without silently becoming coaching, route 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, route, or authority burden. The pattern adopts the demand for explicit grounding, but rejects any shortcut where plausible comparative prose is treated as if it were already a stronger semantic or operational licence. Ordinary recovery: use the Forbidden stronger uptake and World-contact limit rows before letting polished prose win the argument by tone. Manager payoff: polished prose is no longer enough to overrule the underlying source packet or to sneak in a stronger 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 umbrella: InterpretationDiscipline names the wider interpretation zone for this branch.
• Branch: 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-seam reading: the comparative review unit is one working review unit that may be carried by a lawful publication surface over that inherited frame; it is not the moving lineage itself, not a carrier, and not the whole review workflow.
• Builds on: C.2.2a, A.16.0, F.9, E.14
• Normative dependencies: the shared transduction baseline plus whichever host law still governs the base case (A.6.3.*, F.9.1, or E.17.EFP in mixed seams); those constraints remain normative even when the branch stays small.
• Canonical branch-law locus inside the Core: this section now carries the summary, checklist, worked slices, and boundary surface for ComparativeReading; mixed-seam host-owner law remains primary where the base case still belongs elsewhere.
• Neighboring repair patterns: use E.17.AUD.LHR (Local Head Restoration) when head-kind or qualifier pressure is still local; use E.17.AUD.OOTD (AuthoredUnit Object-of-Talk Discipline) when the same review unit still drifts between reviewed material, governed unit, comparative move, and outside workflow 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, F.9.1, E.17.EFP, B.5.2.0, B.5.2, OntologicalReframing, A.6.4, A.15, A.20, A.21
• Primary boundary touch-points: A.6.3.*, F.9.1, E.17.EFP, and B.5.2.0 / B.5.2
• Exit seams: rival-route pressure exits to B.5.2.0 / B.5.2; ontology and changed-target pressure exit to OntologicalReframing or A.6.4; downstream action, gate, assurance, and adjudication pressure exit to A.15 / A.20 / A.21
• Boundary notes: same-entity transform law stays with A.6.3.*; bridge-explication stays with F.9.1; explanation-face governance stays with E.17.EFP; bounded comparative reading does not by itself authorize stronger downstream use.
• Non-goal: this branch does not create a rival authority surface, a rival bridge taxonomy, or a rival formal substrate.

#E.17.ID.CR:End