12.1.5 Tensor Operation Verification Scope

Tensor Operation Verification Scope is the delimitation of exactly which claims about a tensor operation's output actually require verification against the transformation-law procedure, distinguishing the specific checks that remain necessary after an operation's own scope conditions have already been confirmed from checks that those scope conditions have already rendered redundant.

Foundational Setting

Verification Is Not Uniformly Required Everywhere

Once a tensor operation's own scope conditions, such as matching type for addition or an available metric for raising an index, have been confirmed to hold, some further checks are guaranteed automatically by that confirmation and need not be independently verified, while other aspects of the result still warrant explicit confirmation. Operation verification scope draws this line precisely.

Two Categories of Post-Operation Claims

Any claim about the result of a tensor operation falls into one of two categories: claims that follow automatically once the operation's scope conditions are satisfied, and claims that require an independent check even after those conditions are confirmed.

What Scope Conditions Already Guarantee

Type Preservation Under Confirmed Scope

If addition is applied to two tensors already confirmed to share variance type $$(p,q)$$, the fact that their sum is again a tensor of that same type follows automatically from the linearity of the transformation law and does not require a separate, independent verification pass:

Contraction's Guaranteed Reduction

Similarly, once contraction's scope condition of a genuine upper-lower index pair is confirmed, the reduced type of the result, and the fact that the contracted sum transforms consistently, both follow directly from the algebraic cancellation built into the operation and require no further, separate confirmation.

What Still Requires Independent Verification

Correctness of the Specific Objects Involved

Confirming an operation's scope condition, such as verifying that a pair of indices consists of one upper and one lower index, says nothing about whether the objects being contracted are themselves genuine tensors in the first place; this remains a separate question requiring its own verification, particularly for objects with unfamiliar or externally imported notation.

Composite Expressions Built from Multiple Operations

When several operations are chained together, confirming each individual operation's scope condition in isolation does not automatically confirm that the entire composite expression behaves correctly, since an error could still arise from a mismatch between how one operation's output is fed into the next, making a check of the full composite expression's behavior still worthwhile in genuinely novel or unfamiliar constructions.

Visual Overview

Diagram of the Verification Scope Boundary

Practical Implications for Efficient Verification

Avoiding Redundant Checking

Recognizing what is already guaranteed by a confirmed scope condition allows verification effort to be concentrated where it is actually needed, rather than redundantly re-deriving type preservation or invariance properties that a satisfied scope condition already secures automatically.

Directing Effort Toward Genuine Risk

Conversely, recognizing what remains unguaranteed directs attention appropriately toward the input tensors themselves, particularly any object whose tensor status has not yet been independently established, and toward the overall behavior of composite expressions assembled from several chained operations.

Summary of Key Traits

Defining Characteristics

• Confirming an operation's own scope condition, such as matching type or a valid index pairing, automatically guarantees certain properties of the result, including type preservation, without further checking.
• The tensor status of the input objects themselves is not guaranteed by an operation's scope condition and generally requires separate, independent verification.
• Composite expressions built from multiple chained operations may still warrant a holistic check beyond confirming each individual operation's scope in isolation.
• Distinguishing these two categories allows verification effort to be applied efficiently, avoiding redundant checks while still covering genuine sources of risk.