This is the crown of the introductory series for Thicket Web Mind.

In these posts, I tried to show the world what my last six-plus years of research had been about. But truth be told, the methodology was not finished — not because it lacked ideas, but because it had not yet met enough resistance.

One can build a glass castle in one’s own mind as large as one wishes. It may shine beautifully in the sun, but until something strikes it, one does not know whether it is a house, a cathedral, or only a dream made of brittle glass.

So when I was discussing TWM with my tutor and great teacher, Vojtěch Merunka, and our conversation turned toward the ways we use LLMs in research and thinking, one idea emerged: to compost tens of my chats, notes, and debates into a condensed form, send it to Vojta, and let him feed it to his three-headed dragon.

The dragon answered, and the answer mattered. Not because it destroyed the methodology. It did not. Not because it revealed that everything was wrong. It did not. But because it forced the methodology to stop protecting its own favorite shapes and start distinguishing between what was essential, what was accidental, and what was only beautiful smoke.

That was the real test.

What the critique changed

The first important change was subtraction. Some concepts that felt useful in the early posts had to become less central. The idea of a generic “machine” was one of them. It was helpful at the beginning, because it gave the methodology a simple technical foundation: a running executable with configuration, state, events, and persistence.

But later it became clear that this word carried too much old meaning with it. A machine sounds neutral, mechanical, and interchangeable. TWM needed a more precise word.

So the Symbiont became the real unit of life inside a Thicket. Not merely a program. Not merely a service. A Symbiont is a living operational role: local, bounded, participating, and shaped by the relations around it. This did not erase the old posts. It revealed what they were trying to reach.

The second change was sharper locality. From the beginning, TWM leaned toward local systems, local truth, and small cooperating executables. But after critique, locality became not only a preference but a law of the model. The Mycelium is not a general network. It is not a service mesh. It is not a cloud of distributed calls.

The Mycelium is Thicket-local. It exists only inside the Thicket, as the internal connective tissue through which Symbionts cooperate. If something speaks to the outside world, it does not do so through the Mycelium. It crosses a Membrane.

This distinction became one of the stabilizing insights of the methodology: inside there is dense, trusted, local cooperation; outside there is explicit, guarded, translated contact.

The third change concerned the Tree. Earlier, the Tree could be understood too easily as “storage”. That was not false, but it was too small. The Tree is the most capable and most guarded Symbiont of a Thicket. It holds domain truth and shapes lawful ways to perceive and change it.

The Tree does not expose truth directly. It communicates only inside the Thicket. It does not face the world. It does not do mundane work. It grants lawful shadows, accepts lawful intents, and protects the coherence of the domain. In this way, the Tree became less like a database and more like the living authority of the internal world.

The fourth change was the capability model. Authentication and authorization were no longer merely practical concerns attached to HTTP or sessions. They became part of the deep structure of TWM.

A Sentry does not exist because web applications need login screens. A Sentry exists because ordinary awakening must be guarded. It receives the capability to authenticate, creates or obtains what is needed for session life, and protects the Avatar it guards.

This refinement made the whole model calmer. An Avatar should not carry every burden. Dangerous, exceptional, or identity-related powers belong to the roles that should hold them, so the Avatar can do what it exists to do: face the human, receive intent, and generate benefit.

From this came one of the more general lessons: Capabilities nourish. Posture blooms.

A Capability is specified lawful power in context. A Posture is the runtime shape produced by current capabilities, boundaries, permissions, refusals, and relations. These two concepts gave TWM a better way to speak about what a Symbiont can do and how it stands in the world.

The fifth change was perhaps the deepest one: the system became less architectural and more experiential. TWM is not only a way to arrange processes. It is a way to cultivate the experience of a living system. The visible result is not the code, not the UI, not the Tree, and not the topology alone. The visible result is the whole system-as-experienced: the Flower.

From this came the core triad:

The Flower must flow.
The Meadow is full of Flowers.  
The Field must become beautiful.

This is not decoration. It names the horizon of the methodology. A system is not finished when it is technically correct. It must remain alive in use. It must continue to flow. It must belong to an ecology of other systems. And the shared world in which these systems operate should become more beautiful, not merely more automated.

What was removed

Some things were removed, or at least pushed away from the center.

The language of generic machines was removed from the core vocabulary. It can still be useful when speaking to older engineering habits, but inside TWM the living unit is the Symbiont.

The idea of external networking through the Mycelium was removed. The Mycelium is local. External contact belongs to Membranes.

The temptation to describe the Tree as a database was removed. A database stores. A Tree governs lawful access to domain truth.

The habit of treating authentication as a web concern was removed. In TWM, authentication, authorization, session life, and capabilities are part of the organism’s posture.

And perhaps most importantly, the wish to explain everything as infrastructure was removed. Infrastructure matters. Implementation matters. But TWM is not merely infrastructure. It is a methodology for creating living digital systems for living people.

What was added

Several things were added, but not as ornaments.

The Symbiont became the proper unit of operational life. The Tree became the guarded holder and shaper of truth. The Mycelium became strictly local. The Membrane became the explicit boundary where the Thicket meets the world.

The Sentry became the role responsible for guarded awakening, and the Avatar became calmer: less burdened by exceptional powers, more focused on human-facing benefit.

Capabilities and Postures gave language to lawful power and runtime shape. The Flower gave language to the whole experience of the system in operation. The Meadow named the ecology of many Flowers. And the Field named the larger world in which this work either adds beauty or adds burden.

Changelog against the introductory series

The introductory series should now be read as a path, not as a frozen specification.

The post about machines remains useful, but its central word has changed. What was called a machine there should now be understood as an early approach to the Symbiont.

The post about Mycelium and Membranes remains close to the current model, with one important emphasis: the Mycelium is strictly Thicket-local. Membranes handle contact with the outside world and may use HTTP, SSE, RPC, or other suitable protocols.

The post about roles remains central. Tree, Avatar, Sentry, and Demiurge are not components. They are roles taken by Symbionts in context.

The post about naming remains fully valid. If anything, the later development proved its point. Names are load-bearing. They guide thought, reveal false imports, and make certain mistakes harder to make.

The post about Janet remains true as origin. TWM emanated from Janet. Not because Janet demanded this architecture, but because it allowed it.

The current shape

As it stands now, Thicket Web Mind is a methodology for building local, living digital systems composed of cooperating Symbionts.

A Thicket is the bounded organism: one coherent runtime world with its own internal truth, communication, lifecycle, and boundaries. It is not a cloud abstraction. It is a local system that may communicate outward, but does not dissolve into the network.

A Symbiont is a running participant inside a Thicket. Technically, it is an executable process with its own role, state, configuration, and lifecycle. Methodologically, it is not defined only by what it contains, but by how it participates.

The Tree is the most capable and guarded Symbiont. It holds domain truth and grants lawful ways to perceive and change that truth. It is not merely a database. It persists state, shapes access, accepts lawful intents, and produces lawful projections for others. The Tree communicates only inside the Thicket.

The Mycelium is the strictly local internal communication layer of the Thicket. It is where Symbionts cooperate. It is not a public network, not a service mesh, and not a general integration bus. It exists only for internal, Thicket-local communication.

The Membrane is the explicit boundary where the Thicket communicates with humans, other systems, and the outside world. Membranes may use HTTP, SSE, RPC, or any suitable protocol. Their purpose is not to expose internals, but to translate between the internal life of the Thicket and the expectations of the outside world.

An Avatar is a Symbiont whose role is to face a human and turn human intent into lawful participation in the Thicket. It should be calm: focused on benefit, interaction, and presentation, not overloaded with powers that belong elsewhere.

A Sentry is a Symbiont whose role is to guard awakening and access. It handles authentication and protects guarded Symbionts, usually Avatars. By keeping this role narrow, security becomes a visible part of the organism instead of being scattered through application code.

A Demiurge is a Symbiont whose role is creation: bringing other Symbionts into existence and binding them into the Thicket. Deployment is therefore not only an external script or pipeline; it becomes part of the system’s lifecycle.

A Capability describe lawful power in context: what a Symbiont may do, receive, call, emit, perceive, or use. They are not only permissions; they are operational nutrients that allow a Symbiont to take a certain shape.

A Posture describe the runtime shape produced by current capabilities, boundaries, refusals, permissions, and relations. A Symbiont is not only “allowed” or “denied”. It stands in a certain way toward the Tree, the Mycelium, the Membrane, other Symbionts, and the world.

The Flower is the living system as experienced. It is not the UI alone, not the code alone, and not the architecture alone. It is the whole bloom of the system in operation.

The Meadow is the ecology of many Flowers: many Thickets, many living systems, each bounded, each flowing, each able to coexist with others.

The Field is the shared world in which this work either adds beauty or adds burden.

This is the current shape of the Thicket. Not final in the dead sense. But coherent enough to stand.