diff --git a/docs/recovery/onboarding-disposition-2026-08-24.md b/docs/recovery/onboarding-disposition-2026-08-24.md
index e616587..bdccaae 100644
--- a/docs/recovery/onboarding-disposition-2026-08-24.md
+++ b/docs/recovery/onboarding-disposition-2026-08-24.md
@@ -3,11 +3,11 @@
 CUST-WP-0067-T05, 2026-08-24. Of the 44 cache-only repository records, 33 were
 onboarded to central via `rmgr repo-onboard`. Central went from 78 to 111
 repositories. These 11 did not, each for a reason that needs a decision rather
-than a retry.
+than a retry. One (`agent-harness`) has since been decided: dropped.
 
 | Repository | Reason | Needed |
 |---|---|---|
-| `agent-harness` | no working copy on this machine | restore from remote, or drop |
+| ~~`agent-harness`~~ | no working copy on this machine | **dropped 2026-08-25** — see below |
 | `binky-control` | no `.repo-classification.yaml` | author with the repo owner |
 | `clay-borg` | no `.repo-classification.yaml` | author with the repo owner |
 | `direkt-vermittlung-de` | no `.repo-classification.yaml` | author with the repo owner |
@@ -36,9 +36,28 @@ uv run --project ~/repo-manager rmgr repo-onboard \
   --path ~/soul-frame --api-base http://127.0.0.1:8000
 ```
 
-`agent-harness` has no working copy here at all and must be restored from its
-remote or explicitly dropped. Do not preserve it as a hub-only record — that is
-the `ADR-001` violation `ADR-010` calls out.
+### `agent-harness` — dropped (2026-08-25)
+
+Decided by Bernd Worsch: the repository is superseded by `glas-harness` and the
+`rein` concept, so there is nothing to restore. It is therefore **not** onboarded
+to central, and its cache-only record is left to disappear when the local cache
+database is discarded. Preserving it as a hub-only record would be the `ADR-001`
+violation `ADR-010` calls out — a hub record with no backing file that nothing
+can re-derive.
+
+Successors verified present and classified on central before dropping:
+
+| Successor | Domain | Category |
+|---|---|---|
+| `glas-harness` | infotech | tooling |
+| `rein-aharness` | agents | tooling |
+
+`rein-openweights` is part of the same concept but is still awaiting a
+classification file, so it remains in the outstanding set below rather than
+counting as a landed successor.
+
+This is the one record of the 44 that is deliberately *not* recovered. Nothing
+else in the export should be dropped without an equivalent decision.
 
 ## Classification is deferred for all 33
 
diff --git a/workplans/CUST-WP-0067-hub-authority-target-resolution.md b/workplans/CUST-WP-0067-hub-authority-target-resolution.md
index f5b48eb..5e63c46 100644
--- a/workplans/CUST-WP-0067-hub-authority-target-resolution.md
+++ b/workplans/CUST-WP-0067-hub-authority-target-resolution.md
@@ -294,8 +294,9 @@ written disposition; only then may the local cache database be discarded.
 repositories. The remaining 11 each carry a written disposition in
 `docs/recovery/onboarding-disposition-2026-08-24.md`: nine need a classification
 file authored with their owner, `soul-frame` has unpushed research commits that
-are the owner's to publish, and `agent-harness` has no working copy and must be
-restored or explicitly dropped.
+are the owner's to publish, and `agent-harness` was **dropped on 2026-08-25** by owner decision — superseded by
+`glas-harness` and the `rein` concept, both verified present and classified on
+central first. Ten records remain outstanding.
 
 None were forced. Classification is not mechanical (`CUST-WP-0065-T01`), and a
 confident wrong domain is harder to correct than a missing one.