A.6.S:2 - Problem
FPF needs a pattern for engineering signatures as boundary epistemes: a disciplined way to construct, revise, and publish a target U.Signature from partial input, while maintaining:
- separation between signature and mechanism (A.6.0 vs A.6.1),
- separation between laws, admissibility, deontics, and work evidence (A.6.B),
- explicit multi‑view publication without semantic drift (E.17),
- reproducible evolution across editions without silent mutation.