Jump to text
On this page
Copy and source
Upstream freshness not yet confirmed

Source changed 2026-11-22 00:35:13 UTC · snapshot created 2026-11-22 00:40:27 UTC · last check 2026-11-22 01:12:03 UTC

A.6.2:1 - Problem frame

FPF repeatedly needs to relate one episteme to another, often alongside a separately described operation that produced the receiving episteme:

  • turning an informal method description into a more formal specification;
  • projecting a large system description into a smaller “for‑safety‑officer” view;
  • re‑expressing the same behavioural model in a different calculus or notation;
  • relating an analysis about one subsystem to an analysis about another; use A.6.4 for a claimed receiving use and for judging a current case against its bounded-use assertion.

All of these can be described by episteme-to-episteme mathematical arrows. The arrow relates epistemes and states its laws; it does not itself change an episteme, measure, execute, or actuate. Any operation application and Work remain separate.

Without one reusable local discipline for such arrows:

  • each family (KD‑CAL, E.18, MVPK, discipline packs) reinvents its own notion of “projection”, “reinterpretation”, or “refinement”;
  • laws about which parts of the source and receiving epistemes may differ, and which grounding or reference-plane facts their rules read and compare, fragment across the spec;
  • cross‑family reasoning (e.g. “this E.18 structural reinterpretation is a retargeting, not a view”) becomes brittle and ad‑hoc.