12. Admin over a document is only the power to destroy it
A document cannot rotate. Admin over it puts the document itself in someone's reach forever, and admin over a document buys nothing else. So root the document at Edit and supply roles at Edit, unless the owners are the document.

12. Admin over a document is only the power to destroy it

A document cannot rotate. Admin over it puts the document itself in someone's reach forever, and admin over a document buys nothing else. So root the document at Edit and supply roles at Edit, unless the owners are the document.

It is the one setup decision that decides whether any removal in your document can ever be durable.

Rotation works because a fresh node comes after the ex-admin. No fact will ever put it on his keyring.

But one node can never be fresh. The document itself. It is the socket in the wall.

Can the socket be on anyone's keyring? Only if someone holds admin over the document. That is set by the root edge's level, chosen once at creation, and by each supply's level.

Root the document at admin, and every admin of Owners, ever, has the socket on their keyring. Rotate all you like. Each of them can unplug every cord in the socket's room. One revocation kills the document.

What does admin over a document buy? Reading, writing, inviting, managing a role. None of it needs admin over the document. Admin over a document is only the power to destroy it.

So root at edit. Supply roles at edit. Then the socket is on nobody's keyring, and rotation always escapes. Root at admin only when the owners are the document, and ending it is the point.

The level is fixed at creation, and anyone holding the bag can see it. It is a fact about the document, not a policy.

Check yourself. A document is rooted at Admin. Members is supplied at Edit, Bob is removed from Members and Members is rotated. Can Bob still revoke the root edge?

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime

Comments