docs: Drafting tech spec for modeling retrieval evals

[fg-nava]

• Update PR Title to follow this pattern: [INTENT]: [MESSAGE]

The title will become a one-line commit message in the git log, so be as concise and specific as possible -- refer to How to Write a Git Commit Message. Prepend Conventional Commit intent (fix:, feat:, chore:, ci:, docs:, style:, refactor:, perf:, test:).

Ticket

https://navalabs.atlassian.net/browse/DST-<TICKET_NUMBER_HERE>

Changes

What was added, updated, or removed in this PR.
Prefer small PRs; try to limit to 300 lines of code changes

• https://blog.logrocket.com/using-stacked-pull-requests-in-github/
• https://opensource.com/article/18/6/anatomy-perfect-pull-request
• https://developers.google.com/blockly/guides/modify/contribute/write_a_good_pr

Context for reviewers

Background context, more in-depth details of the implementation, and anything else you'd like to call out or ask reviewers.
Add comments to your code under the "Files Changed" tab to explain complex logic or code

• https://betterprogramming.pub/how-to-make-a-perfect-pull-request-3578fb4c112

Testing

Provide evidence that the code works as expected. Explain what was done for testing and the results of the test plan. Include screenshots, GIF demos, shell commands or output to help show the changes working as expected. ProTip: you can drag and drop or paste images into this textbox.

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
2959	2654	90%	80%	🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: 5603f7f by action🐍