fix(context): inherit role capacity instead of local total-window clamps #497
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/local-context-inherit-window"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The user's <5K goal concerns BASE overhead, not total input. Yet local models implicitly received additional 16K Main / 8K child context targets. Under Minerva 0.1.338, real native compactions now succeed and tools continue, but some sessions compact repeatedly around 7–9K reported usage; others remain around 25K after multiple summaries. A smaller locality default does not make irreducible relevant task context fit and wastes summary calls.
Change
Locality alone now inherits the ordinary configured Main/worker budget. Keep existing optional localMainContextTokens/localWorkerContextTokens as explicit stricter operator targets; validate supplied values as before. Preserve configured role/physical/native limits, output headroom, independent assessment, safe handover, authorization and routing. No new input gate, tokenizer request or model dependency.
Existing configs that explicitly pin 16K/8K are NOT silently overridden. Minerva's separate shared PR #142 deliberately matches its existing role budgets and is compatible with already installed Core.
Tests
This changes context policy defaults, not a claim of <5K production base overhead, reduced live compaction frequency or business completion.
PI-REVIEW-RECEIPT
State: PASS
Head:
a790a752fb60Summary: PASS: No actionable findings identified in the supplied diff.
Findings: 0