docs(allocations): correct recursive-allocations page to match the engine (sc-22862)#242
Merged
Merged
Conversation
…gine (sc-22862) The page described a "Recursion mode: direct/reciprocal/iterative" config with convergence tolerance, maximum iterations, and a generation/iteration output column. None of that exists: there is no recursion_mode / reciprocal / convergence / iterative handling anywhere in plaidcloud.utilities or the plaid step schema, and the allocation-split step reference documents none of it. The page entered via a bulk generated docs PR (#159) and was never real. Rewrite it to describe how recursion is actually modelled — by chaining allocation split steps into explicit staged passes, with the author deciding the pass count (no native simultaneous solve, no auto-convergence). Evidence and verdict recorded on sc-22862.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
plaidcloud-docs | c07a2a1 | Commit Preview URL Branch Preview URL |
Jul 07 2026, 10:10 PM |
added 2 commits
July 7, 2026 22:38
…locations-sc22862
…locations-sc22862
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
1 participant
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
The Recursive Allocations guide documented a feature that does not exist.
It described a Recursion mode: direct / reciprocal / iterative config, a convergence tolerance, a maximum iterations cap, and a generation/iteration column on the output. Verified against the engine — none of it is real:
grepacrossplaidcloud.utilitiesand theplaidrepo forreciprocal/convergence/iterative/recursion_mode/convergence_tolerance/max_iterations→ zero hits.allocation-splitstep reference and theconfigure-an-allocationguide mention none of these fields.codex/control-plane-docsPR (Add control plane administration docs #159) and was never grounded in the product.A customer following the old page would look for a "Recursion mode" control that isn't there.
Fix
Rewrite the page to describe how recursion is actually modelled in PlaidCloud: by chaining allocation split steps into explicit staged passes, where the author decides the pass count. There is no native simultaneous (reciprocal) solve and no automatic convergence loop.
Verdict recorded on sc-22862
Reciprocal/iterative allocation is not natively supported — expressible only as hand-authored staged passes. Competitive positioning: "at par on multi-step ABC modelling; reciprocal = manual staged passes, not a native solver."
🤖 Generated with Claude Code