Objective: Provide a reusable, structured method for locating any note within the JSONHTL notes system before resorting to external sources such as email.
1. Attempt direct lookup of likely canonical keys based on naming conventions (e.g. projects/{name}/index, projects/{name}/plan, users/{name}/preferences).
2. Consider singular vs plural variants and common structural patterns defined in the notes naming guidelines.
3. Inspect the main CONTENTS index for relevant links.
4. Check project index notes and bundles/{topic} notes for references to the target document.
5. Search within the logical namespace (e.g. projects/{project}/) for semantically related terms.
6. Review recently modified or thematically related notes for cross-references.
7. If the note cannot be found in the notes system, search email folders for relevant subject lines or references.
8. If content exists only in email, extract and normalise it into a properly structured JSONHTL note under an appropriate canonical key.
9. Confirm the located or reconstructed note is complete and correctly structured.
10. Record the discovery process in a persistent execution log when the search process itself is material to system understanding or audit clarity.