A.6.3.RT:5 - Archetypal grounding

A.6.3.RT:5.1 - Ordinary same-concern text-to-table move

Source slice. Service S showed three recurring latency spikes in the evening batch window. Trace T-44 and dashboard pin D-17 concern the same service and time window.

Target table. These are recurring latency spikes.

The first result needs no endpoint dossier. The note says the service, window, count, recurrence, and pins can be inspected together; those claims survive; prose order is lost; no causal or severity claim is added; use is inspection; and any question about an omitted qualifier or causality returns to the source note and traces.

An independently cited target includes the recurrence caption. If the table is independently cited or disputed, exact source episteme LatencyFinding-X and receiving episteme LatencyTable-Y concern Service-S-during-W under effective schemes ServiceTelemetryScheme-4 and TabularTelemetryScheme-2. TabulateLatency : LatencyFinding-X -> LatencyTable-Y is the exact construction; it states claim construction, endpoint-scheme relation, same exact EntityOfConcern, preservation, omission and recoverability, prohibited strengthening, applicability, inspection-only use, and return to the source note and traces. The visible table form and file carrier are not Y.

A.6.3.RT:5.1.a - A diagram used in a geometric construction

A.6.3.RT.OE:5.1 develops the equilateral-triangle construction on a nonzero segment AB in the Euclidean plane. It keeps the same segments available as radii of two constructed circles and as sides of the triangle. The radius equalities can then be combined in the geometric argument.

For the RT use, the source consists of the construction instructions and intermediate geometric relations. The representation note preserves the circle constructions and segment identities, names joint inspection as the gain, and returns to the subject premises if an intersection or equality is disputed. Geometry supplies the construction and justified conclusion; drawing measurements are not proof premises. The construction and drawing can develop together.

A.6.3.RT:5.1.b - Syllables against a hand-cycle reference

A.6.3.RT.OE:5.3 prepares given syllable-duration assignments against a learned three-beat hand cycle with four pulses per beat. Arithmetic and rhythmic composition determine the six-pulse preparation and the phrase’s ending at the third cycle boundary.

RT’s representation note retains duration assignments, pulse constancy and cycle position, identifies coordination with the hand reference as the gain, and returns to those conditions when the ending no longer aligns. The utterance and gestures can both represent rhythmic content and realize rhythm. Actual fluency or learning requires observation when either is the question.

A.6.3.RT:5.2 - Positive later-specific table-to-diagram occurrence

For this identity-and-obtaining illustration, take the stated endpoint, scheme, model-use, Work and binding facts as hypothetical givens. The source table, receiving diagram and omitted qualifiers are not shown, so this case does not replay their preservation comparison.

Exact source episteme CoolingLoopRelationTable-X and exact receiving episteme CoolingLoopDependencyDiagram-Y state the same two connection claims about CoolingLoop-7 under effective schemes TabularPlantScheme-5 and DirectedDiagramPlantScheme-3. Y is a candidate episteme, not automatically a U.View.

Scheme-description epistemes TabularPlantSchemeDescription-5 and DirectedDiagramPlantSchemeDescription-3 concern their respective schemes and state their interpretation rules. Independently selected CoolingLoopReviewModelUseStructure satisfies A.1.1 because its model-use organization changes this review. A.13 identifies PlantModelingTool-2 as the actual performer through the exact covering assignment. A.15.1 independently admits dated CoolingLoopDiagrammingWork-18. Because this example states precise assignment-bound attribution, its direct case fact says that the Work was performed under the same exact A.13 assignment, so the F.6 check is positive. If that direct fact were missing or another F.6 condition failed, the Work would remain intact and only the attribution would be unresolved. The Work’s A.6.1 bindings use all six participants. DiagramCoolingLoop : X -> Y is the exact construction; it states claim construction, endpoint-scheme relation, same exact EntityOfConcern, preserved connection claims, omitted table qualifiers and their recoverability, prohibited strengthening, applicability, topology-inspection use, and return to X.

Only then does this occurrence obtain:

RepresentationSchemeTransitionRelation@Context(
  CoolingLoopReviewModelUseStructure,
  CoolingLoop-7,
  CoolingLoopRelationTable-X,
  CoolingLoopDependencyDiagram-Y,
  TabularPlantSchemeDescription-5,
  DirectedDiagramPlantSchemeDescription-3)

Its transition-description episteme cites the Work, construction, exact source relations, omitted qualifiers, topology-inspection use, blocked control-timing/work-order inference, and return to X. Rows become directed edges; pairwise lookup becomes topology inspection; each edge links back to its source-table relation. Publication, diagram form, and SVG carrier remain separate. Y is a U.View only if E.17.0 conformance independently obtains.

A.6.3.RT:5.2.a - Correspondence-mediated text-to-table shift

Source prose. In the safety view, CL-2 maintains the required temperature condition during standard operating demand.

Target row.

CM-12 is an additional illustrative correspondence reference, not content recovered from the source quotation. Until its relation kind, endpoints and obtaining basis are supplied, this row does not establish a correspondence-mediated exact construction.

For reliance-facing use, the case stays RT only when exact X, exact Y, and v : X -> Y are identified, their EntityOfConcern is the same, and every relied-on correspondence is an exact governed occurrence. The visible row and correspondence record are not those governed correspondence occurrences.

A.6.3.RT:5.2.b - Same-concern diagram-to-structured-notation shift

Source diagram. CoolingLoop -> Sensor A; CoolingLoop -> Valve B

Target notation. dependsOn(CoolingLoop, SensorA) and dependsOn(CoolingLoop, ValveB)

This remains RT when the notation carries the same two source connection claims and adds no dependency theory. If dependsOn has stronger semantics than the source arrows, that added claim must be removed or separately established.

A.6.3.RT:5.2.c - Functional-description diagram, table, or screen shift

A source description says that a mixing cell transfers liquid from Tank A through heat exchanger H-2 to reactor R-4, while keeping instrumentation and control claims outside. A target table foregrounds the transfer path. This remains RT only while the same functional slice is represented without adding performed-work order, module structure, evidence, gate passage, or control architecture.

Explanatory diagram order is not physical time or Work order unless the source states that temporal claim. OCR or parsing that merely extracts pixels, text, or layout starts with A.7. If the target becomes honest only by omitting exceptions, confidence bands, or source distinctions under a narrower use, use A.6.3.CSC.

A.6.3.RT:5.3 - Boundary to textual rewrite

A prose note is shortened, reordered, or translated but remains in the same textual regime. Use A.6.3.CR rather than inventing RT.

A.6.3.RT:5.4 - Boundary to explanation-facing rendering

A representation is changed mainly to teach or explain an existing face. E.17.EFP is primary; RT remains only for a separately material scheme transition.

A.6.3.RT:5.4.a - Boundary to bridge-bearing comparison

A local reliability note about Pump P-2 becomes a comparison claiming operational equivalence with Unit U-7 in another plant. That is not merely representation change. Keep any local representation delta in RT. Under F.9, first resolve the two exact F.17 SchemeSenseCell values and test that a Bridge obtains; then state the separate C.2.1 bounded-use claim for this equivalence or substitution use.

A.6.3.RT:5.4.b - Boundary to carrier work

A table is exported as CSV and dashboard PNG after its representation scheme was chosen. The later Work produces the CSV and PNG carriers by formatting, exporting, packaging, or rendering the already chosen representation; it is not another RT merely because the visible form changed.

A.6.3.RT:5.4.c - Boundary to coarsened dashboard view

An incident worksheet carries three causal branches, two confidence bands, and an open ambiguity; a dashboard tile foregrounds only cache-failover evidence. If the tile needs a declared narrower use, non-admissible action, and explicit return to the worksheet, A.6.3.CSC is primary. The tile is not causal proof, service-status verdict, or action cue.

A.6.3.RT:5.4.d - Boundary to structure-to-narrative rendering

Source structure. Architecture candidate C-2 has module split M, data-custody constraint D, placement constraint P, and unresolved latency versus maintainability trade-off T.

Unsupported narrative. The team first tried to preserve M, then found that D forced P, so C-2 accepts latency residual T to preserve maintainability.

This adds an earlier attempt by the team, a discovery with the claim that D forced P, and a decision resolving the source’s still-unresolved trade-off.

Source-faithful reader ordering. To examine C-2, first consider module split M, then data-custody constraint D and placement constraint P; finally consider the unresolved latency-versus-maintainability trade-off T.

The source-faithful alternative orders the selected structures into a reader path; “first”, “then”, and “finally” describe that reading order, not a history of design Work. Apply A.6.3.NAR for ordering, connective account, preservation/loss, use, and source return. Use RT only for a remaining representation-scheme shift that does not depend on that narrative ordering.

A.6.3.RT:5.5 - Guarded decode-mediated rendering

Probe run P-8 is tied to model-state log M-12 and evaluation bundle EV-4. If their source material concerns one independently identified failure episode, a decoded rendering may suggest a cluster corresponding to that same episode. Until the decoding/access relation and recoverability evidence support a named stronger use, keep the result exploratory and report-only. A latent region, feature cluster, probe result, source publication, or readable output fills no episteme endpoint.