B.5.3:6 - Consequences

Benefits	Trade-offs / Mitigations
Domain language stays usable: Experts keep familiar words without forcing every word into the kernel.	Recovery overhead: A load-bearing expression needs its exact source-local claim and governed value. Keep the returned explanation short; recover F.17 cells and their basis relations for claims that need them, including F.9 Bridges, and add durable rows only when reuse needs them.
Kernel stays lean: New kinds require explicit admission and ontic support.	More precise modeling choices: The bridge may reveal that one local word hides several FPF values. That is the point: split them before they drive work.
Cross-document clarity: Requirements, diagrams, dashboards, simulations, and reports can be compared without pretending they are the same artifact.	Need for an exact use boundary: Do not reuse a source-local claim or semantic relation in another project, scheme, scope, or action without checking the actual changed values, tolerated loss, and reliance basis.