A.2.6:11 - Archetypal Grounding - Worked Examples

A.2.6:11.1 - Claim-scope membership boundary

Claim-bearing episteme E_adhesive states that Adhesive X retains at least 85 percent tensile strength on Al6061 for two hours at 120-150 °C under rig edition Calib-v3. It designates exact claim scope G_adhesive.

• slice_in = {substrate=Al6061, temp=140°C, dwell=90min, rig=Calib-v3}. member(slice_in, G_adhesive) is true.
• slice_out = {substrate=Al6061, temp=160°C, dwell=90min, rig=Calib-v3}. Membership is false; the attempted use stops.
• slice_unknown = slice_in, evaluated with an interpretation basis whose required rig-edition resolution is unavailable. Evaluation returns unknown; it neither excludes the slice nor permits the use.

LabEvaluator_A may perform exact membership-evaluation work through the declared USM operation. When a named audit or replay use needs a judgment to persist, a C.2.1 episteme may record it. A table showing the three rows is a C.29 representation.

The same G_adhesive may participate in two independently governed model-applicability relation occurrences and may be referred to by exact applied constraint claims in two A.22 structures. Only a selected obtaining model-applicability occurrence or an exact constraint claim as applied contributes through its corresponding A.22 discriminator; the common scope itself contributes through neither path and neither merges nor identifies the relations or structures. A declared applicability interval in either occurrence description is separate from the actual maximal continuous obtaining extent.

A.2.6:11.2 - Translation only when local senses require it

An assembly use expresses temperature through an exact local calibration sense different from the laboratory sense used in G_adhesive. F.9 Bridge B-lab-assembly-temp obtains between those two cells under its calibration-correspondence profile; the profile contains no translation-use rule or loss tolerance.

Separate C.2.1 claim C-adhesive-scope-translation has that Bridge as EntityOfConcern and affirmative polarity. Its content names use translate G_adhesive for the assembly membership check, direction laboratory-to-assembly, the calibration rule for mapping the source interval, and tolerance no selector-meaning loss and at most 2 °C boundary uncertainty.

Use that translation only while exact A.10 relation EP-adhesive-scope-translation connects the claim and that bounded use to evidence record CalibrationComparisonRecord.Calib-v3-to-AssemblyCalibration-v5.2026-07-25. Provenance edge CalibrationComparisonRecord.Calib-v3-to-AssemblyCalibration-v5.2026-07-25 --carriedBy--> CalibrationComparisonRegister.Calib-v3-to-AssemblyCalibration-v5.2026-07-25.csv names its carrier. The window runs from 2026-07-25 through 2026-10-23 and closes earlier if either calibration edition, the mapping rule, or the 2 °C tolerance changes.

The path supports neither reverse translation, a mapping outside the named rule or tolerance, nor a claim that the A.6.1 application or membership evaluation occurred. If the record, carrier, or provenance edge is missing or stale, or the window closes, stop before translation and set RelianceDisposition=reopen; otherwise RelianceDisposition=pass applies only to this bounded use. No assurance claim is made.

For this case, stipulate that the actual A.6.1 application deriveTranslatedScope(G_adhesive, B-lab-assembly-temp, C-adhesive-scope-translation, AssemblyReferenceScheme) applies the named rule and tolerance and returns the receiving scope [122,148]°C. The receiving membership evaluation uses that scope.

If the receiving use merely uses another designation for the same sense under an ordinary resolvable reference scheme, introduce no Bridge, use claim, or translation.

A.2.6:11.3 - Capability: robotic weld Work scope

• Context: RobotCell‑Weld@2026.
• Holder and ability claim: WeldRobot_3; WeldAbilityClaim states that this System can weld seam W at bead width 2.5 ± 0.3 mm and cycle ≤ 12 s under the conditions below.
• Work scope: {humidity<60 %, current∈[35,45]A, wire=ER70S‑6, controller=FW‑2.1}.
• Job slice: {humidity=55 %, current=40A, wire=ER70S‑6, controller=FW‑2.1}.
• Qualification policy: in this example, Recertification90d considers reliance on WeldAbilityClaim qualified for 90 days from the certification date recorded in the controller certificate.
• Qualification evaluation time: 2026-07-25, outside the Work-scope tuple.
• Guards (WG‑1..3): coverage true; measures satisfied; qualificationWindowHolds(WeldAbilityClaim, Recertification90d, 2026-07-25) is true because certification occurred on 2026-05-26.
• Outcome: the capability-related guards pass for this Work. Authority, assignment state and other required entry conditions remain separate.

Controller certificate age does not change Work-scope membership in this case. When the 90-day qualification condition fails, WG-3 stops operational use without removing the Job slice from the scope.

A.2.6:11.4 - Serial intersection (API + dataset compatibility)

• Claim A (API Standard): v2.3 request schema with constraint “idempotent under retry”.
• Claim B (Dataset cohort): “metrics valid for cohort K with schema ds‑14”.
• Composition: service S depends on both A and B → serial intersection of Claim scopes: {api=v2.3} ∩ {cohort=K, schema=ds‑14}.
• Target slice: {api=v2.3, cohort=K, schema=ds‑14} → membership true.
• Target drift (e.g., ds‑15). The changed target slice lies outside the intersection ⇒ path inapplicable for that slice.

A.2.6:11.5 - Parallel support (SpanUnion) in a safety case

• Line L1: tests on dry asphalt support braking property; scope S1={surface=dry, speed≤50 km/h}.
• Line L2: simulations for wet asphalt; scope S2={surface=wet, speed≤40 km/h}.
• Independence basis: partition P-braking identifies complete disjoint essential-component sets for this braking claim: L1 uses DryTrackTestRecord and DryRigCalibration; L2 uses WetBrakeModel, WetValidationRecord, and WetRigCalibration.
• Published scope: SpanUnion({S1,S2}) = {(dry, ≤50), (wet, ≤40)}, with reference to P-braking.
• Guard: allowed; union does not include (wet, 45) because not supported.

With only the method labels, leave P-UNION unresolved. If CalibrationRecord-Q is essential to both lines, P-UNION fails for this pair; retain the individual lines and use their component scopes to assess any dependent combination.

A.2.6:11.6 - ML model deployment with different local feature senses

• Model claim: “AUC >= 0.92 on cohort K, pipeline P, feature sense Training.F.”
• Claim scope: {cohort=K, pipeline=P, exactLocalSense=Training.F}. No gammaTime selector is present because this example does not claim that model applicability changes with the slice time.
• Target slice: product On-Device@v7, pipeline P-prime, feature sense Device.F-prime.
• Translation trigger: ordinary designation resolution fails because Training.F and Device.F-prime have different declared semantics, not merely different labels. Exact F.9 Bridge B-training-device-feature obtains between those cells under a lossy-subset correspondence profile; the profile carries no device-use rule or tolerance.
• Bounded translation claim: exact current C.2.1 claim C-device-feature-scope-translation has that Bridge as EntityOfConcern and affirmative polarity. It names use translate the training claim scope for the On-Device@v7 membership check, direction training-to-device, the subset-mapping rule, and tolerance no feature-kind substitution and no target slice outside the tested mapped subset.
• Evidence and reliance: Before translating, verify that exact A.10 relation EP-device-feature-scope-translation connects claim C-device-feature-scope-translation and this bounded use to both records below.
  • Mapping evidence: MappingTestRecord.TrainingF-to-DeviceFprime.OnDevice-v7.2026-07-25, with exact carrier edge MappingTestRecord.TrainingF-to-DeviceFprime.OnDevice-v7.2026-07-25 --carriedBy--> MappingTestReport.TrainingF-to-DeviceFprime.OnDevice-v7.2026-07-25.json.
  • Training evidence: TrainingEvaluationEvidence.K-P-TrainingF.2026-07-25, with exact carrier edge TrainingEvaluationEvidence.K-P-TrainingF.2026-07-25 --carriedBy--> TrainingEvaluationReport.K-P-TrainingF.2026-07-25.json.
  • Window and stop: the 180-day window runs from 2026-07-25 through 2027-01-21 and closes earlier if pipeline P or P-prime, either feature-sense edition, or the tested mapped subset changes. If a record, carrier, or edge is missing or stale, the window closes, or a named dependency changes, stop before translation and set RelianceDisposition=reopen; otherwise RelianceDisposition=pass applies only to this bounded use.
  • Boundary: the path supports neither feature-kind substitution, a target outside the tested subset, material release or assurance, nor a claim that deployment occurred. No assurance claim is made; a material release use stays with its direct release rule, and an actual assurance claim uses B.3.
• Guard: bind translatedScope := deriveTranslatedScope(G, B-training-device-feature, C-device-feature-scope-translation, ProductReferenceScheme), then evaluate evaluateMembership(TargetSlice, translatedScope, InterpretationBasis); separately require the chosen formality predicate. The translated scope covers only the tested mapped subset.
• Outcome: admit only a target slice in the returned subset; otherwise return false or unknown according to the exact returned scope and available evaluation input.