C.25:4.2 - Q-Bundle shape and identity boundary

The full escalation form is:

Q-Bundle := <Name, QualityBearer, ClaimScope?, WorkScope?, Measures[CHR], QualificationWindow?, Mechanisms?, Status?, Evidence?>

Q-Bundle names a C.25-local record-shaped part of one exact U.ClaimGraph. It is not a new Kernel kind, an independently identified world object, or a second identity beside the enclosing episteme. That episteme supplies the exact claim content, one independently identified QualityBearer as its EntityOfConcern, and the effective U.ReferenceScheme under which the quality claim is read.

The ? is operative: omit any optional slot unless changing it could change the current claim or receiving action. A bundle may therefore contain only Name, QualityBearer, Measures, and one load-bearing scope or window. The full tuple is an escalation aid, not a form every author must fill.

Changing any bundle content that changes the quality claim changes the ClaimGraph and therefore identifies another episteme under C.2.1. A changed layout, form, publication occurrence, or carrier can leave that episteme unchanged. A gate, publication, proxy, comparison, or roll-up cites the exact episteme or one exact C.2.1 ClaimAddress, meaning the exact edition plus an intrinsic claim identity declared by that edition’s ClaimGraph. Later ClaimAddress uses in C.25 mean that same value; a field list or raw record reference is not enough.