Merge pull request #25 from vinomaster/master

Updated BBU Story

UTILITY_LIST.md

@@ -14,6 +14,6 @@ Listed herein, are those endeavors that seek to be listed and that have minimall
 | --- | --- | --- | --- | --- | --- |
 | [IDunion](https://www.pressebox.de/pressemitteilung/esatus-ag/SSI-for-Germany-Consortium-starts-decentralized-identity-network/boxid/1020932) | [Main Incubator GmbH](https://main-incubator.com/en/home), Germany | Create| Project underway, co-funded by [German Federal Ministry of Economic Affairs and Energy](https://www.bmwi.de/Navigation/EN/Home/home.html)  | [Hyperledger Indy](https://www.hyperledger.org/use/hyperledger-indy) | TBD |
 | [Sovrin MainNet](https://www.sovrin.org) | [Sovrin Foundation](https://www.sovrin.org), Utah, USA | Maintain |Running | [Hyperledger Indy](https://www.hyperledger.org/use/hyperledger-indy) | [SaturnV](https://github.com/trustoverip/technical-stack-wg/blob/master/_proposals/saturn-v-tip.md) |
-| [Bedrock Business Utility](https://bedrock-consortium.github.io/bbu-gf/) | Bedrock Consortium | Create| Formation of Linux Foundation Project and Governing Board. | [Hyperledger Indy](https://www.hyperledger.org/use/hyperledger-indy) | [SaturnV](https://github.com/trustoverip/technical-stack-wg/blob/master/_proposals/saturn-v-tip.md) |
+| [Bedrock Business Utility](https://bedrock-consortium.github.io/bbu-gf/) | [Bedrock Consortium](https://bedrockconsortium.org/) | Create| Membership Campaign and Project setup. | [Hyperledger Indy](https://www.hyperledger.org/use/hyperledger-indy) | [SaturnV](https://github.com/trustoverip/technical-stack-wg/blob/master/_proposals/saturn-v-tip.md) |
 | [Indicio Network ](https://indicio.tech/indicio-testnet) | [Indicio.tech](https://indicio.tech), USA | Implement | TestNet Running | [Hyperledger Indy](https://www.hyperledger.org/use/hyperledger-indy) | [SaturnV](https://github.com/trustoverip/technical-stack-wg/blob/master/_proposals/saturn-v-tip.md) |
 | [CanaCred](https://www.canacred.ca)| [Canadian Credential Network (CanaCred)](https://www.canacred.ca) | Convene | Planning phase, member recruitment | [Hyperledger Indy](https://www.hyperledger.org/use/hyperledger-indy) | TBD |

workflow/stories/bbu.md

@@ -4,35 +4,35 @@
 | --- | --- |
 | Bedrock Business Utility | Actual|
 
->DISCLAIMER: This document represents a hi-;level summation of actual activity. A detailed synopsis of activities will be required to understand actual workflow decisions.
+>DISCLAIMER: This document represents a hi-level summation of actual activity. A detailed synopsis of activities will be required to understand actual workflow decisions.
 
 ### Background Context
-The Bedrock Consortium is a collection of international private sector companies that operate the Bedrock Business Utility (BBU), an independent self-governed non-profit legal entity that serves as a public identity utility and operates as a self-sustainable directed fund project under The Linux Foundation.
+The [Bedrock Consortium](https://bedrockconsortium.org/) is a collection of international private sector companies that operate the [Bedrock Business Utility (BBU)](http://bbu.bedrockconsortium.org/), an independent self-governed non-profit legal entity that serves as a public identity utility and operates as a self-sustainable directed fund project under The Linux Foundation.
 
 The BBU is intended to serve organizations that desire to participate in digital trust ecosystems and require an enterprise grade governance framework that will:
 
 * Enforce permissioned-writes with contractual instruments that will conform to privacy regulations such as GDPR
-* Maintain financial sustainability of the consortium members without the use of cryptographic tokens
-* Establish a governing board so that no single organization owns the Identity Utility Network
+* Maintain financial sustainability of the consortium without the use of cryptographic tokens
+* Establish a governing board so that no single organization owns the [public identity utility](https://bedrock-consortium.github.io/bbu-gf/gf_info/glossary/#public-identity-utility).
 * Require adherence to specified open standards and protocols
 
 ### Pertinent Concepts
 
-* Self-sustainability: Leveraging lessons learned from the [Sovrin Foundation](http://sovrin.org), a business model that was not rooted in philanthropic supported infrastructure must be established.
-* Self-governed: As a decentralized public service provider, the Utility must be governed as a legal entity with a transparent governing model.
+* **Self-sustainability**: Leveraging lessons learned from the [Sovrin Foundation](http://sovrin.org), success is dependent on the establishment of a business model that is not rooted in philanthropic supported infrastructure.
+* **Self-governed**: As a decentralized public service provider, the public identity utility must be governed as a legal entity with a transparent governing model.
 
 ### Stakeholders / Persona
 The following subjects are stakeholders to story:
 
-* Dan (Convener): Digital Identity leader at a large technology company.
+* Dan (Founder/Convener): Digital Identity leader at a large technology company.
 * Christine (Steward): Digital Identity leader at a large consulting firm.
 
 ### User Stories
 1. Dan and Christine share common business needs for a public identity utility and decide to collaboratively explore the viability of a Utility.
-2. Dan runs an exploratory campaign with industry competitors and clients to identify prospective stakeholders in a consortium.
+2. Dan runs an exploratory campaign with industry competitors and clients to identify prospective stakeholders that are willing to collaborate in a consortium.
 3. Dan convenes a working group, represented by sponsoring businesses, to establish a governance framework.
-4. The Working Group runs a RFP Process to help validate budgetary requirements and the selection of a Utility Service Provider ("USP").
-5. The Working Group collaborates with the Linux Foundation on the establishment of a *LF Governance Network, Inc*.
+4. The Working Group runs a RFP Process to help validate budgetary requirements and the selection of a [Utility Service Provider](https://bedrock-consortium.github.io/bbu-gf/gf_info/glossary/#utility-service-provider) ("USP").
+5. The Working Group collaborates with the Linux Foundation ("LF")  on the establishment of a LF Governance Network Project under the new [LF Governancewnce Network Model](https://www.linuxfoundation.org/blog/2020/10/introducing-the-open-governance-network-model/).
 6. The Working Group formalizes the launch of a Utility.
 
 ### Utility Foundry Workflow
@@ -41,37 +41,46 @@ The following subjects are stakeholders to story:
 
 ### Learn
 
-* While Dan and Christine had an operational understanding of how a Utility would work, then=y needed to educate prospective stakeholders.
+* While Dan and Christine had an operational understanding of how a Utility would work, they needed to educate prospective stakeholders.
 * Clients of Dan and Christine shared a common need - a trusted and enterprise reliable utility service for identify verification that was easy to maintain and use. They desired a minimum viable utility ("MVU")
 * The employers of Dan and Christine did not desire to own and operate the Utility, they desired a non-profit and open solution.
 4. Both stakeholder companies were deeply concerned about GDPR/CCPA privacy risks associated with participation in such a Utility from an infrastructure perspective.
-5. Dan and Christine agreed the requirements for convening project would be to get 5-10 companies to provide (a) an executive sponsor willing to be a board member if the Utility materialized; (b) a working group resource willing to work on the creation of a governance framework.
+5. Dan and Christine agreed the requirements for convening a project would be to get 5-10 companies to provide (a) an executive sponsor willing to be a board member if the Utility materialized; (b) a working group resource willing to work on the creation of a governance framework.
 
 ### Convene
 The Bedrock Consortium was informally formed with representatives from nine (9) prospective companies. The identification of these prospective nine required numerous emails and educational sessions to establish interest and identify common requirements.
 
 The Bedrock Consortium established a Governance Framework Working Group ("GFWG") with Dan as the Convener.
 
 ### Define
-Using the [Sovrin Governance Framework](https://sovrin.org/library/sovrin-governance-framework/) and a model, the GFWG collaborated on the:
+Using the [Sovrin Governance Framework](https://sovrin.org/library/sovrin-governance-framework/) as a model, the GFWG collaborated on the:
 
-* Creation of an online governance framework that can be easily navigated and maintained via GitHub
-* Articulation of scope of management and how the Utility Project will be governed using proven  Linux Foundation open source project models.
-* Decided on the use of Hyperledger Indy as the ledger technology
-* Accepted the contribution of a BBU specific DID Method (```did:bbu```)
-* Modeled budgetary sustainability requirements for a MVU of 25 Stewards growing no larger than 60 Stewards.
+* Creation of a new governance framework online that can be easily navigated and maintained via GitHub
+* Articulation of scope of management and how the Utility Project will be governed using proven Linux Foundation open source project models.
+* Establishing a set of foundational project decisions:
+
+    1. Design Principles
+    2. Technology Stack
+    3. Accepted the contribution of a BBU specific DID Method (```did:bbu```)
+        * [Demo Resolver](https://resolver.identity.foundation)
+        * [DID Method Driver](TBD): See [bedrock-consortium/TSC Issue #3](https://github.com/bedrock-consortium/TSC/issues/3).
+
+    *Note*: As the GFWG progressed so did the open source community. The maturation of parallel effort aided some  architectural decisions: (i) Saturn-V TIP with emphasis on vendor interop testing; (ii) Trends associated with a [network of Hyperledger Indy public identity utilities](https://github.com/trustoverip/utility-foundry-wg/blob/master/UTILITY_LIST.md#utility-directory) (iii) [Indy DID Method standardization activity](https://wiki.hyperledger.org/display/indy/Indy+DID+Method+Specification)
+
+* Modeling of sustainable budget requirements for a MVU of 25 Stewards growing no larger than 60 Stewards.
 * Outlining criteria for the selection of a Utility Service Provider.
 
 ### Create
-* Published the BBU Governance Framework (a living document)
-* Working with the Linux Foundation to launch the Utility Project:
+* Ran a RFP Process based on the criteria for the selection of a Utility Service Provider.
+* Published the [BBU Governance Framework](http://bbu.bedrockconsortium.org/) (a living document)
+* [Formalized the Utility via a LF Soft-Launch](https://bedrockconsortium.org/blog/2020/12/01/this-is-a-blog-post/):
     * Created a *Briefing Package* to be used to solicit Bedrock Consortium members.
-    * Run exploratory member invitation sessions
+    * Ran exploratory briefing sessions
     * Created the Bedrock Technical Project
-* Ran a RFP Process for a USP.  
+
 
 ### Implement
-TBD
+Execution of an implementation plan is dependent on achieving a minimum viable membership of 36 members.
 
 ### Maintain
 TBD