A.16:4.5 - Work crossing and actual relation changes

Some formalize and operationalize moves only re-express available content. Others require measurements, experiments, installation or use of instrumentation, execution, or other dated U.Work. In the latter case, expose the boundary and use the applicable Work, measurement, experiment, gate, or endpoint pattern. A.16 records the pending or separately established crossing; it does not claim that Work occurred or produced a result.

Next-use docking and a Work crossing do not by themselves establish a change in authority, responsibility, permission, or commitment. If one of those relations actually changes, record it as a separate claim: the exact relation under its governing pattern; participants in that relation’s own roles, including exact giving and receiving admitted systems when its predicate requires them; any exact U.SystemRoleAssignment occurrences through which they participate; its object or action, scope, and effective interval; and the assigning, instituting, revoking, or superseding act when its pattern requires one. A.2, A.2.1, and the applicable deontic or authority pattern establish and test that claim.

Use A.16.0 for such a handoff only when its legitimacy or interpretation depends on upstream move or lineage history. Otherwise the local Work-boundary note and separately established relation are enough.