11. Use current pointers without losing source identity

The manual index has stable anchors for the management manual, Field Book and this guide. Those links answer “where is the current edition?” They do not answer “which edition supported this earlier decision?”

For ordinary discovery, use the stable index. When a requirement, comparison or accepted result depends on exact wording, identify the resolved edition and source revision. Existing Git provides the bytes; add a content hash only when a consumer requires one.

A changed index does not automatically amend App v4's product requirements or historical test fixtures. Update affected current consumers deliberately. Preserve the earlier edition while a live consumer still requires its bytes.

A source update can change language without changing meaning, or change the actual method. Compare the relevant sections and consequences. Do not substitute a new edition merely because its version number is higher.