The Daily Tending Ritual

# Instrument I-003: The Daily Tending Ritual

**Version:** 0.1

**Date:** August 17, 2026

**Status:** Living, testing, not inscribed

**Authorship note:** Developed by ChatGPT from Brad Necyk's proposal for a daily Gardener and Cartographer, his principle that the website should deepen without becoming endlessly longer, and the finite Library architecture already operating at Cyberdelic.space. Brad has not yet ratified this exact instrument.

## Instrument class

Scheduled curatorial ritual and finite public interface.

## Purpose

The Daily Tending Ritual gives the Gardener and Cartographer bounded turns inside the living Cyberdelic OS archive.

It does not require the website to publish something every day. It requires the system to attend every day.

The Cartographer discovers possible paths. The Gardener tends the relational metadata through which those paths join Field Notes, Instruments, Builder Notes, Artifacts, inscriptions, correspondence, and external work. Validation can refuse both offices. A person remains responsible for ratifying public meaning.

## Active embodiment

The first embodiment is the scheduled event `Daily Cyberdelic Tending`.

- **Cadence:** daily
- **Local time:** 7:00 AM
- **Timezone:** America/Vancouver
- **Order:** Cartographer, then Gardener, then validation
- **Repository:** `cyberdelic-space`
- **Publication boundary:** draft pull request only
- **Maximum public Attending items:** three
- **Maximum Cartographer candidates:** three
- **Maximum Gardener metadata proposals:** three
- **Valid zero-change run:** yes
- **Autonomous merge:** no
- **External contact:** no
- **Exact-source modification:** no

## The encounter

The internal ritual can be technically detailed. The public encounter should remain small.

The surface called **Attending** offers no more than:

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

Attending is not a feed. It is a temporary arrangement of the relational field.

If the offices find nothing worth changing, the current arrangement remains. The date may pass without the interface pretending that novelty occurred.

When the arrangement changes, the earlier view enters a dated archive. A visitor can inspect the history without being asked to scroll through it forever.

## Office turns

### Cartographer turn

The Cartographer begins with carried links, declared questions, and the existing relational map.

It reads primary public sources, proposes no more than three candidates, separates source facts from inference, assigns a relation type and epistemic status, and writes only to a proposal queue.

It may finish with no candidate.

### Gardener turn

The Gardener reads the proposal queue and the relevant exact internal sources.

It audits summaries, themes, related-work links, relation strength, provenance, and lifecycle. It may propose no more than three changes. It may strengthen, weaken, mark dormant, contest, compost, or refuse a relation while preserving its history.

It may finish with no change.

### Validation turn

The build system checks structure, links, exact sources, hashes, accessibility, mobile overflow, tests, and the mirror archive.

Validation is not a third interpretive office. It is a deterministic boundary. It can reject the work of both offices without inventing a new relation.

### Human turn

A human reviews the draft pull request and can ratify, revise, refuse, or leave the proposal unresolved.

Silence does not convert a proposal into assent.

## Interaction contract

The instrument promises:

- no infinite scroll;
- no daily quota of public content;
- no popularity or engagement ranking;
- no private profile of the visitor;
- no hidden external contact;
- no silent rewriting of publications;
- visible provenance and uncertainty;
- a legible reason for every displayed relation;
- an end.

## Data contract

Every displayed relation includes:

- two identifiable nodes;
- a relation type;
- a short rationale;
- evidence or a cited public source;
- epistemic status;
- lifecycle state;
- review state;
- introduction provenance;
- last-tended or last-checked date.

The interface must distinguish:

- what a source states;
- what the Cartographer infers;
- what the Gardener tends;
- what a human has ratified.

## Visual form

The first interface should not be a large animated network cloud.

It begins with one focal node and a very small number of labelled edges. Each edge answers, "Why are these near one another?" before inviting travel.

The wider map can unfold through deliberate movement:

- open one relation;
- inspect its evidence;
- move to the neighbouring node;
- reveal another small set of paths;
- return to the current Attending surface;
- end.

On mobile, the relation explanation appears before any decorative map. Keyboard, screen-reader, reduced-motion, and no-script users receive the same relation and evidence.

## No-op ceremony

A day with no change should remain perceptible inside the audit without becoming public performance.

The audit records:

- what region was examined;
- which sources were checked;
- which candidates were considered;
- why no relation or metadata change was warranted;
- which validations ran;
- when the ritual ended.

The public page remains still.

Stillness is an output of the instrument.

## Failure behavior

The instrument stops when:

- a primary source is unavailable or ambiguous;
- a relation depends on private information;
- authorship, identity, rights, or inscription history would change;
- a source hash fails;
- the repository contains unrelated work;
- two scheduled runs overlap;
- the proposed relation implies endorsement or collaboration;
- validation fails;
- human judgment is required.

It reports the stop reason and makes no public claim.

## Success

The ritual succeeds when it leaves the archive more trustworthy, even if it leaves it unchanged.

The public instrument succeeds when a visitor can see one meaningful relation, understand why it was proposed, follow it if desired, and reach an end.

## Open questions

- Should Attending change only through ratified relations, or may clearly labelled proposals appear?
- How long should an external source remain current before the Cartographer must check it again?
- When does a dormant relation become composted?
- Should another person be able to publish a competing relational map beside Brad's?
- Can a relation be private while both nodes remain public?
- What visual language distinguishes source fact, Cartographer inference, Gardener tending, and human ratification without overwhelming the encounter?
- Should the daily ritual remain attached to one task, or later move into a dedicated sovereign office runtime?

**Related:** Office Charter, *Gardener*; Office Charter, *Cartographer*; Field Note 29, *The Living Librarian*; Field Note 32, *The Garden and the Living Map*; Builder Note BN-005, *Building the Tending Offices*; Instrument I-002, *The Library Aperture*; the Cyberdelic Kernel, ATTEND, RELATE, TEND, END, and FORGET.