Obtaining relations selected by G
The following local predicates concern written descriptive content. Their meanings, participant order and basis are part of this scheme. They introduce no reusable relation signature or global ontology.
| Occurrence | Predicate and participants in order | Why it obtains in this illustrative content |
|---|---|---|
| rKT: K addresses T | addresses(controller-design description, task requirement): the first description explicitly identifies the second as the task whose execution it organizes. Participants: first K, second T. | K explicitly says “for T” and supplies its consumption, observation and execution design for that requirement. |
| rNT: N is required by T | requiredContribution(contribution description, task requirement): the second description explicitly requires the contribution designated by the first. Participants: first N, second T. | T explicitly requires the currently applicable procedure designated by N. |
| rQN: Q seeks N | seeks(acquisition proposal, contribution description): the proposal identifies the contribution description as what its acquisition is to supply. Participants: first Q, second N. | Q explicitly asks the named service for the current edition and applicability of the contribution designated by N. |
| rRK: R targets K | targets(repair proposal, controller-design description): the proposal explicitly identifies the description whose realization it proposes to revise. Participants: first R, second K. | R explicitly selects K’s consume/reopen transition as its repair target. |
These relations obtain because the descriptions have that content. They do not assert an acquisition, repair or state change has occurred. A missing selected relation leaves this formal identity provisional; the ordinary explanation can remain usable. The case facts below do not manufacture the relations.