access: a forgotten node cancels its own record

A node forgotten swarm-wide while alive cancels its forget record with
a change naming no user; the rules judged _continuum/forgotten by the
registry alone, so every node refused the cancellation and everything
the node wrote after it. A node may now write its own
_continuum/forgotten/<id>, as it may its member entry.

Review finding 4.

1 files changed, 1 insertions, 0 deletions

diff --git a/docs/access.md b/docs/access.md
index 1ee9994..8443394 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -224,6 +224,7 @@ revocation since refuses nothing it allowed then, and every node judges alike.
 * A remake's decision by the coordinator its proposal names; the rest of a record by
   any member.
 * A user's tokens revoked by that user too (logging out).
+* A member's forget record cancelled by that member too (forgotten while alive).
 * Everything else, protocol data or not, by a user the registry lets write there.
 * A node that isn't a member may only register itself; a banned node nothing (Banning
   a node, below). So a node registers before anything else it writes, through the API