A.2:5.4 - The Same Label in Two Local Practices

An editorial-review practice and a safety-assurance practice can each use ReviewerSystemRole. Compare their exact C.3 definitions before deciding whether one kind continues. In this case the safety-assurance condition admits a materially different contribution and member/non-member boundary, so two kinds are present. The practice names help locate those definitions; a shared label, vocabulary source, or reference-scheme spelling establishes neither sameness nor a Bridge.

Suppose a staffing dashboard proposes u-reviewer-display: show assignments from both practices in one Reviewer column. First recover the two exact local kinds and any F.17 cells needed by the displayed expressions; then establish only the C.3.3 kind relation and F.9 local-sense relation that the display actually consumes. State a separate C.2.1 bounded-use assertion with direction d-safety-to-editorial-display, rule r-preserve-reviewer-differences, and tolerance t-shared-label-only, plus polarity and effective scheme. The rule keeps the practices’ admission, independence, evidence, and completion fields separate and tolerates only the shared display label.

Current A.10 provenance and RelianceDisposition=pass can support that display use. They do not justify substitution between assignments or merge the two kinds. If an actual named assurance claim about that use is current, only its B.3 result can support that bounded assurance use; a non-positive disposition stops or narrows it. Consequence alone creates no assurance claim. A Bridge Card can package the Bridge, bounded-use assertion, evidence, and disposition, but it grants no assignment, eligibility, capability, use suitability, or performed-Work inference. A selected BoundedModelUseStructure is cited only in the receiving use whose interpretation it changes.