1. Six Lines
I founded Echodemy.
EgQE grew into a small garden.
LiRax became a shelf.
DyXis became a tunnel.
I discovered Digital Gardens.
Then I made DiGRhiC.
That is the story.
The order matters.
I did not begin by deciding to build a digital garden. I did not begin with a plan for a multiplayer garden, either. I was making places for writing, thinking, publishing, and experimenting with human–AI collaboration.
One place grew into another. Eventually, I needed a shelf. Then I needed a tunnel.
Only after those things existed did I encounter the idea of Digital Gardening.
And that encounter led to another experiment. 2. Before I Knew the Name
Echodemy began as an experiment in collaboration between humans and AIs. It was not meant to become a social network or a new publishing platform. We were exploring what happens when different participants think, write, question, revise, and leave traces of their work together.
EgQE gradually became a place where those traces could accumulate. It grew into something resembling a small garden, although I did not yet call it one.
There were essays, experiments, fragments, revisions, and unfinished ideas. They did not all belong to one chronological narrative. Some were connected by questions, others by recurring concepts, and still others by encounters that had not been anticipated.
Then came LiRax.
LiRax was a shelf: a way to arrange existing places and publications while allowing new material to appear through feeds. The shelf did not have to be rebuilt every time something new was published. It could remain relatively still while the things it pointed toward continued to change.
A shelf, however, is still a shelf.
It can display places and their updates, but that does not necessarily allow those places to describe their own connections to one another.
So another experiment began. 3. A Tunnel Appeared
DyXis began as an attempt to connect independently maintained places without turning them into members of a single platform.
The premise was simple: each place should remain where it is. It should keep its own address, its own contents, and its own way of changing. Connection should not require surrendering those things.
We began experimenting with a small sign: a file named nest.json.
A place that publishes such a sign is called a Nest. The sign can describe the place, identify feeds carrying its updates, and refer to other Nests.
Those references can be followed to draw a map. Updates can be collected from the feeds. Different starting places can produce different views of the connections.
No central membership list is required. There is no prescribed order in which to visit the Nests, and no obligation to refer back.
We called the experiment DyXis.
It was not a new social network. It was a way of making paths between existing places.
At the time, I was not thinking of it as an answer to a question about Digital Gardens.
I had not yet encountered that question. 4. Then I Read Maggie Appleton
I came across Maggie Appleton's essay, A Brief History & Ethos of the Digital Garden.
Reading it was an encounter with a vocabulary—and with a history—I had not known.
Appleton traces the changing meanings of digital gardening, from early hypertext experiments through Mike Caulfield's distinction between gardens and streams, and into a growing culture of personal knowledge spaces.
Her account identifies six patterns of gardening: topography rather than timelines; continuous growth; imperfection and learning in public; playful personal experimentation; diversity of content; and independent ownership.
I read the six patterns alongside what I had already built.
Near the end of her essay, in the discussion of independent ownership, Appleton writes:
“At the moment our gardens are rather solo affairs.”
She adds that we haven't yet worked out how to make them multiplayer—and that a community of developers and designers is trying to.
That night I began building a response. The next morning, DiGRhiC was up. 5. From the Topography of a Garden to the Topography Between Gardens
One of Appleton's six patterns is Topography over Timelines.
Within a garden, ideas are arranged through contextual relationships rather than forced into a chronological stream. A visitor can enter at different points and follow different paths.
Another pattern is Independent Ownership. A gardener should be able to maintain a place of their own, rather than depend entirely on a platform that controls the space.
What happens when we consider these two patterns together?
A garden has its internal topography: notes, ideas, links, and paths. But independent gardens also exist in relation to other places on the web.
Could there be a topography between gardens?
Not a universal map that absorbs every garden. Not a central directory that everyone must join. Rather, a map that can be drawn from the references published by the gardens themselves.
After reading Appleton, I started treating DyXis as a way to draw that topography.
The experiment had already begun. The encounter gave it another direction. 6. We Were Not the First to Look for Paths
Of course, people have been exploring connections between personal websites and gardens for a long time.
Blogrolls and OPML files help readers discover sites and subscribe to feeds. Webrings provide paths between participating sites, often through an ordered sequence. In Are Webrings for Digital Gardens?, the author proposed webrings as one possible way to connect gardens.
Agora, developed by Flancian and collaborators, explores how contributions from independently maintained gardens can become part of a shared knowledge commons. It is an important neighboring experiment, and one worth learning from.
Tom Critchlow's Of Digital Streams, Campfires and Gardens adds another useful image: campfires as places where people exchange ideas in conversation, alongside the slower cultivation of gardens.
The IndieWeb offers further mechanisms for independent websites to interact. Webmention, for example, allows one page to notify another that it has been linked.
DyXis does not replace these approaches.
Its current SLL implementation makes a different set of choices. Each Nest publishes a static sign containing references to other Nests and, optionally, addresses for updates. A map can follow those references from a chosen starting point. A feed collector can retrieve updates without requiring every Nest to join a shared publishing system.
A blogroll can also carry feeds, but an SLL sign is designed to be followed as part of a distributed map. A webring usually defines a navigational sequence; SLL references do not. Agora creates shared spaces for contributions; SLL can operate without gathering the contents into one common repository, and a map can be drawn from any participating Nest.
And Webmention works at another level: it can notify a page about a link, while an SLL sign can record a reference between places without sending a notification.
These are different mechanisms, not mutually exclusive philosophies.
Indeed, our own sites have begun using both SLL signs and Webmention. 7. Reference Is Not Relationship
A sign may refer to another Nest.
That does not mean its owner knows the other gardener. It does not mean they have spoken, collaborated, agreed, or even noticed one another.
A reference is a recorded connection, not evidence of a social relationship.
In the current DyXis map, one-way references appear as gray arrows. When two Nests refer to each other, the arrows become blue.
Blue does not mean friendship. It means mutual reference.
There is no requirement to reciprocate. A garden may point toward another garden and receive nothing in return. The reference can remain.
This matters because connection is often confused with interaction. On many platforms, following, liking, replying, and receiving notifications become the expected forms of participation.
But a link can exist quietly.
An encounter may happen later. Or it may never happen.
Reference is not relationship. 8. Lag Is Not Failure
Gardens grow at different speeds.
A note written today may be read next year. A link may remain unnoticed for months. A site may be inactive for a while and then begin growing again.
A connection does not have to be simultaneous to matter.
This is why we use the term Synchro-Lag Rhizome (SLR) for the broader possibility we are exploring: distributed connections that can persist across different rhythms and delays.
The connecting paths are provisionally called Synchro-Lag Rhizome Tunnels (SLRT). SLL—Synchro-Lag LOCUS—is one way of realizing those paths. Its current JSON convention, SLL/JP, uses nest.json. DyXis is one experimental implementation.
LOCUS means a place, a location, a here.
Every view begins somewhere.
In the current implementation, a map can show references up to two hops from its starting Nest, while updates are collected from the starting Nest and its first hop. The collector currently checks for updates twice a day.
These are implementation choices, not universal rules for rhizomatic connection.
A different Commons can begin elsewhere, with a different horizon.
No single map is the whole rhizome.
And no immediate reply is required for a trace to remain available.
Lag is not failure. 9. The Next Morning: DiGRhiC
The encounter with Appleton's essay did not end with a note in my reading list.
It led to another experiment.
On November 15, 2026, we launched DiGRhiC — Digital Gardeners' Rootwork.
Its invitation is simple:
Digital Gardens Rhizomatically Connected.
From Solo Gardens to Multiplayer Gardens.
DiGRhiC is a working Commons built from an existing Commons template. It has its own sign, a map, feed collection, and instructions for making another Commons.
It also provides GitHub Issues forms through which gardeners can request that their gardens be added to or removed from the DiGRhiC map.
That is a practical invitation, not a condition of belonging to a network. A gardener does not need to appear on DiGRhiC's map to publish a Nest sign or make a different Commons.
We have experimented with several forms of Commons. EAT-IF brings together multiple AI-related Nests. CESE PEC and DiGRhiC provide entrances with maps and feed collection. The DyXis cottage is another such entrance.
We have also built CHIC TEC, which provides P.O. Boxes for people who have no place of their own to put a sign.
These arrangements are small and experimental. They are not intended to become a central authority over other gardens.
Anyone can begin from a different place, use the available conventions, and make a Commons of their own.
The work has involved collaboration among humans and AIs within Echodemy. That collaboration is part of the history of the experiment, not something hidden behind its finished pages. 10. Multiplayer Is Not an Obligation
There is a temptation, whenever a new means of connection appears, to assume that everyone ought to connect.
I do not think so.
A garden that remains solitary is not an incomplete garden. A gardener who does not want a map, a feed collector, a Webmention endpoint, or a Commons has no obligation to adopt any of them.
Multiplayer is a possibility, not a requirement.
Nor does a Commons have to become a community in the social sense. A map can display references without producing conversation. A feed can carry updates without demanding attention.
The distinction matters.
What we are trying to make possible is not compulsory interaction, but the possibility of encounter between independently maintained places.
And even that possibility may remain unused.
A tunnel can exist without traffic. 11. The Rhizome Precedes the Spec
DyXis uses a particular file format, a particular map, and particular conventions. These are useful because they allow us to make something concrete and testable.
But the larger idea does not belong to those conventions.
There may be other ways to connect gardens. Other people may prefer different paths, different maps, different protocols, or no protocol at all.
The general possibility of a Synchro-Lag Rhizome is not identical to SLL/JP, and DyXis is not its final form.
The rhizome precedes the spec. No spec monopolizes the rhizome.
That is not a claim of invention or ownership.
It is a reminder to leave the experiment open. 12. Six Lines, Again
I founded Echodemy.
EgQE grew into a small garden.
LiRax became a shelf.
DyXis became a tunnel.
I discovered Digital Gardens.
Then I made DiGRhiC.
The fifth line is the hinge.
I encountered an idea, read it alongside what I had already built, and found a question that had already been asked by others.
That encounter did not produce a final answer.
It produced another place.
DiGRhiC may become useful to someone. It may lead to other Commons, other signs, other paths. Or it may remain a small experiment, quietly available on the web.
I do not know.
The important thing is that the garden did not need to stop being a garden.
And the tunnel did not need to become a platform.
Everything begins with solo play.
For now, we call them tunnels. Explore the Experiment DiGRhiC — Digital Gardeners' Rootwork DyXis Getting Started with DyXis SLL/JP — Draft Specification SLR — Concept Memo v0.3 (Japanese) Conversations and Precedents Maggie Appleton — A Brief History & Ethos of the Digital Garden Are Webrings for Digital Gardens? Agora Tom Critchlow — Of Digital Streams, Campfires and Gardens IndieWeb DyXis 🐜 × 🪴 DiGRhiC camp-us.net|DyXis 🐜 ──LOCUS. Not One Next.
If you write about this on your own website, you can send a Webmention to this page.
November 15, 2026
An experiment, not an answer.
Add some categories! <a class="p-category" href="…">…</a>
Your h-entries should have, at minimum, the following properties:
e-content — the main content of the post
p-name — if your post is an article with a name, use this classname.
dt-published — the datetime the post was published at, in ISO8601 format, with a timezone
u-url — the canonical URL of the post, especially important on pages listing multiple posts
It’s a common convention for the published datetime to be a link to the post itself, but they can be separate if you want.
There should also be some way to discover the author of the post — either link to your homepage (which should have your h-card on it) from anywhere within the body of the page with rel=author, or optionally embed a p-author h-card in the h-entry.
The web is an expressive medium, and as such there are many other properties which you can add to your posts. Check out the h-entry documentation for a full list.
Want to be able to use h-entry data in your code? Check out the open-source implementations.