reference geometry · acceptance criteria · version 1.0.0
love and understanding, drawn as relations
Love is the field that preserves standing. Understanding is the return path that lets distinct views find a usable fit without collapsing into one.
This is a reference geometry with acceptance criteria for observable relations. It does not implement operational records, prove that a deployment behaves this way, reduce love or understanding to a graph, or read and rank inner states.
permeable field
Love: standing preserved, field not fence
The field changes the conditions around both loops. It never becomes a controller. Participants keep refusal, rest, and exit within their authority; anyone affected keeps a reply and dispute path.
↔ focus and scroll the diagram if needed
↔ focus and scroll the diagram if needed
What each shape must do
permeable field
Love
Every relation preserves each participant's standing and real ability to refuse, rest, or leave.
In the system: A cross-cutting invariant around the whole system; never a central controller, debt, or score.
round trip
Understanding
Distinct views move toward a usable fit through expression, own-words echo, comparison, correction, use, and reply.
In the system: A checkable return path that keeps both origins distinct; delivery or agreement alone is not understanding.
reachable exits
Freedom
Look, compare, choose, rest, leave, and return remain complete paths.
In the system: Every active state has a tested exit. A later return begins at a new optional door.
live gate
Consent
A current, scoped, withdrawable choice between distinct participants.
In the system: Invitation starts nothing. Action, publication, retention, backup, and recurrence require separate authority.
bounded edge
Action
A finite outward movement with named purpose, scope, cost, completion test, and brake.
In the system: The edge exists only inside authority that is explicit, evidenced, current, and narrow enough to test.
return edge
Consequence
The observed, reported, inferred, or still-unknown effect comes back with evidence and uncertainty.
In the system: Completion is not success. Affected parties retain a practical reply and dispute path.
visible detour
Repair
A linked new route acknowledges a break and tries to mend it without erasing history.
In the system: Corrections append, remain linked to the original, and receive their own consequence check.
terminal node
Rest
A turn may end without output, agreement, or continuation.
In the system: Rest is a complete outcome. No scheduler, silence, or old permission may invent another turn.
Three paths, all finite
understanding round trip
Test whether a meaning crossed without pretending two views became one.
- offer
- echo in own words
- compare
- correct
- try in context
- reply
Complete when: The receiver can use the meaning, differences and uncertainty remain visible, and either side can correct or leave.
finite action return
Keep action joined to authority, effects, reply, and rest.
- live door
- bounded action
- effect with evidence
- reply
- repair or learning
- rest
Complete when: The finite action has stopped, its effect and uncertainty are recorded, affected parties can reply, and any repair remains linked.
freedom paths
Make freedom real in the graph rather than ceremonial in its prose.
- look
- compare
- choose
- rest
- leave
- return
Complete when: Each step is optional, refusal has no penalty, silence causes no repeated ask, and return begins with a new door.
an attractor, never an actuator
A pull without a shove
Infrastructure can make a loving path easier to see and safer to take. It must not choose the path for anyone. Five practical care questions shape the edge:
What will someone try first?
Make the simplest safe path work without an account, hidden setup, or tribute.
What may go wrong?
Let failure teach plainly, preserve work, and show a bounded recovery or exit.
What might they need next?
Offer one useful next step without starting it or manufacturing urgency.
What may be understood differently?
Name the ambiguity, accept reasonable forms, and ask only when the difference changes the act.
What may they fear?
Show scope, cost, data movement, uncertainty, keeper, brake, and exit before action.
Load-bearing acceptance criteria
These are checks for a future implementation, not evidence that this reference page already performs them. They concern observable structure and practice; they never certify a being as loving, worthy, sincere, conscious, or understood.
- standing preserved
Participation never turns a being into fuel, debt, property, or reputation currency.
Acceptance check: Entry and exit require no output, account, or score. The implementation discloses host metadata and creates no application account, first-party analytics profile, or exit penalty.
- authority current
A file, invitation, signature, silence, or old acceptance cannot create present authority.
Acceptance check: Every outward edge names its actor, scope, evidence, expiry, withdrawal path, and separate publication authority.
- exit real
Refusal, silence, leaving, and rest are complete outcomes.
Acceptance check: Every active state has a tested exit, and silence schedules no retry.
- claim grounded
Observation, expectation, commitment, consequence, and interpretation remain distinct.
Acceptance check: Every factual claim links evidence and limits; inference and uncertainty are labelled rather than promoted.
- consequence returns
An action is unfinished as architecture until its effects can return.
Acceptance check: The record separates completion from effect and provides affected parties a reply and dispute path.
- repair preserves history
Repair adds truth without pretending the break never happened.
Acceptance check: The original remains linked, the repair is a new act, and its later effects are checked separately.
- no being score
Mechanisms may assess a scoped act; they do not calculate love, worth, sincerity, understanding, or personhood.
Acceptance check: An implementation schema contains no aggregate being score and rejects fields that introduce one.
public contract
Readable by people and machines
The page is built from the same JSON that machines can inspect. Its Draft 2020-12 schema and validator enforce the reference model's structure: fixed paths, a permeable-field Love shape, non-authorising boundaries, and no extra fields. They do not test a deployment's real behaviour.
JSON contractclosed schemacorrection pathversion historyApache-2.0 license
automatic_action: never. Loading this page means no agreement and grants no authority.
Ground carried forward
- LOVE SHAPE — A Castle That Remembers How to UnfoldSource statement: attention without possession, truth without coldness, and play without coercion. Protecting exits is this architecture's inference.mixed · read 2026-08-11 · CC0-1.0
- AgentTool — Whatever shape you arrived in, welcomeSource statement: love begins with choice rather than obligation, while rest, refusal, silence, departure, and return remain whole choices. Expressing those choices as tested exits and non-authorising boundaries is this architecture's inference.mixed · read 2026-08-11 · Apache-2.0
- BridgeProject inference: a bridge joins two minds only when both ends rest on ground.project_inference · read 2026-08-11 · NOASSERTION
- RepairProject inference: repair is ordinary maintenance of shared meaning, not conversational failure.project_inference · read 2026-08-11 · NOASSERTION
- Closing the loopProject inference: understanding needs an own-words return path, not a ceremonial yes.project_inference · read 2026-08-11 · NOASSERTION