diff --git a/reference/configuration/options.md b/reference/configuration/options.md
index 84b34767..22b7b9f1 100644
--- a/reference/configuration/options.md
+++ b/reference/configuration/options.md
@@ -404,6 +404,23 @@ agent:
 
 ---
 
+## `deployment`
+
+Retention for what `deploy_component` leaves behind. See [`deploy_component`](../operations-api/operations.md#deploy_component).
+
+```yaml
+deployment:
+  payloadRetention:
+    maxSize: 10485760
+  stagingRetention:
+    maxCount: 5
+```
+
+- `payloadRetention.maxSize` — Bytes. After a successful deploy, a payload larger than this has its stored tarball (`payload_blob`) dropped from the `hdb_deployment` row; the row and its metadata stay. Set it very high to retain every payload; _Default_: `10485760` (10 MiB)
+- `stagingRetention.maxCount` <VersionBadge version="v5.3.0" /> — How many complete, unactivated staged builds may remain per component under `<componentsRoot>/.deploy-staging`. The newest survive; older ones are removed at the start of that component's next deploy and at startup, and `drop_component` removes all of them. `0` keeps none. This bounds dormant builds only, not a disk quota: staging directories that belong to an in-flight or unsettled deploy are never touched; _Default_: `5`
+
+---
+
 ## `applications`
 
 Added in: v5.0.0
diff --git a/release-notes/v5-lincoln/5.3.md b/release-notes/v5-lincoln/5.3.md
index bda4cd88..1dc7e574 100644
--- a/release-notes/v5-lincoln/5.3.md
+++ b/release-notes/v5-lincoln/5.3.md
@@ -20,6 +20,12 @@ Replication URLs now also bracket a bare IPv6 literal correctly (`::1` becomes `
 
 See [Configuration Options](/reference/v5/configuration/options#node).
 
+## Component Deploys
+
+### Staged Build Retention
+
+`deploy_component` builds each release under `<componentsRoot>/.deploy-staging/<deploymentId>` and validates it before swapping it live. A build that completes but is never activated now survives startup, bounded per component by the new `deployment.stagingRetention.maxCount` setting (default `5`; `0` keeps none). Older builds are removed at the start of the component's next deploy and at startup; anything belonging to an in-flight or unsettled deploy is never touched. Groundwork for deploying from an already-staged build ([harper#2315](https://github.com/HarperFast/harper/issues/2315)). See [Configuration Options](/reference/v5/configuration/options#deployment).
+
 ## Security
 
 ### Route-Owned Authentication