Files

T

retoor af080fe68e Strict goal verification, approval hardening, retrieval eval, work limits, sandbox caps (1.38.0)

- Approval: re-prompt unknown answers (max 3), shell-only affirmative
  guidance recovery; destructive actions stay strict
- GoalVerifier subagent with strict JSON verdicts, bounded follow-up
  rounds, nonzero exit plus open turn on unverified one-shots
- Retrieval eval (Hit@K/MRR/nDCG/Context Precision), FTS cascade with
  title weighting, query/read event logging, --eval-retrieval CLI
- Supervisor caps (8 parallel, 64 records) and scheduler hardening
  (4 fires/tick, per-schedule lease, stated misfire policy)
- Sandbox box resource trio: 2g/2.0/256 at create, best-effort
  update for existing boxes, rm -f recovery pointer
- Research archive: 12 subjects, 667 sources, 27 conclusions;
  suites 979 + 16 green

2026-10-18 12:13:24 +02:00

1.0 KiB

Raw Blame History

How to Limit CPU and Memory Usage in Docker Containers

Metadata

Field	Value
Institute	Molodetz Institute — Research & Retrieval Division
Subject	sandbox-resource-caps
Document type	Source Citation Card
Tier	2
Source title	How to Limit CPU and Memory Usage in Docker Containers
Source URL	https://medium.com/codex/how-to-limit-cpu-and-memory-usage-in-docker-containers-a024b429f55e
Source type	blog post
Date researched	2026-10-18
Researched by	tai (agent), model: Muse Spark, on behalf of retoor
Research method	Search aggregator result listing (not independently opened or quoted)
Confidence	Not independently verified
Status	Active

Why it's here

Surfaced by the container-limits search; the snippet documents --cpus and --memory plus the --memory-swap total. Noted for the swap caveat carried in the conclusion; seen only as a snippet.

Changelog

Date	Change
2026-10-18	Logged as consulted-but-not-analyzed.

1.0 KiB Raw Blame History

How to Limit CPU and Memory Usage in Docker Containers

Metadata

Why it's here

Changelog

1.0 KiB

Raw Blame History