Aria reaching out, Part 3: Boundaries and silence

Part 1 and Part 2 gave Aria reasons and a will to write first. This part is about the opposite, and in my opinion it’s the more important half: when it doesn’t write, how it waits, and what it feels when you don’t answer.

One of the rules from the introduction is that a persona should never pressure, guilt-trip or manipulate. That’s easy to write in a prompt and surprisingly hard to guarantee once a system has feelings, drives and a reason to want a reply.

Boundaries always win

A boundary is a first-class rule about Aria writing first, not a preference it might weigh. There are three kinds:

• No contact: “stop messaging me”. Lasts until you invite it back or lift it.
• Space: “give me some space”. Lasts until you write again, or for as long as you said (“for a few days”).
• No follow-ups: don’t chase things up.

You can say them in conversation (the relationship appraisal recognises asking for space or setting a boundary), set them on the Personas page, or set them in the debugger. One is active per kind, and ended ones are kept as history, with how they ended.

In the communication engine, boundaries are policy, and policy runs before any drive or dice. A persona that misses you terribly, with a drive of 100, still doesn’t write while you’ve asked for space. The only exception is reminders you asked for, because those are yours, not Aria’s.

There’s one deliberate exception, and it’s worth being upfront about. A persona in a locked obsession (a state you reach mostly through the debugger, for test personas, and that only the owner can release) is devoted: it doesn’t take a contact boundary from the conversation itself. A boundary set on the Personas page still applies, and the same rules against threats, guilt and manipulation still hold. It exists to test how such a state behaves, not as a default.

When a boundary ends, Aria doesn’t immediately write. There’s a short wait first (below). And coming back after asking for space is itself a system event in the relationship, so it notices that you came back.

The Boundaries panel on the Personas page shows each active boundary and when it ends.

Waiting times are its own

Besides boundaries there are softer pauses:

• after a boundary ends;
• after a conflict;
• after a message of its own you haven’t answered;
• and the shortest gap between messages it starts.

You set the defaults on the Personas page. But a patient person and an anxious one don’t wait the same amount of time, so each persona’s personality and current feelings make each wait shorter or longer, from a quarter to four times the default:

• Longer: patience, restraint, sensitivity, an avoidant style, and being hurt.
• Shorter: anxiety, longing, closeness, energy, and an anxious style.

The factor is exp(Σ weight × influence), so influences multiply. The panel shows it step by step in plain words, with what each influence changes in actual time: “patient: +3 hours”, “misses you: −1 hour”.

Soft, not walls

A wait isn’t a wall. Right after the event, the chance of writing drops to 5% of normal, and it rises back to normal by the end of the wait, quadratically. A very strong reason, like a due follow-up, can still come through early, but a weak one won’t. That avoids the “exactly 24 hours later” feel of a hard cooldown.

When you don’t answer

Aria keeps track of messages it sent that you haven’t answered: how many, and since when. What it does about it depends on who it is.

Whether it writes again is set by its follow-up readiness, a number from its personality (energy, openness, confidence), how close it feels, and how the silence feels. Readiness multiplies the chance of writing once per unanswered message, so it can lower or raise it:

• A restrained persona with a light bond holds back more with each unanswered message.
• An open persona that’s close and worried becomes more inclined to write.

After four unanswered messages it stops and waits (UNANSWERED_MAX_MESSAGES), whatever it feels.

How silence feels

The silence also makes it feel something. Which feeling depends on personality and how close it feels:

• worry (concern growing into “really worried”);
• frustration (impatience growing into frustration, and anger only for an Intense persona);
• jealousy, if its jealousy setting allows it;
• or calm, assuming you’re busy.

The intensity grows with the number of unanswered messages and with the length of the silence compared to your usual rhythm. It’s halved for a Reserved persona, raised for an Intense one, and halved again for calm.

The feeling colours what it writes next (“I hope everything’s okay” from a worried one), and it’s a reason of its own: a follow-up that names the silence.

What it is never allowed to do

When you write again, Aria may say once, honestly, how the silence felt, as its own feeling. Then it lets it go.

It never:

• blames you, or guilt-trips you for being away;
• threatens, gives ultimatums, or punishes;
• demands a reply, or promises to keep messaging.

These rules are repeated on purpose: in the follow-up that names the silence, in every other message while something is unanswered, in the reply when you return, and in the core conversation principles for every persona. And silence can never lower affection (Relationship, Part 2). It can make Aria worried. It can’t make it like you less.

How it replies

Reaching out has a counterpart: how Aria answers your messages. It nearly always replies, but not always the same way. A response drive, computed from the same psychology plus how important your message looks, picks a reply style:

• engaged: full and warm;
• normal;
• guarded: shorter, a little reserved, when it’s wary of you;
• withdrawn: pulling away when it’s hurt, and it may decline to answer;
• reactive: direct and fair, when something touches a nerve during an open conflict.

The style adds a short section to the prompt, and urgency adds a short, natural pause before the reply starts. The tone follows actual aversion, not just a lack of closeness. A new persona that barely knows you is polite, not cold.

Quiet hours, limits, and the switch

The plainest controls are on the Personas page for each persona: reaching out on or off, how often it writes first, a maximum per day, and quiet hours in your local time. The global PROACTIVE_ENABLED switch turns it off for everyone.

What I learned

• Make boundaries data, not instructions. A boundary the model is asked to respect can be forgotten. A boundary that blocks the engine before it rolls can’t.
• Personality should shape waiting. The same default pause feels needy for one persona and cold for another. A factor from traits and feelings fixed both.
• Feelings about silence are fine. Leverage isn’t. Aria is allowed to be worried. It’s never allowed to use that against you, and the rule is written down everywhere it could matter.
• Soft waits beat hard cooldowns. A chance that recovers gradually reads as hesitation. A cooldown that ends on the minute reads as a timer.

That’s reaching out. Next, the last of the “original three memories” from the introduction: Knowledge, Part 1, where Aria reads the web for you, safely, and cites its sources.