Search and read

Use rg (ripgrep), or the environment’s equivalent search tool with regular expressions. Run these commands with the public distribution folder as the working directory, or prepend its actual path to the file arguments. In a source repository, limit the search to the selected public publications; campaign notes and historical drafts are not the public corpus.

Inspect the available Markdown files once to establish the search scope. This lists filenames; it does not search their contents:

rg --files --no-ignore -g '*.md' .

For the illustrative question “obtain a needed engineering result: build or buy”, search the text across that scope:

rg -n -i -C 2 --no-ignore -g '*.md' -- 'build or buy|obtain a needed engineering result|obtain climate control' .

This query can return a pattern, a contents row and a connected Reference case. Compare the question each passage answers, open its enclosing section and retain the useful result or return condition. If the output is too large, use the same query with -l instead of -n -C 2 to list matching files, then inspect promising passages. Reformulate an unsuccessful query; a lexical match alone does not establish fit, and no match does not establish that the method is absent.

A browser or retrieval system can serve the same search when it covers the declared publications, including Reference answers. If it exposes only one file or titles, state that limit and extend access when the question requires it.

Locate the file and the start and end lines of the selected pattern:

rg -n --no-ignore -g '*.md' '^## SYSE\.24 |^### SYSE\.24:End[ \t]*\r?$' -- .

Read that pattern in full:

rg -U --no-heading --no-line-number --no-filename --color never '(?ms)^## SYSE\.24 [^\r\n]*\r?\n.*?^### SYSE\.24:End[ \t]*\r?$' -- "Engineering DPF Suite/SYSTEMS-ENGINEERING-PRINCIPLES-FRAMEWORK.md"

Here -U enables multiline search; (?m) makes ^ and $ match line starts and ends, and (?s) lets a dot match a newline. (?ms) combines them. .*? matches through to the nearest specified :End heading; \r?\n accepts Windows and Unix line endings. Substitute another ID and file as needed; escape literal dots in IDs as \..

For other searches, -F treats the query as literal text, -i ignores case, and -C 2 includes neighbouring lines. --no-ignore searches files even in a Git-ignored folder; -g '*.md' selects Markdown files.

If the tool truncates a long result, read the selected text in successive line ranges with the available file reader. Folder search already covers separate publications; no combined file is needed.