Create your own magic with Web 7.0 Agentic OS. Imagine the possibilities.
Copyright © 2025 Michael Herman (Bindloss, Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
Here’s 2 teaser slides…
Mitch Joel’s “Three Little Pigs” (TLP): A Metaphor for Kaplan & Norton’s Strategy Map
Create your own magic with Web 7.0 AgenticOS™. Imagine the possibilities.
Copyright © 2025 Michael Herman (Bindloss, Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
Mitch Joel’s Three Little Pigs (TLP)
“If the Big Bad Wolf of business is disruption — then your house of straw, your house of sticks, your house of bricks … they each represent how you respond. To survive, you can’t just build the straw or the sticks. You need the bricks.” — Mitch Joel (Italics added)
If the “big bad wolf” symbolizes disruption, then the Three Little Pigs are three business responses you need to cover to survive and thrive:
- Pig 1 — Transform: internal change. Make transformation an inside-out function: rethink organizational structure, culture and capabilities so you can meet customers where they are. (Think: change how you operate, not just what you sell.)
- Pig 2 — Innovate: build products, services or experiences that actually connect with people — new tools, features or touchpoints that create fresh ways to engage.
- Pig 3 — Transact: rework how you enable commerce and conversion — the channels, payment flows, and customer journeys that let people buy or interact on their terms.
Why he uses the tale: the fairy tale makes the point visceral: if you only build a “straw” or “stick” strategy (only one of Transform, Innovate, Transact), the wolf (Disruption) will blow you down. You need all three to be resilient.
Pig 1 — Transform: the “inside-out” house-building
- Build capability and culture first. Don’t only redesign products; change how the organisation thinks, decides and moves.
- Focus on skills, structure and processes that let you adapt: cross-functional teams, fast decision loops, data fluency, and an experimentation mindset.
- Make customer context part of every change: measure real customer behaviour (not just surveys) and let that guide priorities.
- Concrete early wins: align one existing team to run a rapid experiment (2–4 week sprint), hire/rotate a digital product lead into a legacy unit, or map your customer journey and remove the top 3 friction points.
- Useful KPIs: time-to-decision, % of revenue from products launched in last 18 months, experiment velocity (number of tested hypotheses per quarter), and Net Promoter Score or task completion rates for key journeys.
Pig 2 — Innovate: Build the house of sticks
“Once you’ve begun transforming internally, you need to create things that people actually want. Innovation isn’t about chasing shiny objects; it’s about connecting better with customers.” — Mitch Joel
Innovation is building new ways for people to engage with your brand, products, or services. It’s the “what we make and how it connects” layer between transformation (internal) and transaction (external).
- Experiment at the edges – Pilot emerging technologies, formats, and experiences (AR, personalization, voice, AI tools) to see what actually enhances value.
- Design for emotion – Innovate not only for efficiency, but for meaning: create products, campaigns, or digital experiences that make people feel something.
- Bridge physical + digital – Mitch calls this “the connected experience.” Every interaction, online or offline, should feel continuous.
- Iterate fast, retire faster – The wolf (disruption) gets through the “stick house” if you can’t evolve quickly. Kill what doesn’t work early.
Pig 3 — Transact: Build the Brick House
Transformation builds the foundation (Pig 1). Innovation builds the structure that attracts and connects people (Pig 2). But the house of sticks still isn’t enough — unless you tie it to real customer action through Transact (Pig 3 — a house of bricks).
“Transformation and innovation don’t mean much if you can’t enable people to act — to buy, to subscribe, to connect. The strongest companies make it effortless for customers to say ‘yes.’” — Mitch Joel
Transact is about removing friction between desire and action. It’s where all your internal change (Pig 1) and creative output (Pig 2) translate into measurable results — purchases, loyalty, advocacy, or community engagement.
Meet customers where they are.
- Build omnichannel experiences — physical, digital, social, voice, app — that feel unified.
- “The future of commerce is context,” he says: people transact in the environment they’re already in.
Simplify the path to action.
- One-click purchasing, mobile optimization, intuitive onboarding, instant checkouts.
- Fewer steps = more conversions.
Trust and transparency.
- Friction isn’t just usability; it’s emotional. People buy when they trust how their data, time, and values are treated.
Close the feedback loop.
- Every transaction should teach you something. Feed that data back into transformation (Pig 1) and innovation (Pig 2).
Mitch’s Metaphor
- Pig 1 — Transformation = foundation (get your own house in order).
- Pig 2 — Innovation = frame and design (what the world sees).
- Pig 3 — Transaction = solid bricks that make the house stand against the wolf (disruption).
Kaplan & Norton’s Strategy Map
A good example of a Kaplan and Norton strategy map appears in Figure 1. The Parallelsapce Corporation Strategy Map applies the Kaplan and Norton Balanced Scorecard framework to align learning, processes, customers, and financial outcomes.
It begins with a foundation of Learning & Growth — focusing on research, training, people, and best practices—to build organizational capabilities.
These capabilities feed into Internal Processes such as analysis, external publishing, partnerships, CRM, and proof-of-concepts, which strengthen Customer Perspectives of knowledge and solution leadership through design excellence and process integrity.
Ultimately, this drives Financial Results across multiple revenue streams, including content, delivery, training, consulting, and both packaged and custom solutions.
The map emphasizes a cause-and-effect flow from people and process excellence to customer trust and financial growth.
Mapping “Three Little Pigs” (TLP) to Kaplan & Norton’s Strategy Map
Figure 2 is a color-coded layout aligning the TLP’s potential business responses of Transform, Innovate, and Transact with the Learning & Growth, Internal Process, Customer, and Financial perspectives of the Balanced Scorecard framework
The 4th Perspective, Learning & Growth (Cultural Foundation), is an extension of the Pig 1 — Transform response used for Perspective 3: Internal Processes.
Resources
- Strategy Maps: Converting Intangible Assets into Tangible Outcomes. Robert S. Kaplan and David P. Morgan. Harvard Business Review Press. 2004.
Filed under Uncategorized
Dunbar’s Number – Explained
Create your own magic with Web 7.0™ / TDW AgenticOS™. Imagine the possibilities.
Copyright © 2019-2025 Michael Herman (Bindloss, Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
Web 7.0™, TDW AgenticOS™ and Hyperonomy™ are trademarks of the Web 7.0 Foundation. All Rights Reserved.
Dunbar’s Number refers to the cognitive limit on the number of stable, meaningful social relationships a person can maintain — typically around 150.
Proposed by anthropologist Robin Dunbar in the early 1990s, it’s based on research linking neocortex size to social group size in primates, then extrapolated to humans.
The key idea: our brains can only manage a limited number of people whose relationships with us (and with each other) we can track in any depth.
📊 Dunbar’s Social Layers
Dunbar found that human relationships form nested circles of intimacy, each layer roughly three times larger than the one before it — but with decreasing emotional closeness and interaction frequency.
| Layer | Approx. Size | Relationship Type | Typical Frequency of Contact / Emotional Closeness |
|---|---|---|---|
| 0th Circle (#Wanderer) | 1 | An individual | N/A |
| 1st Circle (Party of Explorers) | 2-5 | Closest friends & family — your “support clique” | Daily or near-daily contact; deepest emotional ties |
| 2nd Circle (Family Unit) | 5-20 | Good friends you confide in and rely on | Weekly contact; high emotional closeness |
| 3rd Circle (Band) | 20-50 | Friends you might invite to a big personal event (e.g. wedding) | Monthly contact; moderate closeness |
| 4th Circle (Clan) | 50-500 | Meaningful relationships — people you know personally and would help if needed | A few times per year; recognize and understand social context |
| 5th Circle (Tribe) | 1000-2000 | Acquaintances — people whose names and faces you recognize | Occasional interaction or recognition |
| 6th Circle (Nation State) | 2000-150,000+ | People you can place a name to (the limit of facial recognition memory) | Rare interaction; mostly recognition only |
📱 Modern & Practical Implications
Even in the digital era:
- People still maintain about 100–200 active online relationships despite thousands of “followers.”
- Teams, villages, and companies often stabilize near this size before naturally splitting or losing cohesion.
- Some organizations (like W. L. Gore, maker of Gore-Tex) deliberately limit unit size to ~150 to preserve strong internal culture and trust.
Copyright © 2025 Michael Herman (Bindloss, Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
Filed under Uncategorized
Thinking Macromodularly
Create your own magic with Web 7.0 AgenticOS™. Imagine the possibilities.
Copyright © 2025 Michael Herman (Bindloss, Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
The term “macromodular” generally refers to something composed of large, self-contained modules that can be combined or interchanged within a broader system.
Why Macromodular?
The amount of logically irrelevent engineering detail inherent in the design and construction of a computer system is great. As a result, the task of creating a system based on the use of present techniques is so difficult and time-consuming that the number of different systems that can be put into use for evaluation and study by any one group of workers is small. This is unfortunate as we are thereby denied the opportunity to develop that insight into logical organization which can grow out of a working familiarity with many diverse forms. What is needed is a set of relatively simple, easily inter-connected modules from which working systems can be readily assembled for evaluation and study. With such a set, both the designer and user would be able to try out potentially powerful and novel structures on a very large scale, adjusting and improving the systems as needed. Once a design has been realized and its value established, it could then be reworked into tighter engineering form for maximum efficiency and for production by automatic wiring and fabrication techniques, and the experimental units made available for further studies or returned to “inventory” in the manner proposed by Estrin.
Macromodular computer systems. Wesley Clark. 1967.
“Macromodular” is used in several contexts, each with a slightly different nuance.
1. Systems Design / Engineering
Meaning: A macromodular system is built from major components (modules) that can operate semi-independently but connect through defined interfaces.
Example: In aerospace or manufacturing, a rocket might be designed in macromodules — propulsion, guidance, payload — each built and tested separately, then integrated.
Contrast:
Modular → small, interchangeable units.
Macromodular → large, complex modules, often representing entire subsystems.
2. Software Architecture
Meaning: A macromodular architecture organizes codebases into large, cohesive components (e.g., microservices clusters or bounded contexts) rather than granular micro-modules.
Example: A company might have a “macromodule” for payments, another for user management, each encompassing many smaller internal modules.
Benefit: Easier maintainability and clearer ownership boundaries than hyper-granular microservices.
3. Biological or Cognitive Science (less common)
Sometimes used metaphorically to describe large functional units in a system — e.g., macromodular organization of the brain (sets of modules handling high-level tasks like perception or language).
In short: Macromodular = modular at a higher level of aggregation. It emphasizes large-scale modularity — balancing specialization and integration.
The term “macromodular systems” refers to systems composed of large, well-defined, interoperable modules that can be independently developed, maintained, and replaced, yet integrate seamlessly into a larger architecture. It’s an evolution of modular design thinking—scaling up modularity from components or microservices to system-level modules that encapsulate significant functionality or subsystems.
Resources
- Organization of computer systems: the fixed plus variable structure computer. Gerald Estrin. 1960.
- Macromodular computer systems. Wesley Clark. 1967.
- Logical design of macromodules, Mishell J. Stucki et all. 1967.
Designing Multi-Agent Systems
Filed under Uncategorized
The Promise of AI
Create your own magic with Web 7.0 Agentic OS. Imagine the possibilities.
Copyright © 2025 Michael Herman (Bindloss, Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
The true #promise of #AI is solving #macromodular problems – not personal productivity tools like ChatGPT, Copilot, Grok, Gemini, Perplexity, Claude, etc. Michael Herman, November 2, 2025.
Filed under Uncategorized
Why are Agents Important?
Create your own magic with Web 7.0 AgenticOS™. Imagine the possibilities.
Copyright © 2025 Michael Herman (Bindloss, Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
…AI Agents in particular.
Who remembers when Microsoft introduced Visual Basic Controls (VBX)?
Why are Agents important? AI Agents will follow the same trajectory as VBXs and serve an identical purpose: accelerating the componentization, commercialization, and consumption of AI. This trajectory will be measured in years.
Michael Herman, LinkedIn. Web 7.0 Foundation. October 2025.
Footnote
Microsoft introduced Visual Basic controls — often referred to as VBX controls — in 1991, with the release of Visual Basic 1.0 for Windows.
The “father” of VBXs (Visual Basic eXtensions) is generally recognized as Alan Cooper. Here’s how that came about:
Alan Cooper, a software designer and developer, created an early visual programming environment called Tripod in the late 1980s. Microsoft acquired the rights to Tripod and, working with Cooper, developed it into Visual Basic 1.0, which launched in 1991.
Cooper’s prototype introduced the form designer concept — dragging and dropping UI elements (controls) onto forms — which directly led to the need for VBX controls as reusable, pluggable components.
Although Microsoft’s VB team (led by Scott Ferguson and others) implemented the actual VBX architecture, Alan Cooper’s foundational design and vision for a “visual, component-based programming tool” earned him the informal title of:
🧠 “The Father of Visual Basic” — and by extension, of VBX controls.
Filed under Uncategorized
“Best wishes for a New Albertan”
My Wishes for a #NewAlbertan
(read slowly like Paul Harvey would say it)
Ask your Dad for a fingertip drip of Jameson.
Learn how to kiss …passionately.
Clip your fingernails …really close.
Wear Bleu De Chanel.
Smile a lot.
Learn to dance the polka, two-step, and jive.
Slow dancing will come on its own.
Buy flowers …lots of flowers.
Take your Mom out on “school nights”.
Throw the baseball with Dad.
Smile a lot.
Learn to use a real calf rope.
Drive a pickup truck …nothing else.
Learn to pick crocuses and wild roses.
Valpolicella Ripasso is a great wine until you can afford Amarone.
Smile even more.
Travel, yes travel …to Spain, Netherlands, and Poland.
Eat great food.
Make your Mom buy you a pickle canner.
Love your Mom and your Dad but especially your Mother.
Smile even more.
Never forget you’re an Albertan.
Buy a ranch some day.
Wherever life takes you, never forget what an Alberta sky looks like.
Love country music.
Smile.
These are my wishes for you #NewAlbertan.
Michael Herman, February 2021.
Filed under Uncategorized
Web 7.0 AgenticOS™ Trust Graph (Pure Peer Model)
Create your own magic with Web 7.0 AgenticOS™. Imagine the possibilities.
Copyright © 2025 Michael Herman (Bindloss, Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
Filed under Uncategorized
Web 7.0™ / TDW AgenticOS™ (Project “Shorthorn”)
Create your own magic with Web 7.0™ / TDW AgenticOS™. Imagine the possibilities.
Copyright © 2025 Michael Herman (Bindloss, Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
Web 7.0™, TDW AgenticOS™ and Hyperonomy™ are trademarks of the Web 7.0 Foundation. All Rights Reserved.
Introduction
This article describes Web 7.0™ and TDW AgenticOS ™ – with a specific focus on the Web 7.0 Neuromorphic Agent Architecture Reference Model (NAARM) used by TDW AgenticOS™ to support the creation of Web 7.0 Decentralized Societies.
The intended audience for this document is a broad range of professionals interested in furthering their understanding of TDW AgenticOS for use in software apps, agents, and services. This includes software architects, application developers, and user experience (UX) specialists, as well as people involved in a broad range of standards efforts related to decentralized identity, verifiable credentials, and secure storage.
The Second Reformation
Web 7.0 Foundation Ecosystem
“Web 7.0 is a unified software and hardware ecosystem for building resilient, trusted, decentralized systems using decentralized identifiers, DIDComm agents, and verifiable credentials.”
Michael Herman, Trusted Digital Web (TDW) Project, Hyperonomy Digital Identity Lab, Web 7.0 Foundation. January 2023.
TDW AgenticOS™
TDW AgenticOS™ is a macromodular, neuromorphic agent platform for coordinating and executing complex systems of work that is:
- Secure
- Trusted
- Open
- Resilient
TDW AgenticOS™ is 100% Albertan by birth and open source.
Project “Shorthorn”
Project “Shorthorn” is a parody project name based on Microsoft’s Windows “Longhorn” WinFS project (a SQL-based Windows File System project) with which the author was involved in from a design preview and feedback, consulting, and PM technical training (Groove Workspace system architecture and operation) perspectives (circa 2001-2002).
What makes Shorthorns great:
– They’re good at turning grass into meat (great efficiency).
– Shorthorn cows are amazing mothers and raise strong, healthy calves (nurture great offspring).
– Their genetics blend well with other breeds for strong hybrid calves (plays well with others).
…and so it is with TDW AgenticOS™.
Web 7.0 Foundation
The Web 7.0 Foundation, a federally-incorporated Canadian non-profit corporation, is chartered to develop, support, promote, protect, and curate the Web 7.0 ecosystem: TDW AgenticOS operating system software, and related standards and specifications. The Foundation is based in Alberta, Canada.
What we’re building at the Web 7.0 Foundation is described in this quote from Don Tapscott and co.:
“We see an alternate path: a decentralized platform for our digital selves, free from total corporate control and within our reach, thanks to co-emerging technologies.”
“A discussion has begun about “democratizing AI.” Accessibility is critical. Mostaque has argued that the world needs what he calls “Universal Basic AI.” Some in the technology industry have argued that AI can be democratized through open source software that is available for anyone to use, modify, and distribute. Mostaque argues that this is not enough. “AI also needs to be transparent,” meaning that AI systems should be auditable and explainable, allowing researchers to examine their decision-making processes. “AI should not be a single capability on monolithic servers but a modular structure that people can build on,” said Mostaque. “That can’t go down or be corrupted or manipulated by powerful forces. AI needs to be decentralized in both technology, ownership and governance.” He’s right.”
You to the Power Two. Don Tapscott and co. 2025.
A Word about the Past
The Web 7.0 project has roots dating back approximately 30 years to before 1998 with the release of Alias Upfront for Windows. Subsequent to the release of Upfront (which Bill Gates designated as the “most outstanding graphics product for Microsoft Windows 3.0”), the AUSOM Application Design Framework was formalized.
AUSOM Application Design Framework
AUSOM is an acronym for A User State of Mind — the name of a framework or architecture for designing software applications that are easier to design, implement, test, document and support. In addition, an application developed using the AUSOM framework is more capable of being: incrementally enhanced, progressively installed and updated, dynamically configured and is capable of being implemented in many execution environments. This paper describes the Core Framework, the status of its current runtime implementations and its additional features and benefits.
What is AUSOM?
The AUSOM Application Design Framework, developed in 1998, is a new way to design client-side applications. The original implementation of the framework is based on a few basic concepts: user scenarios and detailed task analysis, visual design using state-transition diagrams, and implementation using traditional Windows message handlers.
The original motivation for the framework grew out of the need to implement a highly modeless user interface that was comprised of commands or tasks that were very modal (e.g. allowing the user to change how a polygon was being viewed while the user was still sketching the boundary of the polygon).
To learn more, read The AUSOM Application Design Framework whitepaper.
Einstein’s Advice
The following is essentially the same advice I received from Charles Simonyi when we were both at Microsoft (and one of the reasons why I eventually left the company in 2001).
“No problem can be solved from the same level of consciousness that created it.” [Albert Einstein]
“The meaning of this quote lies in Einstein’s belief that problems are not just technical failures but outcomes of deeper ways of thinking. He suggested that when people approach challenges using the same assumptions, values, and mental habits that led to those challenges, real solutions remain out of reach. Accoding to this idea, improvement begins only when individuals are willing to step beyond familiar thought patterns and question the mindset that shaped the problem.” [Economic Times]
Simonyi et al., in the paper Intentional Software, state:
For the creation of any software, two kinds of contributions need to be combined even though they are not at all similar: those of the domain providing the problem statement and those of software engineering providing the.implementation. They need to be woven together to form the program.
TDW AgenticOS is the software for building decentralized societies.
A Word about the Future
“Before the next century is over, human beings will no longer be the most intelligent or capable type of entity on the planet. Actually, let me take that back. The truth of that last statement depends on how we define human.” Ray Kurzweil. 1999.
NOTE: “Artificial Intelligence” (or “AI”) does not appear anywhere in the remainder of this article. The northstar of the Web 7.0 project is to be a unified software and hardware ecosystem for building resilient, trusted, decentralized systems using decentralized identifiers, DIDComm agents, and verifiable credentials – regardless of whether the outcome (a Web 7.0 network) uses AI or not. Refer to Figures 4a, 4b, and 6 for a better understanding.
DIDComm Notation, a visual language for architecting and designing decentralized systems, was used to create the figures in this article.
Value Proposition
By Personna
Business Analyst – Ability to design and execute, secure, trusted business processes of arbitrary complexity across multiple parties in multiple organizations – anywhere on the planet.
Global Hyperscaler Administrators – Ability to design and execute, secure, trusted systems administration processes (executed using PowerShell) of arbitrary complexity across an unlimited number of physical or virtual servers hosted by an unlimited number of datacenters, deployed by multiple cloud (or in-house) xAAS providers – anywhere on the planet.
App Developers – Ability to design, build, deploy, and manage secure, trusted network-effect-by-default apps of arbitrary complexity across multiple devices owned by anybody – anywhere on the planet.
Smartphone Vendors – Ability to upsell a new category of a second device, a Web 7.0 Always-on Trusted Digital Assistant – a pre-integrated hardware and software solution, that pairs with the smart device that a person already owns. Instead of a person typically purchasing/leasing one smartphone, they can now leverage a Web 7.0-enabled smartphone bundle that also includes a secure, trusted, and decentralized communications link to a Web 7.0 Always-on Trusted Digital Assistant deployed at home (or in a cloud of their choosing).
Digital Church/Religion Builders – Ability to create a new decentralized digital religion for 1 billion people in Communist China.
By Trust Relationship (Verifiable Trust Circle (VTC))
Secure, Trusted Agent-to-Agent Messaging Model
Figure 0. depicts the design of a typical simple agent-to-agent communications model. DIDComm Notation was used to create the diagram.
TDW AgenticOS: Conceptual and Logical Architecture
The Web 7.0 architecture is illustrated in the following figure.
Figure 1 is an all-in illustration of the conceptual architecture of a Web 7.0 Neuromorphic Agent. A Web 7.0 Agent is comprised of a Frontal LOBE and the Neural Messaging pathway. An Agent communicates with the outside world (other Web 7.0 Agents) using its Outbound (Talking), Seeing, and Inbound (Listening) Interfaces. Agents can be grouped together into Neural Clusters to form secure and trusted multi-agent organisms. DIDComm/HTTP is the default secure digital communications protocol (see DIDComm Messages as the Steel Shipping Containers of Secure, Trusted Digital Communication). The Decentralized Identifiers (DIDs) specification is used to define the Identity layer in the Web 7.0 Messaging Superstack (see Figure 6 as well as Decentralized Identifiers (DIDs) as Barcodes for Secure, Trusted Digital Communication).
An agent remains dormant until it receives a message directed to it and returns to a dormant state when no more messages are remaining to be processed. An agent’s message processing can be paused without losing any incoming messages. When an agent is paused, messages are received, queued, and persisted in long-term memory. Message processing can be resumed at any time.
Additionally, an Agent can include a dynamically changing set of Coordination and Execution LOBEs. These LOBEs enable an Agent to capture events (incoming messages), compose responses (outgoing messages), and share these messages with one or more Agents (within a specific Neural Cluster or externally with the Beneficial Agent in other Neural Clusters (see Figure 5)).
What is a LOBE?
LOBE (Loadable Object Brain Extensions) is a macromodular, neuromorphic intelligence framework designed to let systems grow, adapt, and evolve by making it easy to add new capabilities at any time. Each LOBE is a dynamically Loadable Object — a self-contained cognitive module that extends the Frontal LOBE’s functionality, whether for perception, reasoning, coordination, or control (execution). Together, these LOBEs form a dynamic ecosystem of interoperable intelligence, enabling developers to construct distributed, updatable, and extensible minds that can continuously expand their understanding and abilities.
LOBEs lets intelligence and capability grow modularly. Add new lobes, extend cognition, and evolve systems that learn, adapt, and expand over time. Expand your brain. A brain that grows with every download.
What is a NeuroPlex?
A Web 7.0 Neuroplex (aka a Neuro) is a dynamically composed, decentralized, message-driven cognitive solution that spans one or more agents, each with its own dynamically configurable set of LOBEs (Loadable Object Brain Extensions). Each LOBE is specialized for a particular type of message. Agents automatically support extraordinarily efficient by-reference, in-memory, intra-agent message transfers.
A Web 7.0 Neuroplex is not a traditional application or a client–server system, but an emergent, collaborative execution construct assembled from independent, socially-developed cognitive components (LOBEs) connected together by messages. Execution of a Neuroplex is initiated with a NeuroToken.
Horizontal Unbundling: Coordination and Execution Agents
Figure 2 illustrates how the deployment of Coordination and Execution LOBEs can be horizontally unbundled – with each LOBE being assigned to a distinct Frontal LOBE. This is an extreme example designed to underscore the range of deployment options that are possible. Figure 3 is a more common pattern.
Horizontal Rebundling
Figure 3 depicts a more common/conventional deployment pattern where, within a Neural Cluster, a small, reasonable number of Frontal LOBEs host any collection of Coordination and/or Execution LOBEs.
Minimal Execution Agent (Trusted Digital Assistant)
Figure 4a is an example of a minimal agent deployment pattern that hosts a single Trusted Digital Assistant (TDA) LOBE.
Vertical Debundling: Web 7.0 Neural Clusters
Figure 5 depicts the deployment of a Web 7.0 Neural Cluster. Messages external to the Neural Cluster are only sent/received from the Beneficial Agent. Any additional messaging is limited to the Beneficial, Coordination, and Execution LOBEs deployed within the boundary of a Neural Cluster. A use case that illustrates the Neural Cluster model can be found in Appendix D – PWC Multi-Agent Customer Support Use Case.
DIDComm 7.0
Figure 6a is an all-in illustration of the conceptual architecture of a Web 7.0 Neuromorphic Agent. DIDComm Messages can be piped from the Outbound Interface of the Sender agent to the Inbound Agent of of Receiver agent – supporting the composition of secure, trusted agent-to-agent pipelines similar (but superior) to: i) UNIX command pipes (based on text streams), and ii) PowerShell pipelines (based on a .NET object pump implemented by calling ProcessObject() in the subsequent cmdlet in the pipeline).
NOTE: PowerShell does not clone, serialize, or duplicate .NET objects when moving them through the pipeline (except in a few special cases). Instead, the same instance reference flows from one pipeline stage (cmdlet) to the next …neither does DIDComm 7.0 for DIDComm Messages.
Bringing this all together, a DIDComm Message (DIDMessage) can be passed, by reference, from LOBE (Agenlet) to LOBE (Agenlet), in-memory, without serialization/deserialization or physical transport over HTTP (or any other protocol).
| PowerShell | DIDComm 7.0 |
| powershell.exe | tdwagent.exe |
| Cmdlet | LOBE (Loadable Object Brain Extension) |
| .NET Object | Verifiable Credential (VC) |
| PSObject (passed by reference) | DIDMessage (JWT) (passed by reference) |
| PowerShell Pipeline | Web 7.0 Verifiable Trust Circle (VTC) |
| Serial Routing (primarily) | Arbitrary Graph Routing (based on Receiver DID, Sender DID, and DID Message type) |
Feedback from a reviewer: Passing DIDComm messages by reference like you’re describing is quite clever. A great optimization.
Coming to a TDW LOBE near you…
DIDComm 7.0 Superstack
Figure 6b illustrates the interdependencies of the multiple layers within the DIDComm 7.0 Superstack.
Technology Wheel of Reincarnation: Win32 generic.c
References
SSI 7.0 Identity Framework
SSC 7.0 Metamodel
SSC 7.0 Verifiable Trust Circles
Web 7.0 Neuromorphic Agent Identity Model (NAIM)
Figure 7. Web 7.0 Neuromorphic Agent Identity Model (NAIM)
The NAIM seeks to enumerate and identify all of the elements in the AARM that have or will need an identity (DID and DID Document). This is illustrated in Figure 7.
Beneficiaries, Trustees, and Fiduciary Duty
Figure 8 highlights in red the trusts and fiduciary duty relationships between (a) a Beneficiary (Alice, the person) and (b) her Beneificiary Agent (a trustee). Similarly, any pair of agents can also have pair-wise trusts and fiduciary duty relationships where one agent serves in the role of Beneficiary and the second agent, the role of Trustee.
Appendix A – TDW AgenticOS: Edge Agent DMZ Deployment
This section is non-normative.
Appendix B – TDW AgenticOS: Multiple Digital Persona Deployment
This section is non-normative.
Alice has 2 digital personifications: Alice Smith and Alice Athlete. Each of these personifications has its own digital ID. Each of Alice’s personas also has its own Trusted Digital Assistant (TDA) – an agent or agentic neural network.
Bob has (at least) 4 digital personifications: Bob Aggie, Bob Nova, Bob Sovronia, and Bob Developer. Using Web 7.0 Trust Graph Relationships and Verifiable Trust Credentials (VTCs), Bob can also have personas that are members of multiple Web 7.0 networks.
Appendix C – Different Brain Functionalities and Their State of Research in AI (2025)
Source: Advances and Challenges in Foundation Agents: From Brain-Inspired Intelligence to Evolutionary, Collaborative, and Safe Systems. arXiv:2504.01990v2 [https://arxiv.org/abs/2504.01990v2]. August 2025.
In Figure C-3, the Trust Library forms the Inner core and the UX LOBEs, the Crust. The Outer core is comprised of the Fast Cache and Long-Term Memory LOBEs, Neural and Basal Pathways, DID Registry, and LOBE Library. The Mantle is where the Coordination and Execution LOBEs execute.
Appendix D – PWC Multi-Agent Customer Support Use Case
Source: Agentic AI – the new frontier in GenAI. PWC Middle East. 2024.
This use case exemplifies the use of the Web 7.0 Neural Cluster model. Table D-1 maps the PWC Use Case terminology to the corresponding Web 7.0 AARM terminology.
| Web 7.0 NAARM | PWC Use Case |
| Beneficiary Agent | Master agent |
| Coordination Agent (and LOBEs) | Orchestrator agent |
| Execution Agent LOBEs | Micro-agents |
Appendix E – Groove Workspace System Architecture
Resources
Macromodularity
- Organization of computer systems: the fixed plus variable structure computer. Gerald Estrin. 1960.
- Macromodular computer systems. Wesley Clark. 1967.
- Logical design of macromodules, Mishell J. Stucki et all. 1967.
Powered By
Michael Herman
Decentralized Systems Architect
Web 7.0 Foundation
October 15, 2025
Filed under Uncategorized
Google’s Strategic Response to Super Apps
Create your own magic with Web 7.0 AgenticOSs. Imagine the possibilities.
Copyright © 2025 Michael Herman (Bindloss, Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
Google’s Strategic Response to Super Apps
Platform Layer: Defensive Flexibility
- Android modularization: Google could further modularize Android (e.g. via Project Mainline, Play Services) to allow more granular control over APIs and updates—making it easier to support or restrict super app behaviors.
- Policy recalibration: In response to regulatory pressure (e.g. DMA in Europe), Google may loosen Play Store restrictions, support alternative billing, and allow more sideloading to stay competitive.
Developer Layer: Ecosystem Incentives
- Play Console evolution: Google could offer new SDKs and monetization APIs tailored for mini-apps or embedded services, encouraging developers to build within Google’s ecosystem rather than third-party super apps.
- Firebase + App Actions: Deep integration with Google Assistant, Search, and Android widgets could give developers super app-like reach without needing a host app.
Distribution Layer: Search as a Super App
- Google Search + Discover + Assistant already function as a meta-layer for app discovery and engagement. Google may double down on this by:
- Surfacing app content directly in search results
- Promoting App Clips / Instant Apps
- Offering deep links into services without full app installs
Monetization Layer: Bundled Value
- Google One + Pixel Pass: Bundling cloud, security, and device services into a subscription model mimics super app economics.
- Play Points + Wallet: Loyalty programs and integrated payments could be expanded to create a unified commerce layer across apps.
User Layer: Identity & Privacy
- Google Identity Services: Strengthening federated login, cross-app personalization, and privacy dashboards positions Google as a trusted identity broker.
- Privacy Sandbox: Google’s push for privacy-preserving ad tech (e.g. Topics API) could be framed as a safer alternative to super app data centralization.
Strategic Narrative
Google doesn’t need to build a super app—it already operates one in disguise. Android + Search + Assistant + Wallet + Play Store form a distributed super app ecosystem. The challenge is coherence: can Google unify these services into a seamless user experience without triggering antitrust alarms?
Filed under Uncategorized
Web 7.0™ / TDW AgenticOS™ / TDW™ / Hyperonomy™ Digital Identity Lab 