vf-apps-agents issueshttps://lab.allmende.io/valueflows/vf-app-specs/vf-apps-agents/-/issues2020-09-09T10:31:16Zhttps://lab.allmende.io/valueflows/vf-app-specs/vf-apps-agents/-/issues/4Degrees of agency for groups2020-09-09T10:31:16ZBob HaugenDegrees of agency for groups0. A group that has no agency whatsoever.
It just exists and other agents can self-join, no permission needed. Nobody can moderate their behavior or kick them out.0. A group that has no agency whatsoever.
It just exists and other agents can self-join, no permission needed. Nobody can moderate their behavior or kick them out.https://lab.allmende.io/valueflows/vf-app-specs/vf-apps-agents/-/issues/3Group agent use cases2020-08-25T16:30:22ZBob HaugenGroup agent use casesA group agent, aka an agentified group, is a group that has agency as-a-group beyond the agencies of any of the individual members of the group.
Here are some use cases that might explain better:
* A group makes decisions as a group....A group agent, aka an agentified group, is a group that has agency as-a-group beyond the agencies of any of the individual members of the group.
Here are some use cases that might explain better:
* A group makes decisions as a group.
* The group decides how it will make decisions, either as an ongoing procedure, or adhoc, decision-by-decision.
* A group decides how it will handle membership, including, but not limited to:
* procedures for bringing in new members, such as:
* inviting new members, which could be done by individual members or more officially by the group, but if by individual members, the group will either not interfere, or decide to allow it, or decide to prohibit the practice;
* allowing non-members to request membership, and either accepting or rejecting such requests.
* A group makes agreements with other agents, including group and individual agents.
* The agreements made by a group survive the departure of the individuals who participated in making the agreements. If they don't, those agreements were made by some individuals, not by an agentified group.
* The history of decisions made by the group belongs to the group-as-a-whole, and also survives the departure of any of the individual members who participated in those decisions, altho the group can always subsequently rescind any of those prior decisions, except for agreements made by the group with other agents.
* In a vf-apps context, a group decides what apps it will use for what purposes. Individual members will probably need to use those apps when interacting in the context of the group.
Note: this is a starting list. Please help by suggesting improvements, making additions, or recommending deletions. I'd like to arrive at a useful list for some discussions in Holochain.https://lab.allmende.io/valueflows/vf-app-specs/vf-apps-agents/-/issues/2Personal agent app as a bridge for Dweb2019-07-19T00:42:53ZBob HaugenPersonal agent app as a bridge for DwebThis is a contribution (we hope) to this Dweb Camp discussion about [building bridges -- connecting tech stacks for humane UX](https://github.com/dweb-camp-2019/projects/issues/31).
The focus of the discussion is about building bridge...This is a contribution (we hope) to this Dweb Camp discussion about [building bridges -- connecting tech stacks for humane UX](https://github.com/dweb-camp-2019/projects/issues/31).
The focus of the discussion is about building bridges between different decentralized/distributed social/economic media stacks: for example, [Secure Scuttlebutt (SSB)](https://www.scuttlebutt.nz/), [ActivityPub](https://activitypub.rocks/), and [Holochain](https://holochain.org/), which seem to their developers and participants to be akin, in the same family.
So this is a proposal for a relatively simple bridge that would not require changes to any of those stacks.
Each of these mediums, either naturally or possibly, focuses on individual people. Holochain calls it "agent-centric computing".
But as an individual person, I have different personas, or identities, in each of these media. I know people who have several different identities in SSB alone - in many cases because SSB identities are per-device, not per-person. And SSB is talking about some optional mechanism to indicate that many identities represent the same person.
As a person, I would like to view and maybe even interact with all of the activities of all my personas from the same viewpoint. This would be a personal agent app, that can connect to, but not be embedded in, any of the media in which the personas live.
The personal agent app might need to know whatever access credentials are used by each of the connected personas. And show the feeds for each persona, maybe intermingled, or maybe separately, probably with some optional filters. And probably with some other dashboard-y info.
Such an app might raise some issues with the expectations of participants in the various media. For example, in SSB, people can [opt-out from having their posts visible on public gateways](https://www.scuttlebutt.nz/faq/misc/privacy) (which this app might be, depending how it's implemented).
https://lab.allmende.io/valueflows/vf-app-specs/vf-apps-agents/-/issues/1Differences between personal and organizational Agent apps2020-08-25T16:08:17ZBob HaugenDifferences between personal and organizational Agent appsThis is the beginning of an exploration of the territory for discussion at this stage, not a proposal.
As mentioned previously, an individual agent would act from their own Agent app, while if a organizational agent needed to execute ...This is the beginning of an exploration of the territory for discussion at this stage, not a proposal.
As mentioned previously, an individual agent would act from their own Agent app, while if a organizational agent needed to execute its agency in some way, it would need an authorized individual to do that, and ~the individual would most likely act from the organization's app~. **_Rethinking:** all of the actions for group agents could, and probably should, be triggered from individual agent apps, either by agents that are authorized by the group to take particular actions on behalf of the group (and then the group takes the action like a bot) or by means of decision-making protocols offered to the group members by the group, again acting like a bot to offer the decision-making tools and then in executing the decision._
A lot of the apps that would be useful for an organization might also be used by an individual person, but maybe differently.
For example, both individuals and organizations might want to use [Recipes](https://github.com/valueflows/vf-apps-recipes) and [Planning](https://github.com/valueflows/vf-apps-planning).
But what happens if an individual wants others to help to execute a planned process? In an organization, that would be normal, and the process would live in the organization's app, while the individuals who worked on it would mostly take their individual actions (like committing to and logging work on the process) from their individual apps.
But for a set of people who want to work on a process together that are not a defined group with a group app, where does the process live? It could either live in the individual agent app of one of the participants, or the process could be shared by all the participants by each individual having a copy and the copies syncing with each other, or they could form a group agent or an adhoc group that might live only for the duration of the process.
Another set of differences might occur in forming relationships between agents, for example group-forming and membership apps.
Both individuals and organizations might want to form new groups:
* for the individuals, a new group composed of individuals or possibly both individuals and other groups;
* for the groups, maybe networks or other groups of groups, or subgroups or supergroups.
Groups might have membership apps with procedures for bring in, managing, or kicking out, individual or group members. Individual agents would probably not have membership apps.
But both individuals and groups will want to form a variety of relationships with other agents.