#A.6.B:1 — Problem frame

Preface node heading:a-6-b-1-problem-frame:7025

#Content

Boundary descriptions routinely collapse four distinct claim families into “contract soup”: definitions are written as obligations, runtime gates are hidden inside laws, governance talk is assigned to “the interface”, and “guarantees” are asserted without any evidence story. The resulting boundary is brittle: substitution becomes unclear, and auditability becomes performative rather than adjudicable.

FPF already separates the necessary strata (Signature vs Mechanism, Object≠Description≠Carrier, views under viewpoints). What is still needed is a single, reusable routing primitive that any boundary text can apply consistently and that other patterns can cite as a stable authoring module.