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

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:10:20 UTC

A.6.F:4.1 - Trigger rule

When function-like wording remains ambiguous, distinguish the readings below. They are possible meanings to inspect, not a U.* kind, claim kind, relation kind, or admission result:

One phrase may combine several readings or transfer metonymically between them. Recover the claim it makes and retain every distinction that changes its use.

  • architecture or functional architecture;
  • capability, effect, externally promised behavior, or user-visible functionality;
  • method wording, work occurrence, or work result;
  • a system-role kind or assignment, participation, actual functioning, or responsibility;
  • mathematical function, mapping, relation, loss, objective, or value functional;
  • quality, fitness, characteristic, score, or proxy wording;
  • module allocation, interface, signature, port, API, protocol, flow, or mechanism relation;
  • another independently established claim named by value, such as evidence, assurance, gate, decision, or release.

If none of those readings carries a current FPF claim, the wording may remain ordinary Plain prose.