Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-21 14:31:57 UTC · snapshot created 2026-11-21 14:33:37 UTC · last check 2026-11-21 14:45:10 UTC

A.0:4.3 - Putting the glossary to use

  1. Recover the decision before choosing the table. Who will use the result, by when and with what authority? If they need one workable option, an existing candidate with established fitness may finish the job (C.38). A request for the best option also needs a comparison over the allowed alternatives. If the order calls for new candidates, generate them. For a decision left to the recipient, preserve the alternatives they can identify and use in time. Distinguish who set the goal, proposed the candidates and chose the criteria. When designing the search, make and justify the choices left open. When applying a supplied rule, credit those choices to whoever made them.
  2. Work out which choices have to fit together. Several recipients may choose independently, need the same option, or need every member of a combination. Compare whole combinations when a shared resource or condition affects their suitability. For one feasible combination, exhibit it or establish its existence as the request requires. To promise support for every allowed joint choice, establish a way for the participants to meet every such request. At each commitment the plan assigns an authorised action to each participant on the information that participant has. It must work in every situation still compatible with that information. The plan can branch on a distinction that reaches the participant in time. A declaration of agreed members needs the agreement. A report of actual use needs evidence of the work.
  3. Choose what to compare or count. Start with the candidates the commission allows, including ones beyond the current table. When designing a comparison, hold your proposed readings fixed and vary a permitted use or shared condition. If the recipient would have to act differently or give a different justification, retain that distinction or establish how the recipient can learn it in time. Group cases when the same answer and grounds hold (C.39.SA:4). State the eligible population, the question of quality, the admissible units and scales (CG‑Frame) and the ReferencePlane. Choose the Q components or DescriptorMap coordinates used by this operation and retain their meanings and applicable editions. Occupied cells describe a retained archive. A claim about which regions were tested needs evidence of the tests, including rejected candidates when they count. To report all nondominated answers, establish completeness for the requested population and distinguish objective values, one realization of each value, and all qualifying candidate identities (C.18:4.4).
  4. Use the method for the requested result. C.11 governs a local choice. C.18 supplies an archive or front. Use C.19 and record the E/E‑LOG policy‑id when the search needs explore/exploit control. Use G.5 for method-family dispatch or to declare a selected set on an established basis. Keep any consumed Front or Archive identifiable as the source. Return Shortlist or RankedShortlist for retained alternatives and JointUseSet when all named members are included for one use. A G.5 handoff, abstention or escalation carries its own grounds.
  5. Deliver what the recipient can use. Keep references to the criteria, evidence and editions used for the result (basis pins). To compare runs on common terms, also record the editions and policies that G.9 requires for that comparison (parity pins). Publish when the receiving use calls for publication, with the applicable PathIds/PathSliceId. Add a UTS row for a named governed value when F.17’s independent naming and reuse conditions hold. An Illumination Map remains report‑only telemetry by default.