F.16:12 - Cross-domain application sketches

These sketches select claims and routes for a later worked case. They become replayable examples only after their exact local meanings, subject facts, source passages, observations and results are supplied.

F.16:12.1 - OWL class and FCA formal concept

Situation and claim. A product catalogue uses an OWL class named Pump and an FCA formal concept with a similar label. The example asks whether their covered products may be compared for one catalogue query.

Recover both exact local claims. State the actual relation, if any, between their extensions for this data set and the difference between OWL subclass semantics and FCA lattice order. A small comparison table may display the evidence and limits. Similar labels and table co-placement do not establish identity or class inclusion.

F.16:12.2 - System role and RBAC role

Situation and claim. The same System performs Work under a local operator system-role assignment and also has permissions grouped by an RBAC role. The claim is that these are different subjects even when both use the word role.

Recover the local system-role kind under A.2 with C.3 and the exact assignment under A.2.1. For claimed dated Work, recover the performer’s A.13 core and independently admit the Work under A.15.1; add F.6 only for precise attribution through that same obtaining assignment. F.4 supplies a kind description only when one is needed. Use the access-control pattern for the permission grouping, E.10.ROLE and F.0.1 for the trigger word, and the direct rule for any separation-of-duties constraint. A table row or shared spelling establishes neither sameness nor disjointness.

F.16:12.3 - Method description, Work, and service promise

Situation and claim. A build MethodDescription contains a target duration; dated build Work occurs; observations report actual duration; a service promise is evaluated for a calendar week.

Use A.3.2 for MethodDescription membership, A.15 and B.1.5 for delivery and evaluation Work and any Method enactment, C.16 for observations and measured values, A.2.3 and F.12 for promise evaluation, A.6.1 for the exact evaluation application and result binding, A.10 for a descriptive account of independently established evidence relations and bounded reliance, and B.3 only for an actual named assurance claim. Cite the MethodDescription edition only if it changes the result or replay, and state separately whether the Work used it. A comparison table may show promised and observed values, but it establishes neither Work, result, status, nor a verdict episteme.