{
  "api_version": "v1",
  "id": "memory-pressure-resilience-2026-10-29",
  "title": "Bounded host and container swap for memory-pressure resilience",
  "publisher": "Darkoza Knowledge Lab",
  "published_at": "2026-10-29",
  "evidence_status": "host swap and container swap allowance applied; live system state verified",
  "report": "https://darkoza.com/science/reports/memory-pressure-resilience/report.html",
  "audit": "https://darkoza.com/science/reports/memory-pressure-resilience/audit.json",
  "changes": {
    "host_swap_bytes": 4294963200,
    "vm_swappiness": 10,
    "target_container_ram_limit_bytes": 4294967296,
    "target_container_memory_plus_swap_limit_bytes": 8589934592,
    "target_container_swap_limit_bytes": 4294967296,
    "container_restarted": false
  },
  "verification": {
    "docker_active_after_change": true,
    "oersi_autonomy_loop_active_after_change": true,
    "backup_timer_active_after_change": true,
    "disk_available_after_approx_gib": 41,
    "backup_free_space_guard_gib": 25
  },
  "limitations": [
    "Swap cannot prevent all out-of-memory events.",
    "The active memory working set can still exceed the container's RAM limit.",
    "Heavy swapping can significantly reduce model inference performance.",
    "A future container recreation must preserve the combined memory-plus-swap allowance."
  ]
}