A.16.0:13 - Worked trajectories
A.16.0:13.1 - Multi-route state before fork
A routed operator cue may first keep intervention and inquiry routes live for one selected episteme edition in one RoutedCueSet. That is still a multi-route state. A lineage fork exists when independently identified distinct successor epistemes and the actual historical facts satisfy the selected fork predicate. Both successors may still be unpublished. Conversely, publishing the same edition twice creates two publication claims, not a fork.
A.16.0:13.2 - Inquiry trajectory with fork
An inquiry cue pack centered on a felt or trace-anchored discrepancy cue may first identify one selected episteme edition, then fork into:
notice -> stabilize -> route -> projection -> formalize, with a cue-derived prompt form expressing the explanatory branch, andnotice -> stabilize -> route -> projection -> operationalize
if one branch supports explanatory work while another supports immediate probe or control work. The account of that fork identifies the successor epistemes and obtaining lineage links, and discloses each branch’s relevant losses and next-use conditions. These disclosures describe the fork; their publication does not create it. If responsibility actually changes, keep the separately established responsibility-handoff conditions distinct as well.
A.16.0:13.3 - Operator trajectory with retirement
An operator alert note about a service disturbance may move:
notice -> stabilize -> route -> projection -> operationalize
If later evidence no longer supports one route, the admissible continuation may include explicit retirement of that branch rather than silent disappearance. The retirement does not erase the prior branch; it ends the retired branch’s current use and preserves continuity explicitly. Any authority change still requires the separate relation in §4.6.
A.16.0:13.4 - Bridge-sensitive trajectory
A route-bearing comparative note may move through a seam publication and only later dock to a bridge overlay or viewpoint bundle. The bridge or viewpoint attachment does not replace the trajectory account; it annotates or re-expresses a lineage that already exists.