Private tree that is separate from public tree
I think it would be cool if users had a private tree. The private tree would be separate from the public tree. Private information would show either next to or in place of public information depending on what type of information it is. Any work with public records would be stored in the public tree and in the individual who did the work’s private tree, but not automatically to everyone’s private tree (more on that later in the post). Adding private records or memories would only add to the public tree if the individual who added them explicitly decides to. Any public details that are changed would also only be changed in the individual who changed its private tree and the public tree, but not to everyone’s private tree automatically. For each detail or section, users can choose whether they want to “always sync”, “keep private”, or “sync once” (which would then change to keep private). This would be for both syncing data from the private tree to the public, and for syncing from the public tree to the private. This system would allow for the benefits of public records, like collaboration and sharing information, while allowing users to protect their tree from accidental mistakes. This also could be done without much work by utilizing existing infrastructure. In 2014 family search introduced Private Spaces.
Any private data or records could be stored in private spaces. Any private data in a private tree would be a pointer or reference to private spaces, and any data in a private tree that syncs with public data would be a pointer or reference to the public tree and records.