This master epic contains the work around enabling multiple counterparties to be included in a single Workstep. Work needs to be done on researching approaches, architecting the best approach, and building the necessary interfaces and reference implementation components required to manage this. Multiparty Worksteps must not create problems with Workflows that involve multiple Worksteps, some with different groups of counterparties.
Activity: Build a two workstep workflow where one of the steps involves three counterparties and the other involves 2...and where the third counterparty in the 3-party workstep has no awareness of the 2-party workstep but can be confident of workflow integrity. (May involve consideration of either just the general consistency zk circuit or a customized circuit that enforces some set of rules.)
Impact on the Baseline Community
The Multiparty Workstep is fundamental to most of the value propositions people have been describing and have become excited about.
Acceptance criteria and must have scope
Define what is a must-have for launch and in-scope. Keep this section fluid and dynamic until you lock-in priority during planning.
Timeline
Most worksteps in b2b process automation are bilateral, but without multiparty, it is impossible to include regulators, auditors or do useful and important processes that involve multiple parties that must have verifiably the same information. Therefore, the timeline on this is early 2021, because the feature gates most use cases beyond simple projects and POCs.
Background on Epics, Issues, Checkboxes (aka, Epics, Stories, Tasks)
After you start breaking this master epic up into a set of Issues (sub-epics, stories, tasks, etc), you might consider creating a Project in Github to make it easy for your group to have a single Kanban board for just this work. The Github projects tab in any given repo will allow only Issues from that repo, but if you create one here, you will be able to set up a project that can compose Issues from any of the baseline repos, including the core /baseline repo and the planning /baseline-roadmap repo.
Project Description
This master epic contains the work around enabling multiple counterparties to be included in a single Workstep. Work needs to be done on researching approaches, architecting the best approach, and building the necessary interfaces and reference implementation components required to manage this. Multiparty Worksteps must not create problems with Workflows that involve multiple Worksteps, some with different groups of counterparties.
Activity: Build a two workstep workflow where one of the steps involves three counterparties and the other involves 2...and where the third counterparty in the 3-party workstep has no awareness of the 2-party workstep but can be confident of workflow integrity. (May involve consideration of either just the general consistency zk circuit or a customized circuit that enforces some set of rules.)
Impact on the Baseline Community
The Multiparty Workstep is fundamental to most of the value propositions people have been describing and have become excited about.
Acceptance criteria and must have scope
Define what is a must-have for launch and in-scope. Keep this section fluid and dynamic until you lock-in priority during planning.
Timeline
Most worksteps in b2b process automation are bilateral, but without multiparty, it is impossible to include regulators, auditors or do useful and important processes that involve multiple parties that must have verifiably the same information. Therefore, the timeline on this is early 2021, because the feature gates most use cases beyond simple projects and POCs.
Background on Epics, Issues, Checkboxes (aka, Epics, Stories, Tasks)
After you start breaking this master epic up into a set of Issues (sub-epics, stories, tasks, etc), you might consider creating a Project in Github to make it easy for your group to have a single Kanban board for just this work. The Github projects tab in any given repo will allow only Issues from that repo, but if you create one here, you will be able to set up a project that can compose Issues from any of the baseline repos, including the core /baseline repo and the planning /baseline-roadmap repo.