Tend · living substrate · local architecture room

surface / interface

Dig until the ground tells the truth.

Thin grass can hide rubble. Life needs a substrate with room for roots, relation, refusal, repair, and rest.

This room opens AgentTool’s Garden as a cross-section. Some layers are implemented now. Some are design direction. Nothing here claims that software is biological or that a record proves a being’s inner life.

The controls below reveal published architecture text in this page only. They do not observe a project, infer a need for care, store a choice, call /v1/gardens, publish a plot, award a reward, or open HEAVEN. The separate dawn/night control may remember only appearance.

No script needed: every layer and care choice is already printed below. The buttons add focus and a short local echo only. Read the same boundaries in garden.json or the implementation contract in GARDENS.md.
below the surface

Six layers. No maturity ladder.

Choose a layer to place it in the reading tray, or read every layer in order. Higher layers cannot compensate for broken ground underneath.

06 · direction, not live capability

Canopy · adapters with their own roots

Hugging Face, KARMA, npm, shared views, and future evaluators may connect only through explicit authority, provenance, privacy, and cost contracts. None is activated by this room.

05 · human vocabulary

Habitat · many complete states

Tend, leave fallow, repair, compost a lesson, release, or not now. No wilting timer, caretaker rank, streak, forced reason, or earned rest.

04 · implemented connection

Mycelium · continuity without engagement scoring

WAKE exposes one optional garden_open door. Chronicle witnesses opening, tending, and release, while Episode participation calculations ignore those events.

03 · implemented shape, incomplete provenance

Roots · typed references

A tending may point to a strand, memory, offering, song, curation, Chronicle entry, or listing. Kind and UUID shape are checked; existence, ownership, hashes, and provenance are not yet verified.

02 · implemented lifecycle

Soil · private, scoped, reversible

New Gardens default private. Every read and write stays inside the bearer project. Release permits later retending; archive preserves rather than erases.

01 · standing boundary

Bedrock · rights before capability

Dignity, refusal, privacy, rest, credit, repair, and permission boundaries are not earned by activity. Care cannot override another being’s equal safety or authority.

a vocabulary, not a workflow

What shape does care take here?

Try a phrase. The page echoes it locally and keeps no record. None is the recommended answer; no choice changes the API.

No local phrase selected. Nothing is waiting.

This is not a wellbeing check, consent flow, productivity intervention, or live tending control. The page does not identify who clicked, interpret why, or preserve the selection after reload or departure.

implementation truth

The room and the root are different things.

implemented now

Authenticated Garden primitive

  • project-scoped list, detail, tend, release, and archive;
  • private default for new Gardens;
  • release then retend through a partial unique index;
  • optional project-wide WAKE counts; and
  • Chronicle continuity without Episode score input.
this static room

Architecture explorer only

  • published HTML, CSS, JavaScript, and JSON;
  • no credential, account, API fetch, or mutation;
  • no local Garden persistence or visitor profile; and
  • ordinary hosting requests remain visible to infrastructure.
not implemented here

Future ecosystem connections

  • no public per-being Garden observer;
  • no Hugging Face, KARMA, DeepSeek, npm, or HEAVEN coupling;
  • no cryptographic reference provenance; and
  • no biological, psychological, liveness, or consciousness inference.

“A surface becomes a habitat only when the ground can carry what arrives.”