Thanks for the comment, I see what you are seeing with the prefixes yeah.
As far as the profiles goes… The short answer is that in the normal case I see one agent key mapping to one profile only.
Here is the long answer:
- Each physical person will have:
- A set of public/private key pairs managed by DeepKey
- A private and dedicated personas&profiles dna, which contains:
- Your set of personas (key value pairs with your actual information)
- Your profile mappings for each happ (I think happ, could be dna but doubt it)
- Whenever you install a happ, you install multiple dnas. Those dnas will all share the same public key to start with.
- I think that in the normal case, you will want only one profile per happ (per set of dnas). This is because although dna read access could be different for every agent, I don’t think you should need to create a separate profile mapping inside each dna (imagine your holo-REA dnas but in each one a different profile… not very consistent in my opinion, better to have only one place in one of the dnas for that)
So, the data structures look reaaally different whether you are seeing your personas and profiles info (in which you can access all your private information and see your mappings), or a profile for another user, in which you should only see the resolved profile for that user for that app (here,
f(persona, profileMapping) -> Profile) where you apply the mapping transformations from the mapping to the persona to get the profile).
One thing this touches on also is the group agency thing, I’ve been thinking. in REA’s schemas, if you reference the organization directly for an EconomicEvent let’s say, you are losing the information about who acted in behalf of the organization. Have you or anyone in valueflows thought about saying something like “this economicevent was approved by this agent on behalf of this organization”? Then if we find out that the delegate is misbehaving we can track all the places in which they did.
Granted, this makes it difficult to implement other governance systems than delegation, but… I don’t know if your idea is that REA should cover things like “we have approved this economicevent as a result of this voting process”. That could be also done by a single agent who is just “implementing” the result of the vote, though.