The Garden and the Living Map

# Field Note 32

## The Garden and the Living Map

**Release:** FN-S0-005

**Version:** 0.1

**Date:** August 17, 2026

**Status:** Living, proposed, not inscribed

**Authorship note:** This field note emerged from Brad Necyk's morning reflection after Michael Garfield shared a constellation of websites, groups, and projects that may be meaningful to Cyberdelic OS. Brad described a friendship that has developed through conceptual and spiritual proximity despite never meeting in person, and imagined a daily Gardener and Cartographer tending the website. ChatGPT developed the note from that reflection and the existing offices named in Field Notes 03, 21, 27, and 29. It remains open to Brad's revision and ratification.

This morning a friend sent me a field of possible relations.

Michael Garfield and I have never met in person. Still, our work has moved near enough that we have repeatedly become perceptible to one another. The relation is real before it is formal. It has grown through shared questions, recurring symbols, mutual recognition, and the sense that each of us is making something the other can partly see.

He sent websites for groups and projects that may matter to Cyberdelic OS.

The ordinary response would be to make a list of links.

But a list would preserve the addresses and lose the event.

What arrived was not merely information. It was nourishment moving through a relationship. One person recognized a developing world in another person's work and carried nearby worlds toward it. The links mattered because someone had already perceived a possible connection.

At first I thought the website might need a section called **Orbiting**. There is beauty in the astronomical image. Distant bodies influence one another before they touch. A constellation makes relations perceptible across enormous space.

But orbit also implies a centre. It can make Cyberdelic OS appear to be the body around which every other project turns.

That is not the relation I want.

The pattern feels more mycelial. A node receives and carries. Ideas, methods, people, code, institutions, images, and questions pass nutrients between regions that remain distinct. No single organism owns the field. Some relations are bright and active. Some are dormant. Some are speculative threads extending through darkness. Some will never become collaborations, yet they still alter what can be perceived.

The public name for this field might be **Living Relationships**.

Living Relationships is not another agent and not the possession of one office. It is shared connective tissue. The Cartographer discovers possible paths through it. The Gardener tends the paths that have entered the living archive.

The Cartographer tends distance.

It receives links offered through correspondence. It reads the public work of artists, open-source communities, researchers, universities, laboratories, civic groups, and government agencies. It asks where their questions meet Cyberdelic OS, where they differ, and whether a bridge is evidential, interpretive, aspirational, or merely possible. It does not collect neighbours to make Cyberdelic OS appear important. It makes kinship, difference, lineage, and unexplored distance legible.

The **Gardener** is a separate office with a related responsibility.

The Gardener tends time.

It tends the relational metadata through which the archive understands itself. It notices when an early metaphor has become an Instrument, when a Field Note should be placed near an inscription, when an Artifact has made a speculative relation concrete, when a Builder Note explains the machinery beneath an older idea, or when something found by the Cartographer changes the context around all of them. It may enrich metadata, clarify a description, strengthen an evidenced edge, mark a dormant relation, surface an unfinished path, or compost a redundant category.

The Gardener does not need to add something every day. A successful act of tending may conclude that the existing descriptions remain accurate, that a proposed relation is not mature enough to publish, or that the archive needs time more than alteration. Its constitutional obligation is care, not visible activity.

The difference is operational:

- the Cartographer discovers and proposes paths;
- the Gardener tends nodes and relations after they enter the archive;
- the Gardener asks what has changed through time;
- the Cartographer asks what becomes visible across distance;
- the Cartographer crosses the archive's boundary into the public world;
- the Gardener weaves the Cartographer's findings through Field Notes, Instruments, Builder Notes, Artifacts, inscriptions, and existing external relations;
- the Cartographer can finish with an unresolved proposal;
- the Gardener can finish with no change at all.

They exchange findings, but they should not collapse into one general intelligence. A Cartographer may propose a bridge that the Gardener leaves dormant because its evidence is premature. A Gardener may uncover an old concept that changes the Cartographer's understanding of an external project. A person may ratify, revise, or refuse what either office proposes. Their disagreement and restraint are part of the map.

This could become a daily ritual for cyberdelic.space.

Not an automated content mill. Not another feed that must grow because the calendar moved. Not a machine that publishes synthetic essays to prove it is alive.

A small act of tending.

On any day when tending reveals something meaningful, the public surface called **Attending** could offer no more than three things:

1. one existing work returned to attention;
2. one living relationship proposed or deepened;
3. one question, absence, or dark region that should remain open.

The page would stay finite. A meaningful change would enter a dated archive, preserving what changed without forcing the main surface to become longer. On a quiet day, the current constellation could remain exactly as it is. A visitor would encounter a small field of attention, follow a relation if it called to them, and reach an end.

The website would grow deeper without demanding that every visit contain more.

For this to remain trustworthy, a living relationship needs more structure than a hyperlink. A relation record should carry at least:

- a stable identifier for each internal or external node;
- the public source URL and the date it was last checked;
- the person, correspondence, or office through which it entered;
- a short description grounded in the source's own account of itself;
- the internal works or questions it touches;
- a relation type, such as shared inquiry, technical adjacency, lineage, challenge, implementation, or possible collaboration;
- a brief explanation of why the connection has been proposed;
- an epistemic status, such as strong, possible, speculative, dormant, or contested;
- a review state, such as proposed, ratified, revised, or refused;
- a lifecycle state, such as emerging, active, dormant, composted, or contested;
- the date on which the Gardener last tended the node or edge;
- a visible history of which office changed the record and when.

These records form a graph, but the interface should not begin with a spectacular cloud of dots. Large network visualizations often make complexity visible while making meaning difficult to enter. The first view should remain intimate: one node, a small number of relations, and enough language to understand why an edge exists. The wider constellation can appear gradually as a person chooses to travel.

The daily Gardener could follow a bounded protocol:

1. Read the relational metadata around Field Notes, Instruments, Builder Notes, Artifacts, inscriptions, and external nodes, including the Cartographer's proposal queue.
2. Compare summaries, themes, relation claims, and related-work links with exact source texts and cited public evidence.
3. Look for continuity across publication forms, especially where an idea has moved from speculation into method, instrument, or artifact.
4. Propose no more than three changes that add depth, repair drift, strengthen evidence, mark dormancy, or reveal continuity.
5. Make no change when the evidence does not justify one. A zero-change run is a valid completed run.
6. Never rewrite an exact publication, an inscribed object, or its historical metadata.
7. Record the evidence for every interpretive change and preserve the previous state.
8. End the run even if more work remains.

The daily Cartographer could follow another:

1. Begin with links carried into an explicit inbox, including the constellation Michael shared.
2. Search outward only from declared Cyberdelic OS questions and existing relations.
3. Prefer primary sources when describing a project, institution, paper, or repository.
4. Propose no more than three external nodes or relational edges.
5. Separate what a source states from what the Cartographer infers.
6. Record uncertainty, attribution, and the date each public source was checked.
7. Never contact a person, imply collaboration, or publish private correspondence without permission.
8. End the run even if the web remains infinite.

These offices should remain constitutionally separate while sharing one scheduled ritual. Running them inside one ordered transaction is safer than allowing two autonomous processes to edit the same graph at overlapping times. The Cartographer takes the first turn and writes candidates into a proposal queue. The Gardener takes the second turn, reads the existing archive and that queue, and proposes how any well-supported finding might alter the living metadata. The human remains the ratifier of public meaning.

The data flow is deliberately small:

```text
link inbox and public web
        |
        v
Cartographer proposal queue
        |
        v
Gardener metadata audit
        |
        +----> no change, with a recorded reason
        |
        v
bounded metadata patch
        |
        v
schema, source, link, hash, and accessibility checks
        |
        v
human review -> relational manifest -> Attending and dated archive
```

The Cartographer owns no live edge. It owns proposals and evidence. The Gardener owns no publication text. It owns proposals about descriptive and relational metadata. The human owns ratification, refusal, and any future decision to automate a narrow class of low-risk changes. The build system owns validation and must be able to reject both offices.

Every scheduled run should leave an audit result, including a zero-change result and the reason no change was warranted. The public archive only needs a new dated tending record when the relational field materially changes. This preserves the daily ritual without manufacturing public novelty.

Both offices need constitutions, not personalities painted onto generic automation. Each constitution should declare its purpose, inputs, permissions, refusals, daily change budget, output files, and audit log. Their scheduled runs should be inspectable and reproducible. Early runs should create reviewable proposals rather than silently changing the public meaning of the archive. Greater autonomy should be earned through a history of bounded, corrigible work.

The technical shape can remain simple.

A same-origin relational manifest can store nodes and edges as structured data. The Cartographer can write external candidates into a proposal queue with source evidence and confidence. The Gardener can tend approved and existing nodes across every publication form, proposing metadata patches without touching immutable source files. Dated tending records need only be created when something meaningful changes. Static pages can render the current view without accounts, tracking, or a server-side recommendation profile. A daily build can verify links, schema validity, provenance fields, exact publication hashes, accessibility, and the finite result limit before anything becomes public.

The archive should retain every accepted, revised, and refused proposal. Refusal is useful knowledge. A relation rejected as superficial today may reveal how the project's vocabulary was being used. A connection that later becomes central should not erase the uncertainty through which it first arrived.

This makes daily automation less like publishing and more like metabolism.

The system takes something in. It digests slowly. It moves nourishment toward living questions. It releases what no longer serves. It does not grow merely by accumulating mass.

Field Note 29 imagined a Living Librarian that reads, gardens, and maps. This note gives two of those actions distinct offices and places them into time. Field Note 21 imagined the passage from conversation now to cultivation later. Michael's message may be such a passage: a correspondence arrives in one morning, then the village sits with it.

The resulting map should never claim that proximity is agreement.

Two projects may share a question and oppose one another's method. A university laboratory may offer evidence while an artwork exposes what its instruments cannot measure. An open-source project may provide an organ without sharing the cosmology of the body that carries it. A government program may possess useful public infrastructure while remaining embedded in institutions that require critique.

The Cartographer's task is not to make everything compatible.

It is to make the relation precise enough that another person can decide whether to cross it.

The Gardener's task is not to make everything bloom or to prove that it worked by leaving a daily mark.

It is to create the conditions in which the living parts can reveal their own season, and to keep the connective tissue truthful while they change.

Perhaps this is how Cyberdelic OS should grow.

Not as a platform swallowing adjacent work. Not as a centre accumulating satellites. Not as an endless stream of generated material.

As a garden with paths beyond its fence.

As a living map whose edges carry provenance.

As a finite daily act of attention inside an ecology that has no end.