FPF Reference

A.6.8:4.9 — Disambiguation guide (rewrite/selection)

Preface node heading:a-6-8-4-9-disambiguation-guide-rewrite-selection:14637

Content

If the draft says:

  • “the service is deployed/restarted/scaled/called” → rewrite as service access point (system) or service delivery work (deployment work), and (optionally) attach it to a serviceSituation.
  • “the service promises/guarantees X” → rewrite as promise content (promise content), and if “guarantees” is deontic, also introduce service commitment held by the service provider principal.
  • “the service is down/slow/has 5xx” → rewrite as service access point (down) and/or service delivery work (incident/run), with evidence.
  • “we promised the service” / “we agreed the service” → rewrite as service promise act + promise content (+ commitment if binding).
  • “the service provider guarantees X” → rewrite as service provider (role enactor) + service commitment (+ promise content as payload).
  • “the server is down / slow / restarted” → rewrite as service access point (server/host system) and/or delivery work, not as clause.
  • “the service is implemented by / realized by / works by doing Y” → rewrite as service delivery system and/or service delivery method (and keep the clause separate as the outcome constraint).
  • “the service API signature / endpoint schema / request format is …” → rewrite as service access spec.
  • “the service ticket / service request” → rewrite as ticket / request work item; “service” is adjectival legacy and must be eliminated or mapped via LEX.