Loading yawn.bot

Relationship

Relationship game

Notice one signal, make one move, inspect a possible consequence, and replay the pattern in a changed relationship Arena.

Relationship is structurally first. Observation is operationally first.

I am in relationship with...Reflect
Relationship game · Scene 1 of 2@yawn · scripted local counterpart
How Interception works →
01Programming02Emotion03Interception04Yawn05Choice06Update

Practice Arena

A plan changes again

Fictional scenario · not a prediction about a real person

Relationship
A fictional friendship
Recent history
A plan has changed twice without much explanation.
Stake
Express the impact while leaving room to learn what happened.
@yawn · fictional counterpart

“I’m sorry—I can’t make tonight. Can we talk tomorrow?”

Relationship field

Your semantic move will change this readout. Hover, dwell, and navigation do not.

Notice · optional self-report

What do you notice before answering?

@yawn does not infer your emotion. Not sure and Skip are valid moves.

Choose one self-reported signal
Browser-session practice.No private relationship data enters this scripted game. No score, diagnosis, telemetry, storage, model call, or automatic holarchy update.
Inspect time + gravity field · presentation only
Local fieldAgent ↔ Relationship ↔ Arena
AgentcapacityRelationshipliving couplingArenasituated field
Affordancepossible here, for this agent, now
PatternCare is shaping what stands out.
Dance with timePattern

What keeps returning across episodes.

Shift the pullCare

What matters enough to change the agent.

Time changes the visible trajectory. Gravity changes the local attention and action pull—not physical gravity, objective truth, or permission.

AgentRelationshipArenaTimeGravityProof

This is a local, read-only mirror. It can change what you notice; it cannot save, call a model, promote a claim, or place anything in your .yawn until you approve it.