E.10.MOVE:4.2b - Trajectory wording recovery
Use this branch when trajectory or close path wording remains claim-bearing after any primary transformation wording has been recovered. The first result is an ordinary repaired claim or exact gap, not a trajectory record.
Ask only the questions the receiving use needs:
- What exact bearer or represented subject is positioned or ordered?
- What identity, continuity, membership, lineage, or edition rule matters?
- Which declared position, state, configuration or possibility space is relied on, if any? Name a defining episteme edition separately when the use depends on it.
- What is the ordering or reference domain—time, event, generation, plan order, graph order, or another index?
- What counts as a position, segment, branch, interval, generation, or edge for this use?
- What posture does the claim need—for example, actual, observed, reconstructed, predicted, simulated, proposed, recommended, or planned?
- Which direct pattern owns the resulting claim, what receiving use is allowed, and is any grounded non-use boundary needed under the
F.19plausible-intended-reader test?
These are recovery questions, not fields of a new Trajectory, TrajectoryAccount, relation head, Method, or mandatory card.
| Recovered trajectory use | Direct exit and boundary |
|---|---|
| Actual or reconstructed history of one identified subject | A.3.4, A.3.4.P, B.4, C.27.TA, and A.10 as applicable. A plotted sequence or intervention does not establish actual change or continuity. |
| Predicted or simulated state history | A.3.3, A.19, C.27, and C.29; name model edition, state space or position space, transition law, validity boundary, and posture. Model output is not actual history. |
| Proposed, recommended, or planned route | C.22.2, C.11.CRC, C.11, A.15.2, and the domain Method. Recommendation, choice, WorkPlan, performed Work, and effect remain separate. |
| Population or lineage history | C.36 only for the cultural case; otherwise use an admitted domain owner or return the named non-cultural population or lineage architecture gap. Do not model membership turnover as one-holder continuity. |
| NQD/OEE search history, archive or front succession, or possibility-space projection | C.17–C.19, G.5, G.11, and C.29 as applicable. An archive is not automatically a population. |
| Language-state history needed by a responsibility question | A.16.0 supplies an ordinary account of the relevant source editions, position claims, moves, lineage and losses. Any actual responsibility change needs its independently governed participants, scope, time and instituting facts under §4.6; language-state movement does not supply that relation. |
| Mathematical trajectory lens | C.29 for the selected representation and explicit correspondence, with declared losses; keep the represented subject under its direct owner. |
| Ordinary or quote-only wording | Preserve it and stop unless a later FPF use relies on a stronger claim. |
For development trajectory, open E.10.DEV first when the action-changing doubt is what develops, what remains identifiable, or whether improvement is asserted. Continue here only if trajectory still carries an independent claim about position, ordering, posture, or representation. If the bearer and development claim are already clear and only path posture is unresolved, start here and open E.10.DEV afterward only for a remaining separate ambiguity. Do not require two notes or two full passes by spelling alone.