feat(#510): enforce thesis confidence rules#548
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3f55f8ba94
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| requestedConviction: input.conviction, | ||
| priorConviction: existing?.conviction, |
There was a problem hiding this comment.
Preserve original requested conviction in confidence telemetry
recordInvestingThesisRevision now re-evaluates confidence from input.conviction, but the thesis-refresh automation passes draft.conviction (already capped by the first confidence pass) into this function, so persisted confidence.requestedConviction is flattened to the already-downgraded value. In scenarios where an existing thesis carries high conviction and new evidence only supports medium/low, the stored confidence block and investing.thesis.confidence event no longer record that a downshift occurred, which breaks the new audit trail semantics for requested vs applied conviction.
Useful? React with 👍 / 👎.
Summary
thesis-confidence.v1to cap conviction from evidence coverage, tool diversity, and linked valuation context while surfacing the rule in thesis snapshotsTesting
Closes #510