Re: Web 7.0 DID OS

Michael,

Did you generate this graphic?
What is the source?

Christoph


On Sat, Mar 14, 2026, at 8:14 AM, Michael Herman (Trusted Digital Web) wrote:
> Regarding your offline question about being able to create Web 7.9 LOBE modules using JavaScript: absolutely you can. 
> 
> Here's 4 patterns: https://chatgpt.com/s/t_69b55d845fb481919c6acef9b369d337
> 
> Further any language that has a CLI, embeddable runtime, Web service, etc. can be used to create your custom message processing Web 7.0 LOBEs...
> 
> Image
> 
> Michael Herman 
> Chief Digital Architect 
> Web 7.0 Foundation 
> 
> Get Outlook for Android <https://aka.ms/AAb9ysg>
> 
> *From:* Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net>
> *Sent:* Friday, March 13, 2026 5:37:48 PM
> *To:* Christoph <christoph@christophdorn.com>; W3C Credentials CG <public-credentials@w3.org>; Daniel Hardman <daniel.hardman@gmail.com>
> *Subject:* RE: Web 7.0 DID OS
>  
> Thank you Christoph for your acknowledgement of the issues as well as our overall progress.  You can’t build a real-life functioning ecosystem piecemeal: piecemeal standards, piecemeal standards development organizations (SDO) (how many are involved today? W3C, DIF, LF, IETF, Web 7.0, …), piecemeal private implementations, etc.
> 
>  
> 
> NOTE: A couple years ago, I offered Web 7.0 as an integrated platform to DIF and the parochial response was: *Web 7.0 overlaps too much with what we’re doing already*. Too bad. That was an opportunity missed. Hence, I formed the Web 7.0 Foundation to act as the SDO for Web 7.0 (yes, anyone can create an SDO).  Related, as I’ve commented elsewhere, CCG/W3C has no overarching mission/Northstar to provide any overall, useful direction/guidance to for integration across its WGs. The result: piecemealers creating piecemeal pieces.
> 
>  
> 
> SPECIAL NOTE: With Web 7.0 DIDLibOS, no developer will need to know anything about decentralized technologies to build a solution.  They define Message Types (DID + semantics) and provide a LOBE (Loadable Object Brain Extension) (aka PowerShell module) that implements the Task logic for the message type within the context of a particular Capability. LOBEs can be scripted (PowerShell) or coded in any .NET language.
> 
>  
> 
> This enables the incremental scriptable development of the platform’s capabilities to support the deployment of arbitrarily complex, arbitrarily large, network-native, DID-native solutions. The name for one of these solutions is: a Neuroplex.  You don’t build agents. You don’t build apps. You didn’t build services. You don’t build applications. To start a Neuroplex, you simply send an appropriate message type into the network/graph and watch the magic happen.
> 
>  
> 
> PowerShell has grown from a *Windows administration shell* into one of the *most widely used automation platforms in global IT infrastructure*. Its reach spans operating systems, cloud platforms, enterprise environments, and open-source ecosystems.
> 
>  
> 
> Thank you again Christoph,
> 
> Michael Herman
> 
> Chief Digital Architect
> 
>  
> 
> *From:* Christoph <christoph@christophdorn.com> 
> *Sent:* Friday, March 13, 2026 1:44 PM
> *To:* Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net>; W3C Credentials CG <public-credentials@w3.org>; Daniel Hardman <daniel.hardman@gmail.com>
> *Subject:* Re: Web 7.0 DID OS
> 
>  
> 
>  
> 
> Hi Michael,
> 
>  
> 
> I watched your presentation.
> 
>  
> 
> I like what kinds of problems you think about and that you are trying to propose a solution that achieves an end result by using and extending existing specifications.
> 
>  
> 
> I see you are working towards a complete stack and there are still some hurdles to overcome.
> 
> When I compare your effort to what others are doing I see a wide variety of application of the DID standards.
> 
>  
> 
> I like the concept of a Library Operating System with host adapters. I believe this is a natural architecture for where we are going with the web.
> 
>  
> 
> My interest is in figuring out how we can make progress towards an architecture such as you are describing.
> 
> What is the commonality between how progress is achieved towards your architecture as well as those others are working on?
> 
>  
> 
> One challenge I face when looking into the DID approach is that I need to consult many documents and projects to understand where everything fits in. When wanting to contribute to the ecosystem, one is faced with a steep learning curve and then a lack of community around building solutions with DID tech.
> 
>  
> 
> I have always seen the DID/VC standards as patterns with many implementations. This is great but where can I learn about all the VC/DID patterns and see which are supported to what extent by which implementation?
> 
>  
> 
> Furthermore, how do I use the patterns to solve my actual problems I face when building full-stack SASS and other systems?
> 
>  
> 
> I am working towards practical solutions in the short-term. You are working towards an ideal solution in the long-term.
> 
>  
> 
> What are the things we are missing around the VC/DID ecosystem that is slowing our progress towards realizing what we envision? I bet many others are in the same boat.
> 
>  
> 
> I do not subscribe to the notion of "lack of interest".
> 
>  
> 
> What if the onus is on us to make what we envision and build more consumable in a significant way to others?
> 
> What if there is actually a way to do this and all we have to do is pursue it?
> 
> I have no concrete answers but I believe there is a path open to be discovered with further discourse.
> 
>  
> 
> Christoph
> 
>  
> 
>  
> 
>  
> 
> On Thu, Mar 12, 2026, at 12:18 AM, Michael Herman (Trusted Digital Web) wrote:
> 
>> Here's a comprehensive Web 7.0 update that I presented to the DIDComm WG earlier this week (starts 4 minutes into):
>> 
>> https://us02web.zoom.us/rec/play/uCkJ9lauFX8XBfoUSf4-ck4q51E7gXG3M6HmWDbabuEHWuDcgEGgR83aQ01WwgjzDpsVnhtkJXkNyVdz.CFR9MZV7vCxX8h61
>> 
>>  
>> 
>> It is of interest to anyone working in field of large scale Decentralized Systems Architecture (DSA).
>> 
>>  
>> 
>> Michael Herman
>> 
>> Chief Digital Architect 
>> 
>> Web 7.0 Foundation 
>> 
>>  
>> 
>  
>