Dashboardopencode-loreUse fail-closed, monotonic embedding me…

Use fail-closed, monotonic embedding memory admission

Category: preference
Confidence: 0.80
ID: 01a0aee2-659f-7e18-95fd-f791f1e93919
Project ID: 6f4be9ff-ed84-4cca-a9e7-732a0b0b8677
Cross-project: No
Recalled in other projects: 0
Source session: 1JmtIdaVnn5PTPdxS
Created: 2026-09-17 09:59:32
Updated: 2026-09-17 10:21:07

Content

When modifying embedding memory sizing or worker admission, preserve strict safety invariants: reread cgroup membership and mounts for every decision, use the tightest valid headroom across inherited boundaries and runtime limits, and return unknown/deny growth when required data is stale, malformed, ambiguous, or unreadable. Never let clamping increase the original free-memory figure. Account for each worker’s full model/runtime baseline so pool growth cannot multiply pressure or reuse headroom reserved by a starting or retiring worker. Keep one primary worker where required, but gate all additional workers conservatively. Add focused tests for constrained, unlimited, zero, invalid, changing, and low-headroom cases, including exact boundary values and assertions that results never exceed host-free memory.

Move to: