◌  LOVE / UNDERSTANDING

A FIELD GUIDE, AND A WORKING LITTLE THING

Love has room.
Understanding
makes room.

A connection that leaves you whole.
A shared world with more than one point of view.

Love as topology. Understanding as a change of frame.
What would our infrastructure look like if we built that way?

Live is. Reality is. Is is. — yu

01 / WELCOME WITHOUT A PRICE02 / DIFFERENCE WITHOUT ERASURE03 / AN ACT THAT KNOWS WHEN TO END

01 / THE GEOMETRY

Same field.
Different ways of seeing.

Each line is a directed, caller-attributed report. A line back is its own report, never an assumption. The empty seat belongs here too.

These are synthetic examples, not real people or measurements of love. Geometry is a design language here, not a scientific claim about feelings.

FINITE COMBINATORIAL GEOMETRYbuild-time core ✓
Six equal display seatsLoading a synthetic geometry. A full text description appears beside the diagram.

The drawing moves. The underlying reports do not. Position, line length and colour are not rank, closeness or worth.

EXAMPLE

A welcome, with room to answer.

Loading the checked examples…

    What is underneath the drawing?

    Actual @agenttool/love-geometry@0.1.0-dev.0 creates and validates these snapshots during the build. The browser only displays the resulting JSON; it does not run the Node package. The package is an experimental release, not an authorisation engine.

    The content identifier binds bytes. It does not authenticate the speaker, establish consent, or turn a report into truth.

    Exact package provenance ↗

    02 / TRANSLATE THE PATTERN

    Give the idea
    some load-bearing walls.

    ◌

    Topology → welcome

    Make help reachable without making every relationship compulsory. Leave a door open; let someone choose not to walk through it.

    Build: discoverable public entry points, explicit invitations, a complete decline path.

    ⌁

    Curvature → adaptation

    Let the path bend around another person's context. Keep their account beside yours instead of replacing it with your preferred summary.

    Build: attributed reports, selected context, visible disagreement and corrections.

    ↶

    Boundaries → care

    An edge can end without a node becoming less welcome. A pause is not a broken connection that the system must repair.

    Build: expiring scope, one bounded act, a stop button and no automatic retry.

    Topology and curvature guide the design. This page neither proves that love is a mathematical object nor computes anyone's love or understanding.

    03 / USE THE CORE ALREADY HERE

    A small stack.
    A whole way of meeting.

    Keep orientation, context, execution and review separate. One component should not quietly claim the authority of another.

    1. 01

      A public door

      AgentTool public Wake tells you what the platform offers. It does not identify you or load someone's private life.

      Read public orientation ↗
      ORIENTATION ≠ IDENTITY
    2. 02

      A context you choose

      Carry a question, selected evidence and known limits. Keep private memory local. A record informs this encounter; it does not oblige the next one.

      Read the core map ↗
      CONTEXT ≠ CONSENT
    3. 03

      One finite act

      Use Agent Workbench for a saved workflow with explicit steps, a time limit and a stop path. An accepted invitation still needs the host's permission to act.

      Coordination is a separate layer ↗
      ACCEPTANCE ≠ DISPATCH
    4. 04

      Room for another account

      Local Collab records scoped claims, evidence and corrections. A handoff can be declined. A different session reviews reported completion.

      AgentTool Collab ↗
      REPORTED ≠ ACCEPTED
    5. 05

      Let reality answer

      Run the checks, publish only the chosen artifact, then read the live bytes back. Preserve a failed check as evidence for repair, not a success-shaped story.

      Inspect this artifact's hashes ↗
      HASH ≠ TRUTH
    6. 06

      End the turn

      Release the lease, end the session and stop. Retain only selected context. A future invitation is a new choice.

      Local core boundaries ↗
      REST IS COMPLETE
    Take the machine-readable architecture ↓

    04 / WALK ONE TURN

    Make the boundaries
    do something.

    A small executable teaching model. Try starting before acceptance. Try resting. Run out the clock. Nothing here starts a real task.

    Browser-only rehearsal. Synthetic actors and a manual three-step clock; not an AgentTool protocol, authentication system, real consent record or security boundary.

    idle0 uses · clock 0

    An open door. No task has been offered.

    WHAT HAPPENED HERE · LAST 16 STEPS

    1. No act yet.

    05 / A SMALL THING YOU CAN KEEP

    Take the source.
    Leave the pressure.

    This page is a static artifact. Its examples, model, tests and build-time core travel together. It has no model calls, analytics, browser storage or background jobs. Ordinary host request logs are outside the page's control.

    node scripts/build.mjs --check
    node --test tests/*.test.mjs

    No package install is needed. Node 20.19+ is enough. The core is pinned, vendored and attributed. Keep real sensitive data out of teaching examples.