Balancing private pursuit records with public evidence

The situation

A private pursuit was linked to multiple spaces, and a disposable account was deleted to test the system. The live service showed that private pursuit links can be selected independently, but the membership reads did not establish certain relationships. The goal was to finish the hierarchy without exposing private pursuits or inferring member identities. The existing hierarchy projection was the smallest source path to the requested view. The live screen still needed proof of the nested hierarchy.

What they weighed

• Document verified live outcomes and integrate the hierarchy

• Leave the hierarchy flat and report the existing links

What they decided

Record the proven cleanup and membership state, finish the hierarchy through the standalone owner, and verify it on the live screen

Why

The live service proved independent private pursuit links and a successful account deletion. The existing hierarchy projection was the smallest source path to the requested view, and documenting the proven deletion and invite state would prevent future identity guesses. The standalone owner and read model carried the hierarchy, and the knowledge tree carried reusable verification facts.

The first step

Update the knowledge note and check the hierarchy on the live signed-in screen

How they would know it worked

The note matches live membership and cleanup responses; the live screen renders nested private pursuits without unselected exposure

How it turned out

Not known yet. The result is added here when it comes in.