Exploring atproto for engineering data sheets and complex data

[kearsleydlewis]

I am exploring various ways to decentralize engineering data such that it can be freely shared while ownership is retained. For this to work, extensive permissions and controls are required. I did some digging into namespaces and permissions on those, and so I would like to just discuss the right way to go about creating a PDS or lexicon that supports storing sensitive engineering information (i.e. potential IP protections and trade secrets).

Think of this as analogous to trying to store HIPP or PII level information that needs to be secure by default (E2EE, encrypted on device, heightened permissions, etc).

Can atproto handle this? In theory, how could we go about designing this with atproto? Are there fundamental atproto concepts that won't allow this?

[Burhan-Ahmed]

Isn't it a good idea to purchase a patent for your work? to retain ownership

[kearsleydlewis]

yes if you have 15-50k and 2-3 years on your hands.

doesn't solve the PII or HIPPA analogy though, nor the in-progress designs you may have getting share. Doesn't protect trade secrets or "proprietary" non-patented works either

Code is easier because we can have a license that defines how your code can be used, but is mostly protected via copyright (or copyleft). Designs for hardware are trickier due to IP law and protections.

question still stands: how can atproto store sensitive data for a user, limiting access based on permissions while keeping the data secure?