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

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:10:10 UTC

A.6:1 - Problem frame

At an API, protocol, hardware connector, organizational interface or published model, a reader needs to distinguish the declaration from the conditions of use and what occurred. FPF supplies these contributions:

  • U.Signature as a public, law‑governed declaration (with Vocabulary, Laws, Applicability).
  • U.Mechanism as a reusable operation declaration with OperationAlgebra, LawSet, AdmissibilityConditions and Applicability.
  • Multi-view describing through E.17.0 MultiViewDescribing, plus separate E.17 publication discipline for selected epistemes, face uses, forms, and carriers.
  • Recover each claim’s EntityOfConcern separately from its claim-bearing Description episteme and any publication carrier. The concern may itself be an episteme or carrier; its position does not establish agency, Work, evidence, or a decision.

A boundary account can blend these claims into one contract paragraph. Then a signature can acquire an unstated entry gate, a mathematical invariant can be read as a duty, or an effect can be asserted without its basis.

Connect the contributions in two steps:

  1. Distinguish declaration layers from claims about occurrences and their consequences or evidence, and from publication uses.
  2. Classify each boundary claim through A.6.B and place it where its governing content can be maintained and reused.

Terminology note (informative): In this pattern:

  • Layer names a position in the account: Signature, Admission, governance, consequence/evidence or Publication. Actual occurrences remain the subjects of claims rather than parts of their description.
  • View (U.View) is the same C.2.1 episteme individual when E.17.0 conformance to at least one exact viewpoint episteme obtains; it is not a projection operation, publication file, or document.
  • Viewpoint (U.Viewpoint) is the same C.2.1 episteme individual when the fixed E.17.0 viewpoint-convention conditions obtain; its accountability use does not replace those membership conditions.
  • Face (MVPK sense) is a publication form for a bounded reader/use. PlainView, TechCard, InteropCard, and AssuranceLane are face designators, not additional publication-face kind values. A face may expose an episteme that independently has U.View membership; the form, rendering and carrier remain separate from that episteme.