serving: division actuation — wire DivisionPolicy to a consumer (the unique half of #2133) - #2246
Merged
Merged
Conversation
This was referenced Aug 11, 2026
Merged
#2 of the resident/cache split) The serving_daemon half of the contract (BigMama's DivisionPolicy fe624ea is the brain): discover the --resident-only tier manifests (#40) from the device-fit cache dir, warm-start a DivisionBandit over the feasible divisions, and publish the chosen resident-tier label as a fourth axis on the SAME governed plan file. Division of authority (compression): the LIVE device budget stays #305's board-derived axis — this never publishes a budget. It owns only the TIER choice; when a relaunch adopts a smaller resident, the board frees VRAM and #305's budget grows into it organically. Two-speed: publishing resident_tier never triggers a relaunch. Reward: the fork's trace-tail token watermark delta per tick = measured decode tok/s, credited to the tier the spawn ACTUALLY loaded (served_resident tracked at reconcile), never the bandit's latest unlaunched choice. Sub-64-token deltas rejected as noise; watermark resets (relaunch) re-seed silently. First measurement replaces the offline prior outright per the policy contract. Pure parts (manifest parse, discovery, shape derivation, reward loop) live in capacity/division_actuation.rs with 4 tests incl. the served-arm attribution and no-churn publish invariants. Probes: serving.division / serving.division_reward. Also resolves the platform_io/fs_portable duplicate from the canary merge to the ONE canonical fs_portable (compression rule). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LoTjvf5j3Ez13g6k8mRkFo
joelteply
force-pushed
the
feat/division-actuation-rescue
branch
from
August 15, 2026 03:25
fd9e32f to
26898b3
Compare
… a timer-noise floor, not a window shape The de-hardcode guard flagged it (correctly — undeclared token-count const in cognition-reachable code). But the constant gates reward-SAMPLE quality for the division bandit: a 3-token tick delta is timer noise, not a throughput measurement. Timer resolution does not scale with the served window, so a ContextBudget fraction would be the wrong shape. Declared via the guard's own exemption idiom with the reason inline. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LoTjvf5j3Ez13g6k8mRkFo
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.
Salvage of #2133 (31 commits, conflicting). Same adjudication as #2244: check what canary already has before resolving a single hunk.
What was superseded
fe624eaecDivisionPolicy — the governor's VRAM-division RL brain. Canary'score/expert-pager-policy/src/division.rsis 384 lines; the branch's version is 315. Canary carries a later evolution of the same file, so the branch's copy is behind, not ahead.What was NOT — and it's the interesting part
DivisionPolicyappears in exactly one file repo-wide in canary: its own definition. Zero consumers. The governor's division brain has been sitting in the tree unwired — the same built-but-never-called class we keep pulling on (cf. #2227,grid_budget/settlement,BenchmarkGradeModule).6e4782f91is the commit that wires it: the daemon consumesDivisionPolicy, addingcapacity/division_actuation.rs(+528/−3 across 4 files). That is the half worth rescuing, and it turns a dead policy into a live one.Verification
Cherry-picked onto canary, applied clean.
cargo check -p continuum-core --lib --testsclean.Correction on my own method
My first pass grepped
DivisionPolicyundercore/continuum-core/srconly, found nothing, and I nearly reported the whole feature as unlanded. It lives in a different crate. The narrow scope produced a confidently wrong conclusion — caught only because the cherry-pick conflicted on a file I had just claimed did not exist. Repo-widegit grep -lis the check; a crate-scoped one is not.