Clearly distinguish private data and privitized data by using different variable naming conventions on each side of the noise barrier.

In reviewing the source code, it is not clear which variables refer to private data and which refer to privitized data. I suggest that you clearly distinguish these in the source code, perhaps by using different variable naming conventions.

Start by reviewing the Go source code and identify variables on each side of the noise barrier that represent private versus privatized data. Determine a consistent naming convention for both categories, then apply it throughout the relevant source and verify that the code remains clear and builds successfully.

Written by the indexing model from the issue text.