docs(tracing-allocations): add driver what-if (allocation_driver_scenario)#241
Merged
Conversation
…ario) The allocation-tracing guide covered value-change what-ifs (forward_impact) but not the new driver-reweight what-if (allocation_driver_scenario, sc-22833/22859), and one caution still said the agent declines a driver change — it no longer does. - Add the driver what-if to the What You Can Ask table. - Split the what-if caution into value-change (proportional, additive) vs driver (exact reslice, nets to zero, declines outside its exact domain). - Add a Tips bullet distinguishing the two.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
plaidcloud-docs | 0a6d709 | Commit Preview URL Branch Preview URL |
Jul 07 2026, 09:50 PM |
simozzy
pushed a commit
that referenced
this pull request
Jul 7, 2026
… notes Complements #241 (which documents the allocation_driver_scenario driver what-if in the Tracing Allocations guide). This adds the parts #241 doesn't: - Tracing Allocations guide: a caution that a clean-looking whole-pool total can mislead — an offsetting churn (large ups and downs netting small) or a change that is mostly pass-through the driver never split (sc-22859, sc-22911). - July 2026 release page: an Added bullet for the driver-reweight what-if and a Changed bullet for the two new confidence signals.
simozzy
pushed a commit
that referenced
this pull request
Jul 7, 2026
… notes Complements #241 (which documents the allocation_driver_scenario driver what-if in the Tracing Allocations guide). This adds the parts #241 doesn't: - Tracing Allocations guide: a caution that a clean-looking whole-pool total can mislead — an offsetting churn (large ups and downs netting small) or a change that is mostly pass-through the driver never split (sc-22859, sc-22911). - July 2026 release page: an Added bullet for the driver-reweight what-if and a Changed bullet for the two new confidence signals.
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.
What
Updates the Tracing Allocations guide to cover the new driver what-if capability (
allocation_driver_scenario) and corrects a caution that's now out of date.Why
The guide documented the value-change what-if (
allocation_forward_impact) and the confidence/caveats honesty layer, but not the driver-reweight what-if that shipped since (sc-22833, refined by sc-22859). One caution still told users the agent declines a driver change — it no longer does; it reslices the split exactly.Changes
allocation_driver_scenario).Matches the shipped tool behaviour (
allocation_forward_impact= proportional/additive;allocation_driver_scenario= exact, conserving, declines outside single-stageallocation_splitwith a sum driver).No release-notes entry yet — these are still
Unreleasedon the product side (not in a tagged tenant version).🤖 Generated with Claude Code