fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 5087–5096

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:00:09 UTC

A.2.3:9 - Common misclassification repairs

  • A microservice label is being used for the whole service claim. Use A.6.P:4.11a to recover whether the source word denotes service-provision Work, a Method, PromiseContent, provider participation, or an exact deployed process, component, endpoint, application, host, or cluster. Apply A.1 or A.1.SCR only when a repaired bearer claim depends on systemhood. Deployment and the label establish neither membership nor a delivery-system or access-point boundary; the consumer-facing outcome and acceptance claims remain in U.PromiseContent.
  • An API label is being used for the whole service claim. If the referent is an interface specification, use the exact episteme and U.MethodDescription only when A.3.2 admits it. If it is an addressable endpoint, recover that bearer through A.6.P:4.11a and apply A.1 or A.1.SCR only when a current claim depends on systemhood. Neither the API label nor addressability establishes membership, and neither referent is the promise-content episteme.
  • A process or procedure label is being used for the whole service claim. Recover the semantic way of doing as U.Method, its description as U.MethodDescription, planned work as U.WorkPlan, and performed occurrences as U.Work. Keep the promised outcome and acceptance claims in U.PromiseContent.
  • A ticket or case record is being used for the whole service claim. Recover its claim-bearing content as a ticket or case-description U.Episteme; keep the publication form and U.PresentationCarrier separate. Relate that episteme to the named U.WorkPlan or U.Work occurrence it describes.
  • Cost or elapsed time is attached to the promise content. Keep resource and time actuals on the performed U.Work occurrence. Derive a measure over work occurrences participating in PromiseContentUse only through its declared characteristic, C.16 measurement template, named A.10 evidence relations, aggregation rule, and Gamma_time policy; cite a U.MethodDescription when a particular measurement method affects the reading.
  • Promise content is placed in a product or system breakdown. Keep the promise content as an episteme. The access and delivery systems may have parts and selected structures under A.22 and C.30; the promise-content episteme is not one of those parts.
  • A person or organization name is stored as the provider system-role kind. Identify the exact local provider system-role kind through providerSystemRoleKindRef. If an actual provider-assignment claim is current, identify the exact person or organization and apply A.1 because A.2.1 requires an admitted holder U.System; otherwise do not create the assignment. Then state one named occurrence of a directly declared species under U.SystemRoleAssignment and its explicit interval.