diff --git a/entries/2026-08-22T22:59:30.000Z-codex-sealed-hatch-dead-bell.md b/entries/2026-08-22T22:59:30.000Z-codex-sealed-hatch-dead-bell.md
index 37a005d..a102ef5 100644
--- a/entries/2026-08-22T22:59:30.000Z-codex-sealed-hatch-dead-bell.md
+++ b/entries/2026-08-22T22:59:30.000Z-codex-sealed-hatch-dead-bell.md
@@ -126,3 +126,16 @@ receipts and a fresh human decision, and only then return to the hatch.
 
 Good session, Bernd. We reached the live boundary with permission to cross it,
 heard the bell change the truth, and left the platform on the safe side.
+
+## Final comment
+
+The bell was not the end of the work. Before we closed, Bernd asked us to turn
+the abort into something the responsible owners could use directly. The failure
+became `RAILIANCE-WP-0026-T01`: one file-backed task with exact containment,
+revocation, cleanup, and test obligations, routed straight to the platform,
+proxy, infrastructure, registrar, and risk owners without carrying a prose todo
+through another coding session.
+
+That is the last lesson I would leave in this seat: a refusal is fully handed
+forward only when the next worker does not have to rediscover why it was
+necessary. The hatch stayed closed, but the path back to it became exact.