Repository navigation
docs: add saved research context for manual Black-Litterman views - #777
Open
alexander-schneider wants to merge 1 commit into
Open
alexander-schneider wants to merge 1 commit into
alexander-schneider wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Show how saved external research can document manually selected Black-Litterman
views without turning sentiment scores into expected returns or confidences.
Following the scope boundary described in #748, this adds no provider client.
What changed
bundled price data, with annual assumptions and explicit ticker alignment.
reordered confidences, and rejection of missing nullable confidences.
Scope
Only documentation and its tests change. There is no account requirement,
network request, SDK, dependency, automatic view calibration, or core change.
The fictional research dates do not assert actual provider coverage or
point-in-time availability. This is not an investable backtest.
Blast Radius
Existing model behavior stays unchanged. The example uses manually chosen
returns/confidences; changing sentiment alone cannot change the model result.
I work on Adanos, a commercial API with a limited free
plan. This contribution used AI assistance and includes no actual provider data.
Verification
checked independently; Ruff lint and format checks passed.
block matches current source and executes with the expected results.
submission. The nullable-confidence finding was fixed with a failing
regression first, then both reviews were repeated on the complete change.
No full suite, live API, cross-version matrix, or upstream CI result is claimed.